Raritan EMX2-111, Руководство пользователя

Страница: 485 / 565

Appendix E: LDAP Configuration Illustration
473
Field/setting Do this...
Bind DN,
Bind Password,
Confirm Bind Password
Skip the three fields because of anonymous bind.
Base DN for Search Type
dc=techadssl,dc=com
as the starting point where your
search begins on the AD server.
Login Name Attribute
Ensure the field is set to
sAMAccountName
because the LDAP
server is Microsoft Active Directory.
User Entry Object Class Ensure the field is set to
user
because the LDAP server is Microsoft
Active Directory.
User Search Subfilter The field is optional. The subfilter information is also useful for
filtering out additional objects in a large directory structure. In this
example, we leave it blank.
Active Directory Domain Type
techadssl.com
.
4. Click Add Server.The LDAP server is saved.
5. In the Authentication Type field, select LDAP.
6. Click Save. The LDAP authentication is activated.
Note: If the EMX clock and the LDAP server clock are out of sync, the
installed TLS certificates, if any, may be considered expired. To ensure
proper synchronization, administrators should configure the EMX and
the LDAP server to use the same NTP server(s).
Step D. Configure Roles on the EMX Device
A role on the EMX device determines the system permissions. You must
create the roles whose names are identical to the user groups created
for the EMX on the AD server or authorization will fail. Therefore, we will
create the roles named
EMX_User and EMX_Admin on the EMX device.
In this illustration, we assume:

Users assigned to the EMX_User role can only access the EMX
device and view settings.

Users assigned to the
EMX_Admin role can both access and
configure the EMX device because they have the Administrator
permissions.
To create the EMX_User role with appropriate permissions
assigned:
1. Choose User Management > Roles.