127
ï‚·
radius—Sends the user's ID and password a RADIUS server to be authenticated. The method
returns an error if the switch is unable to contact the server.
ï‚·
tacacs+— Sends the user's ID and password to a TACACS+ server to be authenticated. The
method returns an error if the switch is unable to contact the server.
ï‚·
none—No authentication is used. This method never returns an error.
ï‚·
deny
—
Access is denied. This method never returns an error.
An authentication method might require a user name and password to be supplied, a password only, or no
user information. Some methods return errors when authentication fails, while other methods do not. The
following table summarizes the method user name/password requirements and error behavior.
Table 4-1: Authentication Method Summary
You can use the same Authentication Profile for all access types, or select or create a variety of profiles
based on how a user attempts to access the switch management interface. Profiles can be applied to each of
the following access types:
ï‚·
Login—Authenticates all attempts to login to the switch.
ï‚·
Enable—Authenticates all attempts to enter Privileged EXEC mode.
ï‚·
Console—Authenticates access through the console port.
ï‚·
Telnet—Authenticates users accessing the CLI by using telnet
ï‚·
SSH—Authenticates users accessing the CLI by using an SSH client.
The following authentication profiles are configured by default:
ï‚·
defaultList—Method is LOCAL, which means the user credentials are verified against the
information in the local user database.
ï‚·
networkList—Method is LOCAL, which means the user credentials are verified against the
information in the local user database.
ï‚·
enableList—Method is ENABLE, followed by NONE, which means that if the enable password
is not configured access is granted. If the enable password is configured and user fails to
authenticate then access is not granted.
ï‚·
enableNetList — Method is ENABLE, followed by DENY, which means that if the enable
password is not configured access is denied. This list is applied by default for telnet and SSH.
In QNOS the enable password is not configured by default. That means that, by default,
telnet and SSH users will not get access to Privileged EXEC mode. However, a console user