How to change the number of users synchronized from LDAP to Confluence

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.

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

Purpose

If you have connected Confluence to an LDAP directory for user and group management, you may want configure Confluence to synchronise a subset of users from LDAP rather than all users. There are two reasons why you might make this change:

  • Improving performance – If you have performance issues during the synchronisation process, you may be able to improve this by synchronising a subset of data instead.
  • Reducing your user count – You can synchronise a subset of users to Confluence from LDAP to reduce your user count. This will allow you to count fewer users against your Confluence license. See this page for information about other ways of reducing your user count: see Managing your Confluence License.

Solution

The procedure depends on how you initially set up your LDAP directory. If you have all your Confluence users in one organisational unit and your non-Confluence users in another organisational unit, then you can simply configure Confluence to synchronise users against a particular DN (distinguished name). However, if your setup is not so simple (for example, you have your Confluence users and non-Confluence users in the same node) you will need to define an LDAP filter to synchronise the relevant users. Both of these methods are outlined below.

Synchronising against Base DN, Additional User DN and Additional Group DN

  1. Log in as a Confluence system administrator.
  2. Choose Browse > Confluence Admin.
  3. Choose User Directories in the left-hand panel.
  4. Choose your LDAP directory from the list.
  5. Update the Base DN field, and optionally the Additional User DN and/or Additional Group DN to query the directory server as desired. For a description of these fields, see Connecting to an LDAP Directory.
    For example, if you have configured all of your Confluence users in the confluence-users organisational unit only, for your company at  mycompany.example.com , your configuration would look like this:
  • Base DN — dc=mycompany,dc=example,dc=com
  • Additional User DN — ou=confluence-users

Defining an LDAP filter

  1. Log in as a Confluence system administrator.
  2. Choose Browse > Confluence Admin.
  3. Choose User Directories in the left-hand panel.
  4. Choose your LDAP directory from the list.
  5. Update User Object Filter and/or Group Object Filter fields as desired. For a description of these fields, see Connecting to an LDAP Directory. The syntax for LDAP filters is not simple and your query will depend on how you have set up your LDAP directory.
    For example, if you have configured only Confluence groups to have 'confluence' in the CN, you can use a wildcard search in your filter to find them by setting the Group Object Filter = (&(objectCategory=group)(cn=*confluence*))

Pulling objects from more than one OU

 To pull users or groups from multiple OUs do not attempt to define more than one OU in the Base DN field. Rather, use an LDAP filter as explained under the heading Matching Components of Distinguished Names in the article How to write LDAP search filters. This method will not work for Active Directory. Please see this article from Microsoft for more information: http://msdn.microsoft.com/en-us/library/cc223241.aspx

Related topics :

Last modified on Dec 18, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.