Authorizing the Atlassian Admin connection in Okta Workflows requires an API token and a Directory ID. Configuring user provisioning for the Okta Identity Provider (IdP) in the Atlassian Admin site generates the API token. Using an API key generated from the Atlassian Admin site settings fails and Okta generates the following error:

{
"error": "Not authorized to access : scim/directory/{directoryId}/Users",
"traceId": "e40ee97f819a2465"
}

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Workflows
• Atlassian Admin Connector

What steps are required to generate the API key and Directory ID for the Atlassian Admin connector?

Configuring the provisioning for the Okta IdP in the Atlassian Admin site generates the API key and the System for Cross-domain Identity Management (SCIM) base URL containing the Directory ID. Administrators must copy and store the API key securely, as Atlassian does not allow later retrieval. If the API key for user provisioning is unavailable, administrators must regenerate it.

NOTE: Regenerating a new API key disables the existing key. Identify where the existing key is in use to update it after generating a new key. For example, update the provisioning configuration for the Atlassian Cloud Okta Integration Network (OIN) application from the Okta Admin Console.

Regenerate the API key in the Atlassian Admin site by navigating to the identity providers section, opening the Okta directory configuration, and selecting the regenerate option in the user provisioning menu.

1. Navigate to Security > Identity Providers.
2. Select the Directory name for the Okta identity provider to open the configuration page.
3. Select the ellipsis menu in the User provisioning section to access the Regenerate API key menu item.
   
4. Select Regenerate API key to display the confirmation message.
   
5. Select Regenerate key to generate the new key and the Directory base URL.

Related References

• Atlassian Admin Authorization
• Configure user provisioning with Okta