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.
Application startup issue - Disable SSO Plugin
Problem
After installing/updating/enabling/configuring the SAML Single Sign On plugin for Data Center or Server, the JIRA/Confluence/Bitbucket/Bamboo/Fisheye-Crucible application crashed and it is not starting anymore.
How can I remove/disable the SAML Single Sign On plugin without the Plugin Manager?
Solution
JIRA and Confluence Server & Confluence Data Center:
You can temporarily disable the SAML Single Sign On plugin for Atlassian Data Center / Server at startup, using the following startup script commands:
Application | Operation System | Command |
---|---|---|
JIRA | Windows |
|
Linux | <installation-directory>/bin/start-jira.sh --disable-addons=com.resolution.atlasplugins.samlsso.Jira:com.resolution.samlwrapper-plugin | |
Confluence | Windows |
|
Linux |
|
Please note: This feature does not work for JIRA Data Center applications
Bitbucket Data Center & Server and Bamboo Server:
Delete all files starting with samlsso and samlwrapper in the following directory:
Bitbucket: <home-directory>/shared/plugins/installed-plugins
Bamboo: <home-directory>
/plugins
Fisheye-Crucible: <instance-directory>/var/plugins/user
Start the application.
Clear SAML SSO Config:
To clear the current configurations, so the plugin can be enabled again with an empty configuration page, follow this guide: Clear the configuration
Please know: The plugin configurations can't be restored after clear if you have no backup created with the "Download XML" function before.