topic Authenticating HTTP with TACACS+ in Network Access Control

Authenticating HTTP with TACACS+

venancio.martinez — Sun, 10 Mar 2019 14:12:21 GMT

We have configured aaa authentication through a tacacs+ server in a catalyst switch. It works fine with console and telnet, but not with http access.

We see that console and telnet access makes that the catalyst uses tcp 49 port (tacacs+), but http access uses 49 udp port.

Our ACS works with 49 tcp (tacacs+), but not with 49 udp.

What's the problem? How can we solve it?

TIA

Re: Authenticating HTTP with TACACS+

a-vazquez — Fri, 21 Mar 2003 21:22:41 GMT

I think you are using the old HTTP authentication command thats why its using UDP port 49, try using the following command

aaa authentication login default group tacacs+ enable

ip http authentication aaa

Re: Authenticating HTTP with TACACS+

mhoda — Thu, 27 Mar 2003 07:59:03 GMT

Older version used to support XTACACS which used UDP port 49 rather than TCP/49 used for TACACS+. Please refer to this link and make sure that you have the config set up properly.

http://www.cisco.com/en/US/tech/tk583/tk642/technologies_tech_note09186a0080094ea4.shtml