Configuring LDAP for authorization

Prev Next

If you configured an LDAP server to authenticate users, you can configure LDAP mappings for authorization by using the appliance CLI:

When the appliance needs to determine the identity of the user, the Subject Alternative Name (SAN) extension with the User Principal Name (UPN) extension in the certificate can be used as an identifier when matching the certificate to an entry in the Active Directory (AD), which is supported by the LDAP protocol.

When the certificate is validated, the AD server uses the Principal Name field (Principal Name=user@fully.qualified.domain.name) in the SAN with the UPN of the certificate to search for the user in the Active Directory. The server permits or denies access to the Web UI based on the matched fields.

The user schema name and login name for the LDAP attribute are used to match the configured certificate authorization field. An administrator can configure the LDAP record to map the login name. An administrator can define an LDAP search filter in the configuration that controls which users can log in using a certificate and then can be authorized using LDAP.

Prerequisites