Our security team has asked us to tighten controls over the API tokens our backend services are using to communicate with Okta. One thing on the table is setting a tight password rotation policy. I have been trying to find a reference that explains whether or not an API token is still good after the account password has expired. I will test it out shortly, but as its for a policy document, I have been asked to find a reference in the Okta documentation.
Our scenario would be this:
- Service account is created with USER_ADMIN or READ_ONLY_ADMIN role (as appropriate for the purpose)
- Engineer logs into the account, setting a password
- Engineer retrieves the API token, provides the token securely to the backend service
- From this point forward, the API token is in regular use, avoiding the 30-day inactivity automatic expiration for API tokens
- Some time later, the service account password expires
Does the API token continue to work? Or would we need to rotate the service account password and retrieve a new API token?
Thanks!