...
| Name | Description / Sample Value | Screen (Click to view) |
|---|
| User Base DN | Set the user base DN property. | Info |
|---|
| If you set the "User Base DN" to your LDAP Root DN, it means that the search will start from the Root DN until it finds all the results that matched the search filter. So, setting the "User Base DN" precisely is very important as it will decide where the search is starting from. It will save all the unnecessary search between the Root DN to your "User Base DN". | Code Block |
|---|
| DC=joget,DC=org |
| Code Block |
|---|
| title | Under the Root DN, you have the following DN: |
|---|
| DC=HR,DC=joget,DC=org
DC=Product Department,DC=joget,DC=org
DC=Operation,DC=joget,DC=org
DC=Users,DC=joget,DC=org |
If your users are all under "DC=Users, DC=joget,DC=org", you should set this to "User Base DN".
By doing this, it will not go through all the other entries and it's child entries before reaching "DC=Users, DC=joget,DC=org". |
|
Figure 2: User Properties
|
| User Import Search Filter | (objectClass=person) | Info |
|---|
| | Code Block |
|---|
| (&(objectClass=person)(|(cn=admin)(cn=cat)(cn=jack)(cn=john)(cn=jackie))) |
This mean all the LDAP entries which have "objectClass" attribute equals to "person" and "cn" attribute equals to either "admin", "cat", "jack", "john" or "jackie" are Joget users. So, when a login is performed by "admin", the search filter will add additional filter and become "(&(&(objectClass=person)(|(cn=admin)(cn=cat)(cn=jack)(cn=john)(cn=jackie)))(cn=admin))". You will notice an extra (cn=admin) is added to the search filter to make sure it return only the "admin" user. |
| Info |
|---|
| User license determines on how many eventual users (sorted alphabetically) from your LDAP/AD can log in into the system. You can make use of this attribute to control amount of users returned from your LDAP. |
More details at LDAP Directory Manager#ConfiguringTheUserImportSearchFilter. |
Attribute Mapping - Username | cn |
Attribute Mapping - First Name | givenName |
Attribute Mapping - Last Name | sn |
Attribute Mapping - Email | mail |
Attribute Mapping - Status | status |
Attribute Mapping - Time Zone | 8 |
Attribute Mapping - Locale | en_US |
Employment
| Name | Description / Sample Value | Screen (Click to view) |
|---|
| Attribute Mapping - Employee Code | employeeCode |  Image Modified
Figure 3: Employment Properties
|
| Attribute Mapping - Job Title | jobTitle |
| Attribute Mapping - Report To | Use this if an LDAP user that a user reports to is kept in LDAP user entry. eg. manager |
| Map To "Report To" Entry Attribute | Used together with "Attribute Mapping - Report To". eg. distinguishedName |
| Attribute Mapping - Metas | Additional attributes to retrieve using #user.USERNAME.meta.KEY# or #currentUser.meta.KEY# |
Admin Role
| Name | Description / Sample Value | Screen (Click to view) |
|---|
| Admin Role Base DN | Set the Admin Role Base DN |  Image Modified
Figure 4: Admin Role Properties
|
| Admin Role Import Search Filter | eg. (objectClass=group) |
| Attribute Mapping - Users | Use this if the admin role of user(s) is kept in LDAP entry. eg. member |
| Map To LDAP User Entry Primary Attribute | Map To LDAP User Entry Primary Attribute |
Advance
| Name | Description / Sample Value | Screen (Click to view) |
|---|
Result Size Per Paged Search | 100 | 
Figure 5: Advance Properties |
| Debug Mode | Checked | Info |
|---|
| The Debug Mode is highly recommended to be turned on when configuring the LDAP plugin for the first time.
When debug mode is on, you can find all the search queries performed by the directory manager. They will all be logged into the log file. From there, you can observe the search filter string and improve the accuracy and performance of the lookup. |
|
Related Documentation
LDAP Directory Manager
Automatically synchronize LDAP based on schedule using BeanShell Java code.
...