Certain External Directory does not synchronize every user that matches the filter completely

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Problem

When setting up Confluence with External Directory, it is expected to have all users meeting the filter to be synchronized into Confluence completely.

However, the successful directory synchronization only synced a certain portion of users into Confluence instead.

Diagnosis

Environment

⚠️ External Directories below are known to have a limitation of search limit:

  • Oracle Sun ONE Directory

  • OpenLDAP

  • Jump Cloud LDAP-as-a-Service

Diagnostic Steps

  • Synchronization log looks fine in the atlassian-confluence.log with no failure log

  • However, the synchronization log appears to found a hard limit for the number of users to be synced (eg: 500, 2000, 10000, etc..) like the examples below:

    Sun ONE Directory

    1 2018-04-02 21:33:40,707 Caesium-2-4 INFO [directory.ldap.cache.RemoteDirectoryCacheRefresher] found [ 2000 ] remote users in [ 2284 ms ]

    Or

    Open LDAP

    1 2017-11-13 06:45:45 ... [c.a.c.d.ldap.cache.RemoteDirectoryCacheRefresher] found [ 500 ] remote users in [ 41 ms ]

    Or

    Jump Cloud

    1 2018-07-25 18:53:37,120 INFO [Caesium-1-3] [directory.ldap.cache.RemoteDirectoryCacheRefresher] findAllRemoteUsers found [ 10000 ] remote users in [ 16444 ms ]

Cause

There is some limitation from the LDAP that limits the number of users to be searched thus not all users within the filter will be synchronized to Confluence.

Solution

Resolution

Depends which LDAP you are using, look for the limitation that is applied and make the adjustment accordingly.

Oracle Sun ONE Directory

Refer to this Documentation and adjust the search-size-limit

Open LDAP

Refer to this Documentation and adjust the olcSizeLimit

Jump Cloud LDAP-as-a-Service

Contact the support for Jump Cloud to increase the limit

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.