Crowd 2 Plugin

Plugin Information

Plugin ID crowd2
Latest Release 1.5-h-3
Latest Release Date May 6, 2014
Plugin Central Plugin Central 3.2
Sources Github
Support Eclipse Hudson Forum
Issue Tracking Eclipse Bugzilla
Hudson Core (latest) 3.3.3

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. has more information on how to configure applications in Crowd.

Be sure to also allow connections to Crowd from the server Hudson runs on.

Next you need to configure a group that contains all users that are allowed to login into Hudson. has more information how to manage users, groups and roles.

Once you have the application and group configured in Crowd, you can enable Crowd-based security in Hudson on the "Manage Hudson" 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 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 Hudson 2.1.x and Crowd 2.3.x, but was built using Hudson core 1.398 so it should work with Hudson >= 1.398.

This plugin uses Crowd REST APIs for connecting to Crowd and therefore requires Crowd >= 2.1
(see 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 all open issues of the "Crowd Plugin". (If you look at the issue navigator, there are only five, but they are quite old; three of them even older than one year. Looking at the source code at GitHub (, there doesn't seem to be much activity trying to fix them).

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 History

Version 1.5 (Aug 23, 2012)

Version 1.4 (only released for Jenkins)

  • Upgrade commons-httpclient version to 3.1.

Version 1.3 (Oct 27, 2011)

Fixed the following bugs:

  • Crowd2 doesn't always show full user name (see JENKINS-11418)
  • Single-sign-on isn't working correctly in the Crowd 2 plugin (see JENKINS-11507)

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.
    This version was not correctly published to the plugin repository at that time, but should now be available.

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 Hudsons console output because they are logged with log level FINE or below. See here how to enable them (the plugin uses logger classes de.theit.hudson.crowd.XXX).

Version 1.0 (Sep 21, 2011)

  • Initial release


tier3-hudson-plugin tier3-hudson-plugin Delete
plugin-user plugin-user Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.