...
Figure 1: Configure LDAP Directory Manager
| Warning |
|---|
|
Do not lock yourself out when you are configuring any Directory Manager plugin. Keep your browser session open and perform actual test in other machine/browser so that in case of any wrong configurations used, you can still continue to make amends. |
| Info |
|---|
|
User license determines how many eventual users (sorted alphabetically) from your LDAP/AD can login to the system. Make sure that you configure the plugin accordingly. |
Sample Configuration
Configure LDAP Directory Manager
| Name | Value |
|---|
| URL | - ldap://IP_ADDRESS:389
- ldaps://IP_ADDRESS:636
|
Admin Username (Principal) | cn=admin,dc=joget,dc=org |
Admin Password (Credential) | admin |
| DC=joget,DC=org |
| Infowarning |
|---|
| title | Don't lock yourself out | Administrative Access |
|---|
|
In case you have a misconfiguration and cannot login, you can make use of the credential set above ( You can fill in with the values you used for "Admin Username (Principal) " and "& Admin Password (Credential) ) " to login to the console if your mapping is not working properlyas the administrator. |
User
| Name | Value |
|---|
User Base DN | User Base DN | 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". |
|
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. |
|
Attribute Mapping - Username | cn |
Attribute Mapping - First Name | givenName |
Attribute Mapping - Last Name | sn |
Attribute Mapping - Email | mail |
Attribute Mapping - Status | |
Attribute Mapping - Time Zone | 8 |
Attribute Mapping - Locale | en_US |
...
| Name | Value |
|---|
Result Size Per Paged Search | 100 |
| 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. |
|