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.
Cannot access Jira / Confluence/ Bitbucket/ Bamboo/ Fisheye-Crucible anymore - Bypass SSO
Problem
I have installed the SAML Single Sign On for Jira/ Confluence/ Bitbucket/ Bamboo/ Fisheye-Crucible Server or Data Center successfully.
Further, I have activated "Enabled SSO Redirect" on the plugin configuration page.
After the configurations are done, I logged out and tried logging in with SSO.
Unfortunately, this results in an error page on the Identity Provider or in the Atlassian Server or Data Center application itself.
I cannot access the Jira/ Confluence/ Bitbucket/ Bamboo/ Fisheye-Crucible anymore.
Is there a way to bypass the Single Sign On and get the default login again?
Solution
For bypassing the Single Sign-On, please use one of the following URLs:
Application | Nosso URL |
---|---|
JIRA | https://<jira-baseurl>/login.jsp?nosso |
Confluence | https://<confluence-baseurl>/login.action?nosso |
Bitbucket | https://<bitbucket-baseurl>/login?nosso |
Bamboo | Bamboo 5: https://<bamboo-baseurl>/userlogin!default.action?nosso Bamboo 6 and later: https://<bamboo-baseurl>/userlogin!doDefault.action?nosso |
Fisheye-Crucible | https://<fisheye-baseurl>/login?nosso |
From plugin version 6.5 it is also possible to use ?auth_fallback
instead of ?nosso
. This is used in Atlassian SSO implementation and might help remember the redirection bypass URLs better when switching to our plugin.
If you still have problems reaching your application, please contact our support here: https://jira.resolution.de/servicedesk/customer/portal