Manage API key expiration for SCIM
In early January of 2025, we automatically set API keys for SCIM to expire in one year when you:
set up user provisioning
regenerate an API key for your identity provider directory
This does not affect existing API keys for SCIM.
Who can do this? |
An API key for SCIM with an expiration date reduces your security risk. When your API key expires, you can’t provision and de-provision users between your identity provider and Atlassian. If a key is leaked or stolen, its limited lifespan prevents attackers from using it to access sensitive information in your Atlassian organization.
When you set up user provisioning or regenerate an API key, we automatically set it to expire in one year.
You may need to regenerate an API key for SCIM to:
Address a security breach
Control user access to your organization
Keep provisioning users to your identity provider directory
When you regenerate an API key for SCIM, the existing key stops working.
Regenerate API key for SCIM
Regenerate an API key to set the expiration date to one year.
To regenerate the API key:
Log in to admin.atlassian.com. Select your organization if you have more than one.
Select Security > Identity providers.
Select your Identity provider Directory.
Select Regenerate API key from […}.
Copy the SCIM base URL and API key details to your identity provider.
API key expiration date appears next to the API key details.
View API key expiration for SCIM
After you set up user provisioning for an identity provider directory, you can view when your API key for SCIM expires.
To view when the API key expires:
Log in to admin.atlassian.com. Select your organization if you have more than one.
Select Security > Identity providers.
Select your Identity provider Directory.
Go to Provisioning to view API key expiration.
You can regenerate an API key for SCIM when your key expires.
Was this helpful?