Page tree
Skip to end of metadata
Go to start of metadata

Linchpin User Profiles - Documentation

Create a meaningful and up to date profile

See the documentation for your Release

Old version

This documentation refers to an old version of the Custom User Profile. The latest version uses the Confluence build-in LDAP configuration. See: CUP - Administration Guide 1.7  

LDAP Configuration

In Administration Console select "LDAP Configuration" under "Extended User Profile".

Insert the required data to enable the plugin to load user profile data from LDAP if possible.

In Release 1.3 there is furthermore a Quicktest-Button to test your connection, before you actually synchronizing your data.

 

Server Settings

PropertyExplanationExample
HostHostname of the server running LDAP. Mandatory.
ldap.example.com
PortPort number for LDAP host. Mandatory. Default: 389
389
Bind DN or userBind DN or user for LDAP connection.
user@domain.name
cn=user,dc=domain,dc=name
PasswordPassword for LDAP connection.
secret

Search Settings

PropertyExplanationExample
Base DNRoot node in LDAP from which to search for users and groups. Mandatory.
cn=users,dc=example,dc=com
User AttributeUnique user attribute representing Confluence user name. Mandatory.
uid
User Update Search Filter

LDAP query filter for updating users. Mandatory.

To use the configured date (see section LDAP sync) insert place holder [last_sync_timestamp]

(&(objectClass=person)(modifyTimestamp>=[last_sync_timestamp]))

 LDAP sync

PropertyExplanationExample
Last LDAP sync date

If the marker [last_sync_timestamp] in User Update Search Filter is set, the marker is replaced with this date. It is formatted with Pattern for last modification. The date is automatically updated after successful synchronization.

  • Format: dd-MM-yyyy HH:mm:ss
  • If the field is left blank, 1970-01-01 00:00:00 will be assumed.
23-05-2010 15:00:00
Pattern for last modificationPattern to format last modification date in LDAP User Update Search Query.
yyyyMMddHHmmssZ

 

These configurations are used to create an LDAP connection when

  • a user clicks "Update profile" in his or her profile page.
  • the synchronization job is triggered (either automatically or manually by an administrator). See: Scheduled profile update job

 

  • No labels