Integrating Crowd with Atlassian Confluence

Atlassian's popular Confluence wiki can quickly be configured to use Crowd for user and group management.

On this page:

Compatibility of Confluence and Crowd Versions

Please ensure that your Crowd and Confluence versions are compatible:

Prerequisites

1. Download and install Crowd. Refer to the Crowd installation guide for instructions. We will refer to the Crowd root folder as CROWD.
2. Download and install Confluence (version 2.6.2 or later). Refer to the Confluence installation guide for instructions. We will refer to the Confluence root folder as CONFLUENCE. For the purposes of this document, we will assume that you have used the Crowd distribution (not EAR-WAR) (i.e. the easier) installation method of Confluence. If you need to install Confluence as an EAR/WAR, simply explode the EAR/WAR and make the necessary changes as described below, then repackage the EAR/WAR.
3. Run the Confluence Setup Wizard, as described in the Confluence documentation. During this setup process, you will define the Confluence administrator's username and password. It is easier to do this before you integrate Confluence with Crowd.
4. After setting up Confluence, shut down Confluence before you begin the integration process described below.

Step 1. Configuring Crowd to Talk to Confluence

1.1 Prepare Crowd's Directories/Groups/Users for Confluence

The Confluence application will need to authenticate users against a directory configured in Crowd. You will need to set up a directory in Crowd for Confluence. For more information on how to do this, see Adding a Directory. We will assume that the directory is called Confluence Directory for the rest of this document. It is possible to assign more than one directory for an application, but for the purposes of this example, we will use Confluence Directory to house Confluence users.

Confluence also requires particular groups to exist in the directory in order to authenticate users. You will need to create two groups in the Confluence Directory:

1. confluence-users
2. confluence-administrators

See the documentation on Creating Groups for more information on how to define these groups.

You also need to ensure that the Confluence Directory contains at least one user who is a member of both groups. Choose one of the two options below:

• If you have an existing Confluence deployment and would like to import existing users and groups into Crowd, use the Confluence Importer tool by navigating to Users > Import Users > Atlassian Importer. Select 'Confluence' as the Atlassian product, and the Confluence Directory as the directory into which Confluence users will be imported. For details please see Importing Users from Atlassian Confluence.

  If you are going to import users into Crowd, you need to do this now before you proceed any further

  
  OR:

• If you don't wish to import your Confluence users, make sure you use Crowd to create at least one user in the Confluence Directory and assign them to both the confluence-users and the confluence-administrators group. The Crowd documentation has more information on creating groups, creating users and assigning users to groups.

1.2 Define the Confluence Application in Crowd

Crowd needs to be aware that the Confluence application will be making authentication requests to Crowd. We need to add the Confluence application to Crowd and map it to the Confluence Directory:

1. Log in to the Crowd Administration Console and navigate to Applications > Add Application.

2. Complete the 'Add Application' wizard for the Confluence application. See the instructions.

   The Name and Password values you specify in the 'Add Application' wizard must match the application.name and application.password that you will set in the CONFLUENCE/confluence/WEB-INF/classes/crowd.properties file. (See Step 2 below.)

1.3 Specify which Users can Log In to Confluence

Once Crowd is aware of the Confluence application, Crowd needs to know which users can authenticate (log in) to Confluence via Crowd. As part of the 'Add Application' wizard, you will set up your directories and group authorizations for the application. If necessary, you can adjust these settings after completing the wizard. Below are some examples.

You can either allow entire directories to authenticate, or just particular groups within the directories. In our example, we will allow the confluence-users and confluence-administrators groups within the Confluence Directory to authenticate:

For details please see Specifying which Groups can access an Application.

1.4 Specify the Address from which Confluence can Log In to Crowd

As part of the 'Add Application' wizard, you will set up Confluence's IP address. This is the address which Confluence will use to authenticate to Crowd. If necessary you can add a hostname, in addition to the IP address, after completing the wizard. See Specifying an Application's Address or Hostname.

Step 2. Configuring Confluence to talk to Crowd

2.1 Add a Crowd Directory in Confluence

Confluence can use Crowd for user authentication simply by adding the 'Atlassian Crowd' user directory.

1. Log in to Confluence Admin as 'confluence-administrator'.
2. Click on the 'User Directories' label of the left bar under the 'Security' tab.
3. Click 'Add Directory'. Then select 'Atlassian Crowd' from the dropdown list. Click 'Next'.
4. Enter connection parameters and save. Now a new Crowd directory should appear on the user directory list.

