Configuring the Caching of your LDAP Repository

1. Click the 'Administration' link in the top navigation bar.
2. ファイル .../webapp/WEB-INF/classes/atlassian-user.xml を編集します。
3. Set the property cache="false" on your LDAP repository, as shown in the example below:

         
   <ldap key="myLdapRepository" name="LDAP Repository@hecate.atlassian.com" cache="false">
             <host>hecate.atlassian.com</host>
             <port>389</port>
   

1. ファイル .../webapp/WEB-INF/classes/atlassian-user.xml を編集します。
2. Set the property cache="true" on your LDAP repository as shown in the example below:

         
   <ldap key="myLdapRepository" name="LDAP Repository@hecate.atlassian.com" cache="true">
             <host>hecate.atlassian.com</host>
             <port>389</port>
   
   

1. Edit the file .../webapp/WEB-INF/classes/ehcache.xml.
2. Find the cache that you wish to edit. Examples of each of the caches are described in the Configuring Caches for Users and Configuring Caches for User Groups sections below.
3. Modify the cache, as desired. The following properties can be configured for each cache:

• maxElementsInMemory (mandatory) - Sets the maximum number of objects that will be created in memory
• eternal (mandatory) - Sets whether elements are eternal. If eternal, timeouts are ignored and the element is never expired.
• timeToIdleSeconds (optional) - Sets the time to idle for an element before it expires. i.e. The maximum amount of time between accesses before an element expires. This is only used if the element is not eternal. A value of 0 means that an Element can idle for infinity. The default value is 0.
• timeToLiveSeconds (optional) - Sets the time to live for an element before it expires i.e. The maximum time between creation time and when an element expires. This is only used if the element is not eternal. A value of 0 means that an Element can live for infinity. The default value is 0.

Configuring Caches for Users

In each of the examples below, replace myLdapRepository with the key of the repository specified in atlassian-user.xml

• LDAPUserManagerReadOnly.*.users

  LDAPUserManagerReadOnly.*.users stores the individual users, if you have difficulties with Bamboo picking up new user additions in the LDAP repository you will need to alter the configuration of this cache. In the example below, the users will expire after 5 minutes.

  <cache name="com.atlassian.user.impl.ldap.LDAPUserManagerReadOnly.myLdapRepository.users"
           maxElementsInMemory="500"
           eternal="false"
           timeToIdleSeconds="300"
           timeToLiveSeconds="300"
     />
  

• LDAPUserManagerReadOnly.*.users_ro

  LDAPUserManagerReadOnly.*.users_ro stores whether or not the users are read only. This will have no effect on the functionality of Bamboo, but you may wish to modify this cache for performance and memory tuning purposes.

  <cache name="com.atlassian.user.impl.ldap.LDAPUserManagerReadOnly.myLdapRepository.users_ro"
           maxElementsInMemory="500"
           eternal="false"
           timeToIdleSeconds="300"
           timeToLiveSeconds="300"
     />
  

• LDAPUserManagerReadOnly.*.repository

  LDAPUserManagerReadOnly.*.repository stores which repository the user belongs to. Bamboo does not yet support multiple repositories, so modifying this cache will have no effect on functionality. However, you may wish to modify this cache for performance and memory tuning purposes.

  <cache name="com.atlassian.user.impl.ldap.LDAPUserManagerReadOnly.myLdapRepository.repository"
           maxElementsInMemory="500"
           eternal="false"
           timeToIdleSeconds="300"
           timeToLiveSeconds="300"
     />
  

Configuring Caches for User Groups

In each of the examples below, replace myLdapRepository with the key of the repository specified in atlassian-user.xml

• LDAPGroupManagerReadOnly.*.groups

  LDAPGroupManagerReadOnly.*.groups stores the available groups in LDAP. If you wish Bamboo to pick up changes made to groups, then you will need to configure this cache appropriately.

  <cache name="com.atlassian.user.impl.ldap.LDAPGroupManagerReadOnly.myLdapRepository.groups"
           maxElementsInMemory="500"
           eternal="false"
           timeToIdleSeconds="300"
           timeToLiveSeconds="300"
     />
  

• LDAPGroupManagerReadOnly.*.groups_hasMembership* and *LDAPGroupManagerReadOnly.*.groups_getGroupsForUser

  The LDAPGroupManagerReadOnly.*.groups_hasMembership and LDAPGroupManagerReadOnly.*.groups_getGroupsForUser caches store the associations between users and groups. If you wish Bamboo to pick up changes made to group memberships then you will need to configure these caches appropriately.

  <cache name="com.atlassian.user.impl.ldap.LDAPGroupManagerReadOnly.myLdapRepository.groups_hasMembership"
           maxElementsInMemory="500"
           eternal="false"
           timeToIdleSeconds="300"
           timeToLiveSeconds="300"
     />
  <cache name="com.atlassian.user.impl.ldap.LDAPGroupManagerReadOnly.myLdapRepository.groups_getGroupsForUser"
           maxElementsInMemory="500"
           eternal="false"
           timeToIdleSeconds="300"
           timeToLiveSeconds="300"
     />
  

• LDAPGroupManagerReadOnly.*.repositories

  LDAPGroupManagerReadOnly.*.repositories stores which repository the group belongs to. Bamboo does not yet support multiple repositories, so modifying this cache will have no effect on functionality. However, you may wish to modify this cache for performance and memory tuning purposes.

  <cache name="com.atlassian.user.impl.ldap.LDAPGroupManagerReadOnly.myLdapRepository.repositories"
           maxElementsInMemory="500"
           eternal="false"
           timeToIdleSeconds="300"
           timeToLiveSeconds="300"
     />