--- title: "Defining the authentication order using the CLI" slug: "defining-the-authentication-order-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:07Z published: 2026-09-01T19:03:07Z canonical: "docs.trellix.com/defining-the-authentication-order-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. # Defining the authentication order using the CLI If you have multiple authentication tools that can be used for authentication, you can determine the order in which each tool is used to authenticate users against the appliance. For example, if you have an external LDAP server authenticating users, you can set the order to authenticate users first with LDAP, and then locally on the appliance itself. The order of the tools used is based on the sequence of tools added to the `aaa authentication login default` command. Prerequisites - Admin access To define the authentication order: 1. Go to CLI configuration mode: ``` hostname > enable hostname # configure terminal ``` 2. To specify the authentication tool order, use the following command: ``` aaa authentication login default ... ``` For example, if you want to set the authentication order to first authenticate against an LDAP server, second authenticate against a RADIUS server, and finally locally on the appliance, enter the following: ``` hostname # (config) aaa authentication login default ldap radius local ``` :