This page last changed on Feb 26, 2007 by rosie@atlassian.com.

Atlassian's Bamboo integration server can quickly be configured to use the atlassian-user libraries to link in single or multiple directory servers through Crowd.

To configure the atlassian-user framework, perform the following:

  1. Copy the Crowd integration libraries and configuration files as described in the 3.2 - Client Configuration documentation.
  2. Edit the \bamboo\webapp\WEB-INF\classes\atlassian-user.xml file to add the following respository:
    <repository class="com.atlassian.crowd.integration.atlassianuser.CrowdRepository">
    	<classes>
    		<processor>com.atlassian.crowd.integration.atlassianuser.CrowdRepositoryProcessor</processor>
    		<userManager>com.atlassian.crowd.integration.atlassianuser.CrowdUserManager</userManager>
    		<groupManager>com.atlassian.crowd.integration.atlassianuser.CrowdGroupManager</groupManager>
    		<authenticator>com.atlassian.crowd.integration.atlassianuser.CrowdAuthenticator</authenticator>
    		<propertySetFactory>com.atlassian.crowd.integration.atlassianuser.CrowdPropertySetFactory</propertySetFactory>
    		<entityQueryParser>com.atlassian.crowd.integration.atlassianuser.CrowdEntityQueryParser</entityQueryParser>
    	</classes>
    </repository>


    You will need to comment out the Hibernate repository key

    <!-- <hibernate name="Hibernate Repository" key="hibernateRepository" description="Hibernate Repository"/> -->
  3. This step is only necessary if you wish to enable single sign-on:
    Enabling Single Sign-On
    Single sign-on (SSO) is optional when integrating Bamboo and other Atlassian products. To use centralised authentication do not configure Seraph based authentication.
    Edit the \bamboo\webapp\WEB-INF\classes\seraph-config.xml, changing the authenticator node to read:
    <authenticator class="com.atlassian.crowd.integration.seraph.BambooAuthenticator"/>

Bamboo's authentication and access request calls will now be performed using the atlassian-user Crowd plugin.

When utilising the atlassian-user and Crowd framework together with Bamboo, it is highly recommended that caching be enabled. Multiple redundant calls to the atlassian-user framework are made on any given request. These results can be stored locally between calls by enabling caching in the Crowd 'Options' menu. In doing so, Bamboo will obtain all necessary information for the period specified by the cache in minutes. If a security change or addition occurs in Crowd, these changes will not be visible in Confluence until the item cache expires.

Additional configuration steps:

  • Create the 'bamboo' application in the Crowd administration console. Make sure that you use the same password as configured in the crowd.properties file. More information on adding an application is available here
    • You will need to make sure you add the IP address of the client address, in this case Bamboo's IP address to the list of
  • Create a group bamboo-admin, through the Crowd console or directly in your directory server.
    • You will need to assign the bamboo-admin group to the newly configure 'bamboo' application through the Crowd administration console or authentication attempts will fail.
      For more information please refer to the Bamboo documentation.

There is no such file {{atlassian-user.xml when using }}bamboo 1.0-beta.

Posted by thomasvdv at Feb 01, 2007 23:42

This is fixed in 1.0-rc1

Posted by thomasvdv at Feb 02, 2007 17:18
Document generated by Confluence on Mar 08, 2007 18:50