JIRA confluence 集成crowd單點登錄

2.2 Configure JIRA to use Crowd's Authenticator to enable SSO (Optional)

At this stage, JIRA is set up for centralized authentication. If you wish, you can now enable single sign-on (SSO) to JIRA. This will ensure that JIRA's authentication and access request calls will be performed using Seraph.

Note: if you are migrating/upgrading a JIRA instance that already uses Crowd, you will need to merge these files (not overwrite them).

1. If JIRA is running, shut it down first.

2. Edit the JIRA/atlassian-jira/WEB-INF/classes/seraph-config.xml file. Comment out the authenticator node:

   1

   <!--<authenticator class="com.atlassian.jira.security.login.JiraSeraphAuthenticator"/>-->

   
   Uncomment the line that contains the new authenticator:

   1

   <authenticator class="com.atlassian.jira.security.login.SSOSeraphAuthenticator"/>

3. Copy the crowd.properties file from CROWD/client/conf/ to JIRA/atlassian-jira/WEB-INF/classes.

4. Edit JIRA/atlassian-jira/WEB-INF/classes/crowd.properties. Change the following properties:

   Key	Value
   application.name	jira  The application name must match the name that you specified when you defined the application in Crowd (see Step 1 above).
   application.password	The password must match the one that you specified when you defined the application in Crowd (see Step 1 above).
   crowd.base.url	eg. (http://localhost:8095/crowd/) If your Crowd server's port is configured differently from the default (i.e. 8095), set it accordingly. crowd.base.url must be the same URL used to access Crowd in your Browser.
   session.validationinterval	Set to 0, if you want authentication checks to occur on each request. Otherwise set to the number of minutes between request to validate if the user is logged in or out of the Crowd SSO server. Setting this value to 1 or higher will increase the performance of Crowd's integration.

It is possible to define multiple user directories in JIRA. However, if you enable SSO integration, you will only be able to authenticate as users from the Crowd server defined in the crowd.properties file.

You can read more about optional settings in the crowd.properties file.

2.3 (Optional) Disable the Auto-Complete Function in JIRA's User Picker

To improve performance on page-loading in JIRA, we recommend that you disable the auto-complete function in JIRA's 'User Picker' popup screens. Follow the instructions in the JIRA documentation.

More information: In our experience, disabling this feature in JIRA helps performance for customers with extremely large user bases. If you leave this feature enabled and have adequate performance results in JIRA, feel free to leave it enabled.