Is HWTACACS compatible with TACACS+

2

HWTACACS and the TACACS+ protocols of other vendors support authentication, authorization, and accounting. HWTACACS and TACACS+ are identical in authentication process and implementation mechanism. That is, they are compatible with each other at the protocol layer. For example, a device running HWTACACS can communicate with a Cisco server (such as ACS); however, HWTACACS may not be compatible with Cisco extended attributes because different vendors define different fields and meanings for extended attributes.

Other related questions:
Is HWTACACS compatible with TACACS+
HWTACACS and the TACACS+ protocols of other vendors support authentication, authorization, and accounting. HWTACACS and TACACS+ are identical in authentication process and implementation mechanism. That is, they are compatible with each other at the protocol layer. For example, a device running HWTACACS can communicate with a Cisco server (such as ACS); however, HWTACACS may not be compatible with Cisco extended attributes because different vendors define different fields and meanings for extended attributes.

Is HWTACACS supported by S series switches compatible with TACACS+
Both HWTACACS supported by Huawei S series switches (except S1700 switches) and TACACS+ supported by devices from other vendors provide authentication, authorization, and accounting functions, and use the same authentication process and implementation. That is, they are compatible with each other at the protocol layer. For example, a switch running HWTACACS can communicate with a Cisco server (such as ACS). However, HWTACACS may not be compatible with Cisco extended attributes because different vendors define different fields and meanings for extended attributes.

Why does HWTACACS authentication fail when the HWTACACS configuration is correct
The HWTACACS server template configuration of the AR is correct. In AAA mode, the HWTACACS authentication configuration and configuration of the remote TACACS server are correct. The possible causes for HWTACACS authentication failures are as follows: - The client's IP address is not configured on the TACACS server, so the TACACS server does not send authentication packets. - Different shared keys are configured on the AR and TACACS server.

Why does HWTACACS authentication fail when the HWTACACS server template and HWTACACS server are properly configured
This failure has the following possible causes: -The IP address of the router (a client) is not configured on the HWTACACS server, so the HWTACACS server cannot send an authentication response packet to the router . -Different shared keys are configured on the router and the HWTACACS server.

What are the possible causes for SSH+TACACS authentication failure
There is no default authentication mode for SSH users. If no authentication mode is specified for SSH users, users cannot access the Internet. Solution: When configuring SSH authentication, run the ssh authentication-type default password command to configure password authentication for SSH users.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top