Update the Atlassian Tenant URL in an Okta Integration

When an organization changes its Atlassian domain, administrators must update the JIRA Base URL, Assertion Consumer Service (ACS) URL, and Entity ID in the Okta Admin Console. The Atlassian Security Assertion Markup Language (SAML) configuration must also be updated to ensure Single Sign-On (SSO) continues to function correctly.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Atlassian Cloud (JIRA) SAML Application
• Single Sign-On (SSO)

What are the steps to update the Atlassian tenant URL in an Okta integration?

Update the JIRA Base URL in the Okta Admin Console, confirm the ACS URL and Entity ID, update the Atlassian SAML configuration, and test the SSO login.

1. In the Okta Admin Console, navigate to the Atlassian Cloud (JIRA) SAML application.
2. Go to the Sign On tab and select Advanced Sign-On Settings.
3. Replace the old JIRA Base URL (https://<oldlink>.atlassian.net) with the new JIRA Base URL (https://<newlink>.atlassian.net).
4. Confirm that the ACS URL in Okta matches the ACS URL provided in the Atlassian SAML configuration. The ACS URL and Entity ID are generated based on the JIRA Base URL. If Atlassian provides updated metadata after the domain change, reimport the ACS URL and Entity ID in Okta, or manually update them to match.
5. In the Atlassian admin portal, update the SAML configuration to use the new ACS URL and metadata from Okta if required.
6. Test the SSO login to confirm users authenticate successfully with the new domain.

NOTE: Test this configuration in a preview environment before deploying the changes to a production environment.