Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-17505

Use non eternal caching for LDAP by default

XMLWordPrintable

    • 0
    • 14

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      By default:

      • Caching is enabled in the LDAP documentation
      • LDAP specific cache configuration is commented out in <Bamboo installation directory>/atlassian-bamboo/WEB-INF/classes/ehcache.xml
      • defaultCache property "eternal" set to "true" which means that elements have no timeout

      As an effect of this configuration, the cache is only rotated once it reaches the maximum elements in memory.

      Problem Statement

      One of the possible issues that is most commonly faced in this scenario is that Bamboo does not update it's LDAP cache or information when LDAP is updated (example: user removed or password change) until a restart.

      Workaround

      To workaround this issue, users should configure LDAP specific caching as instructed in the below documentation:
      https://confluence.atlassian.com/bamboo/configuring-the-caching-of-your-ldap-repository-289277216.html

      Suggestion

      Use non-eternal caching for LDAP by default so that elements have a timeout and refreshed accordingly.

              Unassigned Unassigned
              dlee@atlassian.com Deric Lee (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: