3.2.04 Integrating Crowd with Atlassian CrowdID

Atlassian CrowdID is a free add-on to Crowd. It gives administrators a secure way to provide OpenID accounts for their users.

Prerequisites

1. Download and install Crowd. Refer to the Crowd installation guide for detailed information on how to do this. We will refer to the Crowd root folder as CROWD.
2. This guide assumes that CrowdID was NOT installed with the installation of Crowd. If CrowdID was installed using the Crowd Setup Wizard, there is no need for further configuration.

Step 1. Configuring Crowd to talk to CrowdID

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

The CrowdID application will need to locate users from a directory configured in Crowd. You will need to set up a directory in Crowd for CrowdID. For information on how to do this, see 2.2 Adding a Directory. We will assume that the directory is called CrowdID 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 CrowdID Directory to house CrowdID users.

CrowdID also requires an administrator group to exist in the directory. You need to ensure that a crowd-administrators groups exist in the CrowdID Directory. Any user in this group will have CrowdID administrator access.

The Crowd documentation has more information on creating groups,  creating principals and assigning principals to groups.

1.2 Define the CrowdID Application in Crowd

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

1. Log in to the Crowd Administration Console and navigate to Applications > Add Application.
2. Fill out the form to add the CrowdID application:
   
   

The Name and Password values must match the application.name and application.password that you set in the CROWD/crowd-openidserver-webapp/WEB-INF/classes/crowd.properties (see Step 2 below).

1.3 Specify which users can log in to CrowdID

Now that Crowd is aware of the CrowdID application, Crowd needs to know which directories or users can authenticate (log in) via Crowd. You can either allow entire directories to authenticate, or just particular groups within the directories. In our example, we will allow the entire CrowdID Directory to authenticate:

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

1.4 Specify the address from which CrowdID can log in to Crowd

Please see 3.5 Specifying an Application's Address or Hostname. Please note:

• If CrowdID is on a different host to Crowd
  If you are running the CrowdID on a different host to Crowd, you will need to modify the permissible hosts via the Remote Addresses tab. This lists the hosts/IP addresses that are allowed to authenticate to Crowd. If CrowdID is remote to Crowd, add the IP address of your CrowdID server and ensure the "Status" field is set to "true". Remove the entry for localhost.

• If CrowdID is on the same host as Crowd
  By default, when you add an application, localhost is a permissible foreign host. However, you will also need to manually add the IP address 127.0.0.1, as incoming requests to Crowd from CrowdID (both on the same, local, host) may be from the host 127.0.0.1 and not localhost. Crowd does not do a DNS lookup of the hostname, rather, it compares the values as is. Ensure the "Status" field is set to "true".

Step 2. Configuring CrowdID to talk to Crowd

CROWD/crowd-openidserver-webapp/WEB-INF/classes/crowd.properties を編集します。次のプロパティを変更します。

If your Crowd server's port is configured differently from the default (i.e. 8095), set it accordingly. The application.name and application.password must match the Name and Password that you specified when you defined the application in Crowd (see Step 1 above). The application.login.url should point to the correct host and port of the CrowdID application.

See CrowdID in Action

• Go to http://localhost:8095/openidserver and login with any principal in the CrowdID Directory.

関連トピック  

• 3.1 Using the Application Browser
• 3.2 Adding an Application
  • 3.2.01 Integrating Crowd with Apache
  • 3.2.02 Integrating Crowd with Subversion
  • 3.2.03 Integrating Crowd with Atlassian Confluence
    • 3.2.3.1 Configuring Confluence for NTLM SSO
  • 3.2.04 Integrating Crowd with Atlassian CrowdID
  • 3.2.05 Integrating Crowd with Atlassian FishEye
    • Configuring FishEye 1.3.x to talk to Crowd
  • 3.2.06 Integrating Crowd with Atlassian JIRA
    • 3.2.6.1 Configuring JIRA for NTLM SSO
  • 3.2.07 Integrating Crowd with Jive Forums
    • 3.2.7.1 Jive SSO
  • 3.2.08 Integrating Crowd with Atlassian Bamboo
  • 3.2.09 Integrating Crowd with Acegi Security
    • Integrating AppFuse - a Crowd-Acegi Integration Tutorial
  • 3.2.10 Integrating Crowd with Atlassian Crucible
  • 3.2.11 Integrating Crowd with a Custom Application
• 3.3 Mapping a Directory to an Application
  • 3.3.1 Specifying the Directory Order for an Application
  • 3.3.2 Specifying an Application's Directory Permissions
    • Example of Directory Permissions
• 3.4 Specifying which Groups can access an Application
• 3.5 Specifying an Application's Address or Hostname
• 3.6 Testing a User's Login to an Application
• 3.7 Managing an Application's Session
• 3.8 Deleting or Deactivating an Application

Crowd 1.2 Documentation