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.
Remote Directory limitations
Up to version 2.0.4, there was a limitation when using SAML SingleSignOn with remote directories (e.g. LDAP):
If a user was created in the LDAP, this user was not found during the SAML login process until the next directory synchronization. This has been resolved with version 2.0.5, but the solution uses APIs which require these versions of Atlassian products:
Jira | 7.3.0 |
Confluence | 6.1.0 |
Bitbucket | 4.12.0 |
This is why version 2.0.5 raised the minimal version requirements.
Version 2.0.7 re-enables compatibility with the versions compatible with version 2.0.x of the add-on:
Jira | 7.0.4 |
Confluence | 6.1.0 |
Bitbucket | 5.9.1 |
With these versions, it can happen that users newly created in a remote directory see an error message when trying to login. This is the same behaviour as with add-on versions < 2.0.5 but has an explicit error message now. To resolve this, you can wait for the directory to synchronise, manually trigger a directory sync or upgrade your host application.