3.2.2 Integrating Crowd with Atlassian Bamboo

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.

Currently Crowd supports centralised authentication and single sign-on for Bamboo versions 1.2.2 and later.

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

1. Copy the Crowd integration libraries and configuration files to Bamboo's WEB-INF/lib directory.

   Copy From	Copy To
   CROWD/client/crowd-core-X.X.X.jar	Bamboo/webapp/WEB-INF/lib
   CROWD/client/crowd-atlassian-user-X.X.X.jar	Bamboo/webapp/WEB-INF/lib

2. Edit the \bamboo\webapp\WEB-INF\classes\atlassian-user.xml file to add the following repository:
   

   <crowd name="Crowd Repository" key="crowd" cache="true"/>
   

3. In the \bamboo\webapp\WEB-INF\classes\atlassian-user.xml file, comment out the Hibernate repository key:
   

   <!-- <hibernate name="Hibernate Repository" key="hibernateRepository" description="Hibernate Repository"/> -->
   

   
   

4. Please make sure that you leave Bamboo's External User Management turned off.
   
   
5. 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.

   1. Edit the \bamboo\webapp\WEB-INF\classes\seraph-config.xml, changing the authenticator node to read:

      <authenticator class="com.atlassian.crowd.integration.seraph.BambooAuthenticator"/>
      

   2. Bamboo will also require the latest version of Atlassian Seraph. Copy this JAR file into Bamboo's \bamboo\webapp\WEB-INF\lib directory and remove the old file.

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 via the Crowd Administration Console — for details on adding an application, see 3.2 Adding an Application. Make sure that you use the same password as configured in the crowd.properties file. 
  • 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 authorised addresses — see 3.5 Specifying an Application's Address or Hostname.
• 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 configured 'bamboo' application (see 3.4 Specifying which Groups can access an Application) or authentication attempts will fail.

    For more information please refer to the Bamboo documentation.

    
    

Related Topics  

• 3.1 Using the Application Browser
• 3.2 Adding an Application
  • 3.2.1 Integrating Crowd with Apache or Subversion
  • 3.2.2 Integrating Crowd with Atlassian Bamboo
  • 3.2.3 Integrating Crowd with Atlassian Confluence
  • 3.2.4 Integrating Crowd with Atlassian CrowdID
  • 3.2.5 Integrating Crowd with Atlassian FishEye
  • 3.2.6 Integrating Crowd with Atlassian JIRA
  • 3.2.7 Integrating Crowd with Jive Forums
    • 3.2.7.1 Jive SSO
  • 3.2.8 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.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.1 Documentation