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

Option 1: Temporarily Disable the Plugin at Startup

Jira (Server) and Confluence (Server & Data Center)

Use the following commands based on your operating system:

Jira:

• Windows:

  1. <installation-directory>\bin\start-jira.bat /disableaddons=com.resolution.atlasplugins.samlsso.Jira

• Linux:

  1. <installation-directory>/bin/start-jira.sh --disable-addons=com.resolution.atlasplugins.samlsso.Jira

Confluence:

• Windows:

  1. <installation-directory>\bin\start-confluence.bat /disableaddons=com.resolution.atlasplugins.samlsso.Confluence

• Linux:

  1. <installation-directory>/bin/start-confluence.sh --disable-addons=com.resolution.atlasplugins.samlsso.Confluence

Limitations

Option 2: Manually Remove Plugin Files

Follow these steps if Option 1 isn't feasible:

1. Stop your application.

2. Navigate to the plugin directories:

3. Delete all files beginning with:

   • samlsso

   • samlwrapper

4. Restart your application.

Limitations

Option 3: Clear Plugin Configuration

If the issue persists after disabling the plugin:

• Clear the SAML SSO plugin configuration following this guide.

Additional Resources

• Production Rollout Checklist

• Retrieve and Upload Config via API

• Atlassian Guide: Manually Remove Malfunctioning Add-ons

Support

If issues persist or further assistance is needed, please contact support via https://jira.resolution.de/servicedesk/customer/portal.