Application startup issue - Disable SSO Plugin
Problem Description
After installing, updating, enabling, or configuring the SAML Single Sign-On plugin (by Resolution) for Atlassian Data Center or Server products such as Jira, Confluence, Bitbucket, Bamboo, or Fisheye/Crucible, the application crashes or fails to start.
When to Use This Guide
- The application fails to start after plugin changes. 
- Access via the standard Plugin Manager UI is not possible. 
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 | <installation-directory>/bin/start-jira.bat /disableaddons=com.resolution.atlasplugins.samlsso.Jira:com.resolution.samlwrapper-plugin | 
| Linux | 
 | |
| Confluence | Windows | <installation-directory>/bin/start-confluence.bat /disableaddons=com.resolution.atlasplugins.samlsso.Confluence:com.resolution.samlwrapper-plugin | 
| 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.
