If you want to enable SSO from app A to app B, do you have to configure and restart both apps, or just A?

[Andrew Pennebaker]

For testing purposes, it would be convenient if only the origin application needed to be taken down for configuration, while the destination remained online, unmodified.

[Jobin Kuruvilla [Adaptavist]]

Crowd SSO needs different authenticator to be configured on all the apps and need crowd.properties file populated with correct values. Once the authenticator is changed, you will have to restart the apps.

[C_ Faysal]

files to be edited are for example:

Jira:

atlassian-jira/WEB-INF/classes/crowd.properties
atlassian-jira/WEB-INF/classes/seraph-config.xml

Confluence:

confluence/WEB-INF/classes/crowd.properties
confluence/WEB-INF/classes/seraph-config.xml

the crowd.properties must be editied to fit your installation (crowd URL, application name&passwd)

in the seraph-config.xml you will need to comment out the internal authenticator and comment in the crowd authenticator.

like this: (this is for confluence)

<!-- Default Confluence authenticator, which uses the configured user management for authentication. -->
   <!--<authenticator class="com.atlassian.confluence.user.ConfluenceAuthenticator"/>-->


   <!-- Authenticator with support for Crowd single-sign on (SSO). -->
   <authenticator class="com.atlassian.confluence.user.ConfluenceCrowdSSOAuthenticator"/>

of course you need to restart confluence afterwards

[C_ Faysal]

i think i missunderstood the question or at least the desciption...sorry :)