Troubleshooting SSO with Crowd

1. Confirm that you can log into each application with the same username and password.

Applications -> Click View next to the application -> Config Test

2. Ensure each Atlassian application's WEB-INF/classes/seraph-config.xml file is using the original authenticator class instead of the com.atlassian.crowd authenticator class. For example in JIRA:

<authenticator class="com.atlassian.crowd.integration.seraph.JIRAAuthenticator"/>

should revert to

<authenticator class="com.atlassian.seraph.auth.DefaultAuthenticator"/>

3. Once each application is using centralized authentication instead of SSO, confirm you can log in to each application with the same username and password.

4. Ensure that each application is using the same sub-domain. For example:

• JIRA -> jira.example.com
• Confluence -> confluence.example.com
• Crowd -> crowd.example.com

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 following documentation:

• http://confluence.atlassian.com/display/CROWD/5.2.3+Domain

まだ問題が解決しませんか。

1. Under Admin -> Logging & Profiling, please change the com.atlassian.crowd package to DEBUG.
2. Replicate the SSO problem you are having.
3. Attach the resulting {CROWD}/atlassian-crowd.log file to a support issue at http://support.atlassian.com.