7.4.6. Using Atlassian Crowd
If your organization is using Atlassian products such as JIRA and Confluence, you may also be using
Crowd. Crowd is a commercial Identity Management and Single-Sign On (SSO) application from
Atlassian that lets you manage single user accounts across multiple products. It lets you manage both
an internal database of users, groups and roles, and integrate with external directories such as LDAP
directories or custom user stores.
Using the Jenkins Crowd plugin, you can use Atlassian Crowd as the source of your Jenkins users
and groups. Before you start, you need to set up a new application in Crowd (see Figure 7.12,
“Using Atlassian Crowd as the Jenkins Security Realm”). Just set up a new Generic Application called
“hudson” (or something similar), and step through the tabs. In the Connections tab, you need to provide
the IP address of your Jenkins server. Then map the Crowd directories that you will be using to retrieve
Jenkins user accounts and group information. Finally, you will need to tell Crowd which users from these
directories can connect to Jenkins. One option is to allow all users to authenticate, and let Jenkins sort
out the details. Alternatively, you can list the Crown user groups who are allowed to connect to Jenkins.
Figure 7.12. Using Atlassian Crowd as the Jenkins Security Realm
Once you have set this up, you need to install the Jenkins Crowd plugin, which you do as usual via the
Jenkins Plugin Manager. Once you have installed the plugin and restarted Jenkins, you can define Crowd
as your Security Realm in the main Jenkins configuration screen (see Figure 7.13, “Using Atlassian
Crowd as the Jenkins Security Realm”).