Primary
Select the preferred Type from the two options available in the drop-down list: OpenLDAP and ActiveDirectory. Depending on this selection, different settings will be configurable in the following steps.
| Setting | Description | Type/required |
|---|---|---|
| LDAP URL | The URL of the LDAP server. Note: Use
ldaps for a secure connection. For example:
ldaps://192.0.2.0.
|
Input/Required for both OpenLDAP and ActiveDirectory |
| Bind DN | User-specified value for the Bind DN to validate the principal user. For example: cn=Admin, cn=Users, dc=netreg, dc=bcn, dc=com. | Input/Required for both OpenLDAP and ActiveDirectory |
| Bind password | Password used to access Bind. | Input/Required for both OpenLDAP and ActiveDirectory |
| Test Bind | Option to validate Bind DN parameters. | Button/Optional |
| Search base DN | Enter the LDAP search base DN using the attribute for the environment. For example: ou=people,dc=bcn,dc=com | Input/Required for both OpenLDAP and ActiveDirectory |
| Search groups base DN | Input/Required for OpenLDAP | |
| User prefix | Enter the name of the LDAP attribute that is used to find
users. Note: Enter uid for OpenLDAP and
sAMAccountName for ActiveDirectory.
|
Input/Required for both OpenLDAP and ActiveDirectory |
| Search filter | Set the LDAP search filter to specify the object class of user objects in your directory. | Input/Required for both OpenLDAP and ActiveDirectory |
| Test account username | Enter ActiveDirectory/OpenLDAP username that should be validated if it is allowed to register. | Input/Optional for both OpenLDAP and ActiveDirectory |
| Test account password | Enter ActiveDirectory/OpenLDAP password of a user that should be validated if it is allowed to register. | Input/Optional for both OpenLDAP and ActiveDirectory |
| Validate test account | Option to validate given ActiveDirectory/OpenLDAP account. | Button/Optional |
Sencodary server can be set in the same way to serve as a backup authenticator in case that connection to primary fails. If a Secondary server is added and the connection with the Primary fails, the system will try to connect to the Secondary in order to continue using DRP without interruptions.
Groups Settings
To define each of the LDAP groups, set the following parameters:
| Setting | Description | Type/required |
|---|---|---|
| Group name | Enter the Common Name (not Distinguished Name) of an LDAP group that corresponds to each DRP administrative group. The same group name must exist on the LDAP server. | Input/Required for Admin, but optional for Junior Admin and Report group. |
| Restrict search (optional) | Enter the search criteria that the group cannot use. For
example:
|
Input/Optional |
| Read-only access | Disabled by default, so members of this group are able to register new and make changes to existing devices in the pools. If enabled, members of this groups will not be able to register new devices or make changes to devices currently in the pools. | Toggle/Optional |
| Allow DHCP Reservation | When enabled, both dynamic and reserved registrations can be used by this LDAP group. If disabled, only dynamic registration will be used when Admins of this group are registering new devices. | Toggle/Optional |
| Delete blocklist devices | If enabled, members of this group are able to delete a blocklisted device. Disable it to prevent members of the group from deleting blocklisted devices and display an error message instead. | Toggle/Optional |
Tip:
Use the same settings to define a secondary authentication server and two additional user groups.