Please follow the steps below to troubleshoot problems with SSO (single sign-on) in Crowd:
Set each application to use centralised SSO authentication, as follows. Ensure that each Atlassian application's WEB-INF/classes/seraph-config.xml file is using the Crowd's com.atlassian.crowd authenticator class. For example in JIRA, instead of this:
<authenticator class="com.atlassian.jira.security.login.JiraSeraphAuthenticator"/> |
you should have this:
<authenticator class="com.atlassian.jira.security.login.SSOSeraphAuthenticator"/> |
Please, see our Adding an Application Tutorial page to check the SSO authenticator classes for other applications.
SSO will only work with applications on the same sub-domain. Why? Crowd uses a cookie to manage SSO and your browser only has access to cookies in the same sub domain, e.g. *.example.com.
This is the value that you set in the Domain property (e.g. .example.com) for Crowd to enable SSO. This is covered in the documentation on configuring the domain.
If the above steps have not solved your problem, please gather some debugging information as described below before contacting Atlassian support:
com.atlassian.crowd package to DEBUG.CROWD HOME}/logs/atlassian-crowd.log file with the debug information gathered.