For more information on configuring a Crowd remote directory in Confluence, check out the Confluence documentation on Connecting to Crowd or Jira for User Management.

2.2 Enable SSO integration with Crowd (Optional)

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

2. Now, edit the file CONFLUENCE/confluence/WEB-INF/classes/seraph-config.xml
   Comment out the line:-

   <!-- <authenticator class="com.atlassian.confluence.user.ConfluenceAuthenticator"/> -->
   

   Uncomment the line:-

   <authenticator class="com.atlassian.confluence.user.ConfluenceCrowdSSOAuthenticator"/>
   

3. Copy the crowd.properties file from CROWD/client/conf/ to CONFLUENCE/confluence/WEB-INF/classes.

4. Edit CONFLUENCE/confluence/WEB-INF/classes/crowd.properties. Change the following properties:

   Key	Value
   application.name	confluence The application.name and application.password must match the Name and Password that you specified when defining the application in Crowd (see Step 1 above).
   application.password	The application.name and application.password must match the Name and Password that you specified when defining the application in Crowd (see Step 1 above).
   crowd.base.url	http://localhost:8095/crowd/ If your Crowd server's port is configured differently from the default (i.e. 8095), set it accordingly.
   session.validationinterval	This is the number of minutes between validation requests, when Crowd validates whether the user is logged in to or out of the Crowd SSO server. Set to the required number of minutes between validation requests. The recommended default is 2 minutes. Setting this value to 1 or higher will increase the performance of Crowd's integration. Setting this value to 0 will cause the application to perform authentication checks on each request but can cause poor performance, especially with Crowd 2.1 - Crowd 2.3.2 using REST due to CWD-2646.

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

    

See Crowd in Action

• Users belonging to the confluence-users group should now be able to log in to Confluence.
• Try adding a user to the confluence-users group using Crowd — you should be able to log in to Confluence using this newly created user. That's centralized authentication in action!
• If you have enabled SSO, you can try adding the Confluence Directory and confluence-administrators group to the crowd application (see Mapping a Directory to an Application and Specifying which Groups can access an Application). This will allow Confluence administrators to log in to the Crowd Administration Console. Try logging in to Crowd as a Confluence administrator, and then point your browser at Confluence. You should be logged in as the same user in Confluence. That's single sign-on in action!

RELATED TOPICS

• Using the Application Browser
• Adding an Application
  • Integrating Crowd with Atlassian Bamboo
  • Integrating Crowd with Atlassian Confluence
    • Integrating Crowd with Atlassian Confluence 3.4 or earlier
    • Updating Files in a Confluence Evaluation Distribution
  • Integrating Crowd with Atlassian CrowdID
  • Integrating Crowd with Atlassian Crucible
  • Integrating Crowd with Atlassian FishEye
    • Configuring FishEye earlier than 4.0 with Crowd
  • Integrating Crowd with Atlassian JIRA
    • Integrating Crowd with Atlassian JIRA 4.2 or earlier
  • Integrating Crowd with Atlassian Bitbucket Server
  • Integrating Crowd with Acegi Security
    • Integrating AppFuse - a Crowd-Acegi Integration Tutorial
  • Integrating Crowd with Apache
    • Disabling Previous Versions of the Crowd Apache Connector
    • Installing the Crowd Apache Connector on CentOS Linux
    • Installing the Crowd Apache Connector on Red Hat Enterprise Linux
    • Installing the Crowd Apache Connector on Ubuntu Linux
    • Installing the Crowd Apache Connector on Debian
    • Installing the Crowd Apache Connector on Other UNIX-Like Systems
    • Installing the Crowd Apache Connector on Windows
  • Integrating Crowd with Jive Forums
    • Jive SSO
  • Integrating Crowd with Spring Security
    • Integrating AppFuse - a Crowd-Spring Security Integration Tutorial
  • Integrating Crowd with Subversion
  • Integrating Crowd with a Custom Application
  • Integrating Crowd with Atlassian HipChat
• Configuring the Google Apps Connector
• Mapping a Directory to an Application
  • Specifying the Directory Order for an Application
  • Specifying an Application's Directory Permissions
    • Example of Directory Permissions
  • Viewing Users in Directories Mapped to an Application
  • Specifying which Groups can access an Application
• Effective memberships with multiple directories
• Specifying an Application's Address or Hostname
• Testing a User's Login to an Application
• Enforcing Lower-Case Usernames and Groups for an Application
• Managing an Application's Session
• Deleting or Deactivating an Application
• Configuring Caching for an Application
• Overview of SSO
• Configuring Options for an Application

Crowd 3.0 beta documentation