Hi,
Configure HWTACACS authentication on the firewall. Most accounts can be authenticated using HWTACACS. After login, account priorities are controlled by the HWTACACS server. However, when the user admin logs in to the system, HWTACACS authentication is not performed. Instead, local authentication is performed and the user priority level is 15. This does not meet the expectation. Why does the user admin skip HWTACACS authentication?
Here is the configuration:
#
hwtacacs-server template aaa
hwtacacs-server authentication x.x.x.x
hwtacacs-server authentication x.x.x.x secondary
hwtacacs-server authorization x.x.x.x
hwtacacs-server authorization x.x.x.x secondary
hwtacacs-server accounting x.x.x.x
hwtacacs-server accounting x.x.x.x secondary
hwtacacs-server source-ip x.x.x.x
hwtacacs-server shared-key cipher %^%#on(\GR>ov#dwIO'Z^xc:UU"
undo hwtacacs-server user-name domain-included
#
aaa
authentication-scheme default
authentication-scheme admin_local
authentication-scheme admin_radius_local
authentication-scheme admin_hwtacacs_local
authentication-scheme admin_ad_local
authentication-scheme admin_ldap_local
authentication-scheme admin_radius
authentication-scheme admin_hwtacacs
authentication-scheme admin_ad
authentication-scheme admin_ldap
authentication-scheme aaa
authentication-mode hwtacacs local
authorization-scheme default
authorization-scheme aaa
authorization-mode hwtacacs local
authorization-cmd 0 hwtacacs local
authorization-cmd 1 hwtacacs local
authorization-cmd 3 hwtacacs local
authorization-cmd 15 hwtacacs local
accounting-scheme default
accounting-scheme aaa
accounting-mode hwtacacs
accounting start-fail online
domain default
authentication-scheme aaa
accounting-scheme aaa
authorization-scheme aaa
hwtacacs-server aaa
manager-user admin
password cipher @%@%
service-type web terminal ssh
level 15