--- title: "Configure PKI, PKI with LDAP, or Active Directory authentication" slug: "configure-pki-pki-with-ldap-or-active-directory-authentication-2" tags: ["Install and Get Started", "NDR 4.x", "Customer", "Network Security"] updated: 2026-11-17T09:23:23Z published: 2026-11-17T09:23:23Z canonical: "docs.trellix.com/configure-pki-pki-with-ldap-or-active-directory-authentication-2" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Configure PKI, PKI with LDAP, or Active Directory authentication Public Key Infrastructure (PKI) authentication verifies a user's identity using a digital certificate, often from a smart card, such as a Common Access Card (CAC) or Personal Identity Verification (PIV). See [Common Access Card (CAC) for certificate authentication](/network-and-platform/docs/common-access-card-cac-for-certificate-authentication-3) for more detailed information. This section explains when to choose PKI, PKI w/ LDAP, or PKI w/ Active Directory as authentication methods and to how to configure them. **Prerequisites**: Download a CA certificate bundle or add an imported certificate to an existing bundle from a specified URL. For details, see [Uploading a Custom CA-signed Web Server certificate](/network-and-platform/docs/uploading-a-custom-ca-signed-web-server-certificate-2). 1. Log in to the system as `npadmin` using the system's IP address or FQDN. For example: `$ ssh npadmin@10.1.0.1` Or, `$ ssh npadmin@exampleFQDN` 2. Enter privileged mode: `npadmin@hostname > enable` 3. Enter the admin password. `[sudo] password for npadmin: <password>` 4. Enter configuration mode: `npadmin@hostname# configure system` 5. Open the authentication configuration: ``` npadmin@hostname(config)# authentication 1: Authentication Method = pam 2: Configure Current Authentication Method ----------------------------------------         Q: Save changes and exit C: Cancel changes and exit         Select which option you would like to change using the index number: ``` 6. Type `1` to open the authentication mechanism menu. - Press `6` to choose `PKI` which authenticates user information on LDAP or AD servers. - Press `7` for `PKI w/ LDAP`, or `8` for `PKI w/ Active Directory` which enable user information to be picked up from a valid certificate for further authentication on LDAP or AD servers. ``` Authentication Mechanisms: 1: PAM 2: LDAP 3: RADIUS 4: TACACS+ 5: Active Directory 6: PKI 7: PKI w/ LDAP 8: PKI w/ Active Directory C: Cancel changes and exit Select the authentication method to use: 7 ``` When you have selected PKI or PKI w/ LDAP or PKI w/ Active Directory as the authentication method, the following options appear in the CLI: ``` 1: Authentication Method = pki or pki-ldap or pki-ad 2: Configure Current Authentication Method 3: Flush AD/LDAP passwd and group cache ---------------------------------------- Q: Save changes and exit C: Cancel changes and exit Select which option you would like to change using the index number: ``` 7. Press `2` to select `Configure Current Authentication Method`. The PKI configuration menu is displayed on the CLI: ``` PKI Configuration: 1. Status = disabled 2. OCSP Verification URL = 3. Certificate Revocation List = 4. Appliance Certificate = 5. Client CA Certificate = 6. Delete Client CA Certificate ---------------------------------------- Q: Save changes and go to the next menu C: Cancel changes and go to the next menu Enter your choice: ``` Make changes to the following fields, as required: 1. `Status`: Type `1` CAC / PKI authentication status which can be set to `disabled` (selected by default), `enabled`, and `optional`. Check [how to enable or disable CAC/PIV for certificate authentication](/network-and-platform/docs/enabling-or-disabling-cac-piv-for-certificate-authentication-2) and [logging in to the Web UI with certificate authentication](/network-and-platform/docs/logging-in-to-the-web-ui-with-certificate-authentication-2) for details. > [!WARNING] > Important > > You must upload a CA certificate to the appliance under the transfer folder before enabling `Status`. 2. `OCSP Verification URL`: Type `2` to set the URL of the OCSP server used to verify the revocation status of certificates in real time. If the certificate is part of the revocation list, it will be blocked. See [how to add OCSP Verification URL](/network-and-platform/docs/adding-the-ocsp-url-using-the-configuration-menu-2) for details. 3. `Certificate Revocation List`: A Certificate Revocation List (CRL) is a file maintained locally that lists revoked digital certificates to allow for their offline validation. To work on the CRL, type `3` and press `Enter`. The following CRL configuration options appear on CLI: ``` CRL Configuration: 1: CRL Retrieval URL = 2: CRL Retrieval interval (hours between refresh) = 1 3: Upload CRL file = 4: View CRL contents 5: Delete CRL file ---------------------------------------- Q: Save changes and exit C: Cancel changes and exit Enter your choice: ``` Configure the fields in the following order. Enter `Q` to save the changes and exit the CRL configuration menu and return to PKI authentication configuration menu, or `C` to cancel. 1. `Upload CRL file`: Type `3` to [upload a local CRL file](/network-and-platform/docs/adding-a-local-crl-file-using-the-configuration-menu-2). 2. `CRL Retrieval URL`: Type `1` to [enter the URL of the direct path to the certificate file for file updates](/network-and-platform/docs/adding-the-ocsp-url-using-the-configuration-menu-2). 3. `CRL Retrieval interval`: Type `2` to [configure a CRL retrieval interval](/network-and-platform/docs/refreshing-a-crl-file-using-the-configuration-menu-2) (in hours). 4. `View CRL contents / Delete CRL file`: Type `4` to review the configured CRL contents or type `5` if you want to [delete a CRL file](/network-and-platform/docs/deleting-a-crl-file-using-the-configuration-menu-2). 4. `Appliance Certificate`: On the PKI authentication configuration menu, type `4` to set the SSL/TLS certificate used by the appliance for secure communication. 5. `Client CA Certificate`: To define the trusted CA for client certificate validation, type `5` in the PKI authentication menu and provide the certificate's filename, such as `ca-chain.pem`. 6. `Delete Client CA Certificate`: On the PKI authentication configuration menu, type `6` if you want to remove the stored client CA certificate from the appliance. Type `Y` to confirm. 7. Enter `Q` to save the configuration changes. You will be redirected to LDAP authentication configuration menu with the same configuration options as discussed in the [Configure LDAP and Active Directory authentication](/network-and-platform/docs/configure-ldap-or-active-directory-authentication-2) section along with the following fields. When done, enter `Q` to save the configuration changes. After the configuration, it might look like the following: ``` 1: LDAP Server(s) = 10.x.x.x:3xx 2: Base DN = CN=Users,DC=piblr,DC=quality 3: Bind DN = CN=administrator,CN=Users,DC=piblr,DC=quality 4: Bind Password = ********** 5: Base Password = ********** 6: Base Group = CN=Users,DC=piblr,DC=qa 7: LDAP/AD UIAPI Group = uiapigrp 8: LDAP/AD Sudo Group = sudogrp 9: LDAP/AD SSH Group = sshgrp 10: LDAP Domain SID = None 11: LDAP USE SSL = False 12: LDAP USE STARTTLS = False 13: Ignore Constraints = false 14: Enable LDAP Group Traversal = True 15: Certificate Identity Field = x509-cert-subject-cn 16: Certificate-to-LDAP Mapping Attribute = cn 17: LDAP Username Attribute = sAMAccountName ``` 1. `Certificate Identity Field`: Type `15` to specify which field from the X.509 certificate is used to identify the user (such as x509-cert-subject, x509-cert-san-email, 509-cert-subject-cn etc.) See [Configuring the user attributes for certificate authentication](/network-and-platform/docs/configuring-the-user-attributes-for-certificate-authentication-3) for more details. 2. `Certificate-to-LDAP Mapping Attribute`: Type `16` to define the LDAP attribute (for example, CN) that the `Certificate Identity Field` is matched against for user lookup. 3. `LDAP Username Attribute`: Type `17` to specify the LDAP attribute (that is, sAMAccountName) used as the user’s login name during authentication. 8. (Optional) If you want to clear any cached credentials or group information previously configured, press `3` (`Flush AD/LDAP passwd and group cache`).