--- title: "Configuring an active directory server using the CLI" slug: "configuring-an-active-directory-server-using-the-cli-1" tags: ["File Protect (FX)", "Malware Analysis (AX)", "IAM", "Email Security - Cloud", "Network Security (NX)", "Email Security — Server", "Central Management System", "Helix Enterprise", "Endpoint Security (HX)", "Product Usage", "Install and Get Started", "Helix", "Intelligent Virtual Execution "] updated: 2026-09-01T19:03:12Z published: 2026-09-01T19:03:12Z canonical: "docs.trellix.com/configuring-an-active-directory-server-using-the-cli-1" --- > ## 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. # Configuring an active directory server using the CLI Because Active Directory (AD) supports the LDAP protocol, Trellix appliances can also authenticate through an AD server. The binding user or `bind-dn` as seen in the Trellix configuration is a read-only user that is used to query the directory structure starting from the `base-dn`. The `localUserNameFireEye` attribute is an addition that needs to be made above other attributes used by default on Active Directory. Adding the `localUserNameFireEye `as an attribute to the AD schema is not without risks. Refer to the following resource for more information: [https://technet.microsoft.com/en-us/library/2008.05.schema.aspx?pr=blog](https://technet.microsoft.com/en-us/library/2008.05.schema.aspx?pr=blog) ### Important The` localUserNameFireEye `attribute requires a non-administrator “binding user” for searching and browsing AD server records. Prerequisites - Admin access To configure Active Directory authentication: 1. Go to CLI configuration mode: ``` hostname > enable hostname # configure terminal ``` 2. Configure the host to send LDAP authentication requests. Use the following command: ``` ldap host ``` 3. Configure the LDAP user search base. Use the following command: ``` ldap base-dn ``` 4. Set the Distinguished Name used to bind to the server. Use the following command: ``` ldap bind-dn ``` 5. Configure the credentials used to bind to the server. Use the following command: ``` ldap bind-password ``` 6. Configure which attribute holds the login name. Use the following command: ``` ldap login-attribute sAMAccountName ``` `sAMAccountName` is a fixed value that replaces the`<uid>`attribute defined for LDAP authentication. 7. Save your changes: ``` hostname (config) # write memory ``` :