Important Update Effective February 1, 2024!
Due to recent changes in Jira and Confluence, we've made the tough decision to discontinue the OpenID Connect (OIDC)/OAuth app and no longer provide new versions for the newest Jira/Confluence releases as of January 31, 2024.
This is due to some necessary components no longer shipping with Jira/Confluence, which would require some extensive rewrites of the OIDC App.
Important Update! This app will be discontinued soon!
Due to recent changes in Jira, which no longer ships with some components required for our Read Receipts app to run, we've made the tough decision to discontinue the app, as of Februar 5, 2025.
Important Update! This app will be discontinued soon!
We've made the tough business decision to discontinue the app, as of January 11, 2025.
Microsoft Entra ID (formerly Azure AD): Migrate to Client Credentials Flow
Starting with User Sync 1.5.0/ SAML SSO 3.5.5, the Azure AD connector is using a different OAuth2 authentication flow,
where it is no longer necessary to explicitly authorize the application from within the Atlassian application.
After updating to 1.5.0 you see this message in the Azure AD connector details:
Follow these steps to migrate to the new authorization method:
- Go to portal.azure.com, click "Azure Active Directory" in the left panel and then choose "App registrations".
- Open the application you have already created for User Sync.
- Click on "API permissions" on the left navigation.
- Make sure "Directory.Read.All" is configured as an "Application Permission"
- All other permissions can be removed:
- Click on "Grant admin consent for ...". It should look like this:
- Confirm the action
- Switch back to the Azure AD connector configuration in User Sync.
- Select "click here to switch to the new authorization method" to complete the migration.