...
Sync LDAP Properties
Configuring Sync LDAP
Image Added
Image Removed
Figure 1: Configure Sync LDAP
Image Added
Image Removed
Figure 2: Sync Organization Enabled
| Name | Description / Sample Value |
|---|
| URL | ldap://IP_ADDRESS:389 |
Admin Username (Principal) | cn=admin,dc=joget,dc=org |
Admin Password (Credential) | Input the admin password for your LDAP/AD. |
| Root DN | Set the root DB, for example "eg. DC=Joget,DC=org". |
| Sync Organization | | Panel |
|---|
| borderColor | purple |
|---|
| borderWidth | 1 |
|---|
| titleBGColor | #ddccff |
|---|
| borderStyle | solid |
|---|
| title | New Feature |
|---|
| This is a new feature in Joget DX. |
Perform synchronization not just to user objects, but to the whole organizational structure including Group, Department, Grade as well. By enabling this feature, you will need to configure the following as well. | Name | Description / Sample Value |
|---|
| Organization ID | Declare a organization ID to bind all the users synced from LDAP with. If the organization declared does not exists in Joget, a new one will be created. | | Organization Name | Declare a organization name to bind all the users synced from LDAP with. If the one declared here is not the same as the existing one in Joget, it will be updated with the value set here. |
Please refer to documentation for setting up Group, Department, and Grade in LDAP Directory Manager. |
| Auto schedule sync? | | Panel |
|---|
| borderColor | purple |
|---|
| borderWidth | 1 |
|---|
| titleBGColor | #ddccff |
|---|
| borderStyle | solid |
|---|
| title | New Feature |
|---|
| This is a new feature in Joget DX. |
Clicking this checkbox to automatically sync your LDAP on a schedule, will display additional options as follows: - Sync Interval (Hour)
- Sync Initial Start Time (HH:mm)
|
User
Image Removed
Image Added
Figure 2: User Properties
| Name | Description / Sample Value |
|---|
| 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". |
|
| 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
Image Added
Image Removed
Figure 3: Employment Properties
| Name | Description / Sample Value |
|---|
| Attribute Mapping - Employee Code | employeeCode |
| 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
Image Removed
Image Added
Figure 4: Admin Role Properties
| Name | Description / Sample Value |
|---|
| Admin Role Base DN | Set the Admin Role Base DN |
| 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
Image Added
Image Removed
Figure 5: Advance Properties
...