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
| Property | Explanation | Example |
|---|---|---|
| Host | Hostname of the server running LDAP. Mandatory. | ldap.example.com |
| Port | Port number for LDAP host. Mandatory. Default: 389 | 389 |
| Bind DN or user | Bind DN or user for LDAP connection. | user@domain.name cn=user,dc=domain,dc=name |
| Password | Password for LDAP connection. | secret |
Search Settings
| Property | Explanation | Example |
|---|---|---|
| Base DN | Root node in LDAP from which to search for users and groups. Mandatory. | cn=users,dc=example,dc=com |
| User Attribute | Unique 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 | (&(objectClass=person)(modifyTimestamp>=[last_sync_timestamp])) |
LDAP sync
| Property | Explanation | Example |
|---|---|---|
| Last LDAP sync date | If the marker
| 23-05-2010 15:00:00 |
| Pattern for last modification | Pattern 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