Crowd 2 Integration2.0.2Minimum Jenkins requirement: 2.89.3ID: crowd2
View Crowd 2 Integration on the plugin site for more information.
This plugin is up for adoption. The maintainer is looking for a co-maintainer or successor. Click here to learn more!
Crowd 2 Plugin
This plugin enables use of Atlassian Crowd >= 2.1.x as an authentication source.Crowd is a commercial identity management and Single Sign-On (SSO) application.
To configure the plugin, you first need to create a new application in Crowd. https://confluence.atlassian.com/crowd/adding-an-application-18579591.html has more information on how to configure applications in Crowd.
Be sure to also allow connections to Crowd from the server Jenkins runs on.
Next you need to configure a group that contains all users that are allowed to login into Jenkins. https://confluence.atlassian.com/crowd/managing-users-and-groups-193223.html has more information how to manage users and groups.
Once you have the application and group configured in Crowd, you can enable Crowd-based security in Jenkins on the "Manage Jenkins" page. Enter the URL of your Crowd server (will typically end with .../crowd) as well as the application name, password and group name you configured in Crowd.
Click on the "Check Connection" button to ensure that your connection credentials are valid.
Crowd supports nested groups, i.e. groups which contain other groups as members and groups that are members of other groups (see http://confluence.atlassian.com/display/CROWD/Nested+Groups+in+Crowd). If you want to use this feature, click on the "Advanced..." button and enable it. This may degrade performance, depending on your server configuration.
This plugin doesn't support Crowd roles. As long as there's not enough interest, it's unlikely that they are supported in a future version because they are deprecated since Crowd 2.0 (see here for details).
This plugin has been tested with Jenkins 1.431 and Crowd 2.3.x, but was built using Jenkins core 1.398 so it should work with Jenkins >= 1.398.
This plugin uses Crowd REST APIs for connecting to Crowd and therefore requires Crowd >= 2.1
(see http://developer.atlassian.com/display/CROWDDEV/Crowd+REST+APIs). If you have an older Crowd server, use the older "Crowd Plugin" instead.
Is Single-Sign-On (SSO) supported?
Yes :-) That was the main reason I wrote this plugin.
What's the difference between this plugin and "Crowd Plugin"?
Apart from SSO this plugin contains fixes for almost all open issues of the "Crowd Plugin". (If you look at the issue navigator, there are actually seven; five of them are almost or even older than one year. Looking at the source code at GitHub (https://github.com/jenkinsci/crowd-plugin), there doesn't seem to be much activity trying to fix them). I have to admit that I haven't tested JENKINS-9924 so far, i.e. what happens when the Crowd server is down. This will be done in the near future.
A more technically answer is that this plugin code was written from scratch using a different API to connect to the Crowd server, i.e. the Crowd REST APIs. These are recommeded by Atlassian for long-term compatibility.
In contrary, the "Crowd Plugin" uses Crowd's Java integration libraries that have the disadvantage that one perhaps has to re-compile the source code when a new Crowd release is available and one has to update these libraries.
Why do I have to choose a group for users?
To restrict the number of your Crowd users that are allowed to login. I thought it's cool to have such a feature because for example Confluence and JIRA, other well known products from Atlassian, also work that way.
Is there Localization support?
Actually only German localization is included. If you can translate a couple of messages and info texts into other languages, please send me a note, and I'll include them in a newer version.
Version 2.0.1 (Sep 25, 2018)
Version 2.0.0 (Jul 23, 2018)
- JENKINS-16703 - Too many periodic requests to Crowd server
- JENKINS-27070 - Plenty of "SEVERE: Host connection pool not found, hostConfig=HostConfiguration"
- JENKINS-40472 - Crowd2 plugin should allow blanks in parameter 'Restrict groups'
- Added possibility to enable caching to reduce remote calls to Crowd
Version 1.8 (Aug 1, 2014)
- [JENKINS-23208] Fixed trace with enabled "remember me" checkbox.
- isAuthenticated() in /whoAmI page is now true.
Version 1.7 (Apr 23, 2014)
- [JENKINS-21852] Added http proxy configuration.
- [JENKINS-18791] Session validation interval saved from ui.
- [JENKINS-13279] Don't use ssoTokenHelper, work with Embedded Crowd in Jira.
- [JENKINS-16703] More options for connection configuration.
- Updated rest-api library to 2.7.1
Version 1.6 (Nov 23, 2013)
Note: check that your group list uses CSV separator and you have SSO checkbox enabled (if you use it).
- pull #3 Fixed bug whereby bogus user IDs were created that included display names. When upgrading, manual cleanup of
$JENKINS_HOME/users/may be required.
- JENKINS-15509: Don't require group.
- JENKINS-15753: Allow spaces in group names.
- JENKINS-19212: Make "useSSO" optional.
- Updated rest-api library to 2.6.6.
Version 1.5 (Aug 23, 2012)
- JENKINS-11829: Support more than one group
- JENKINS-12339: misspelling in error message
- JENKINS-13547: Jenkins runs extremely slow with remote crowd server
Version 1.4 (Nov 25, 2011)
- Upgrade commons-httpclient version to 3.1.
Version 1.3 (Oct 27, 2011)
Fixed the following bugs:
- JENKINS-11418: Crowd2 doesn't always show full user name
- JENKINS-11507: Single-sign-on isn't working correctly in the Crowd 2 plugin
Version 1.2 (Oct 19, 2011)
- Fixed a problem that prevented you at least from adding pre- or post build steps when reconfiguring a build job.
- Added some debug log messages.
Version 1.1 (Oct 11, 2011)
- Fix for a problem that I discovered in combination with the Email-ext plugin: Sending emails to the logged-in user was not possible because a lookup operation in the Crowd server for details about a user failed.
- The Crowd user Id is now shown besides the display name of the logged-in user.
Added more debug log messages.
The debug log messages are usually not shown in Jenkins' console output because they are logged with log level FINE or below. See here how to enable them (the plugin uses logger classes
Version 1.0 (Sep 23, 2011)
- Initial release