Reversing One Login SSO To Log In With Local User
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
In some circumstances it may be required to log into JIRA as a local user to diagnose an environment that has One Login SSO authentication enabled. Due to the nature of this customization it is not possible without reverting JIRA to a stock user login configuration.
Workaround
Here is a set of steps that can be leveraged to undo the specific customizations that will allow you to log in as a local user.
Stop JIRA
Create a backup and then replace the following files with the original versions. If these files are not immediately available they can be found in the tar or zip release for your specific version found in https://www.atlassian.com/software/jira/download-archives
JIRA_INSTALL/atlassian-jira/secure/views/dashboard.jspJIRA_INSTALL/atlassian-jira/includes/loginform.jspJIRA_INSTALL/atlassian-jira/WEB-INF/classes/seraph-config.xmlRemove the following file from JIRA_INSTALL and JIRA_INSTALL/bin:
jira_onelogin.xmlMove the plugin file
customauth-jira-6.1.2.jarfromJIRA_INSTALL/atlassian-jira/WEB-INF/libto a temporary location- Restart JIRA
Once the original issue is resolved the steps documented in the following article can be used to reconfigure SSO/SAML.
https://onelogin.zendesk.com/hc/en-us/articles/201173884-Configuring-SAML-for-JIRA