Alternative LDAP connection for profile fields
By default the user directories configured in Confluence (ADMINISTRATION > USERS & SECURITY > User Directories) are used to fill the user profiles.
In some cases companies have two LDAPs for the same users, but with different information. A common use case would be to manage your users (name, password) and groups (confluence-admins) in a user directory managed by Confluence, but maintain user profile data (position, location etc.) in a different directory. If that's the case for you and you want to retrieve additional data for profile fields from an LDAP different to the one configured in confluence, you can configure a separate LDAP resource under (ADMINISTRATION > LINCHPIN USER PROFILES > DATA SOURCES).
Please note: If you configure an LDAP resource here, the LUP App will then use this resource exclusively to fill the fields you have configured for user profiles. It won't merge information with the LDAP configured in Confluence.
Configure a separate LDAP connection
The settings are pretty much the same as configuring a user directory in Confluence.
Please note: The configured LDAP access is strictly read-only.
|Host name of the server running LDAP
|Bind DN or user
|User to log in to LDAP
|firstname.lastname@example.org or cn=user,dc=domain,dc=name.
|Root node in LDAP from which to search for users and groups
|Unique user attribute representing Confluence user name
|User Update Search Filter
|Filter for updating users.
To use the configured date (see section LDAP sync) insert place holder [last_sync_timestamp]
|Use Paged Results
|Enable paging for search results and define the page sites according to your LDAP configuration
Clear LDAP Connection
- No labels