LDAP Server URL
Introduction:
LDAP Synchronization allows the Connect/Breeze Administrator to import user accounts and pertinent information existing in an external LDAP directory.
It provides the following benefits:
- If you already have an external authentication system with lots of user accounts in it, the Breeze/Connect Administrator doesnt have to manually create user accounts.
- The user doesnt have to come up with another user id and can use the same account that he/she already has been using.
Connect/Breeze can pull the data from any LDAP v3 compatible servers. These include openLDAP, Microsoft ActiveDirectory, SunONE LDAP and Novel eDirectory.
Configuration
The following tables provide the most common values that might be used to configure LDAP synchronization for ActiveDirectory.
Connection Settings
|
ldap://domain.controller.name:389 |
LDAP Connection Authentication Method |
Simple |
LDAP Connection Username |
CN=Administrator,CN=USERS,DC=YOUR,DC=DOMAIN,DC=COM |
LDAP Connection password |
Password |
LDAP Query Time out connection |
Blank |
Note: Substitute the name of your domain controller for "domain.controller.name" in the LDAP Server URL setting above. The same applies to the values for LDAP Connection Username setting too. For example:
CN=John Doe, CN=USERS,DC=ADOBE,DC=COM
User Profile Mapping
Login |
sAMAccountName |
First Name |
givenName |
Last Name |
sn |
|
|
BranchDN |
cn=USERS,DC=YOUR,DC=COMPANY,DC=COM |
Filter |
(objectClass=person) or (!(objectClass=group)) |
Subtree Search |
True |
Note: Substitute the value of the BranchDN setting for the valid branch DN from your ActiveDirectory. For example:
CN=USERS,DC=ADOBE,DC=COM
GroupProfile Mapping
Group Name |
sAMAccountName |
Group Member |
member |
Branch DN |
cn=USERS,DC=YOUR,DC=COMPANY,DC=com |
Filter |
(objectClass=group) |
Subtree Search |
True |
Note: Substitute the value of the BranchDN setting for the valid branch DN from your ActiveDirectory. For example:
CN=USERS,DC=ADOBE,DC=COM