topic TACACS+ vs. RADIUS in Network Access Control

TACACS+ vs. RADIUS

r-lemaster — Sun, 10 Mar 2019 21:00:03 GMT

My textbooks don't seem to agree on this one issue. One of my textbooks say that you have to use TACACS+ for some features like cut-through proxy or virtual http, where another says you can use RADIUS for any AAA implementation.

Could someone tell me when TACACS+ is required and RADIUS is not supported? CSACS seems like an unnecessary expense when RADIUS is free.

Re: TACACS+ vs. RADIUS

gfullage — Wed, 02 Feb 2005 04:13:13 GMT

The main things Radius can't do is command authorization and accounting. This is a limitation of the Radius protocol where all authentication and authorization are combined, so there's no way to have a Radius device send off command requests after the initial user authentication has taken place.

Not sure what you mean by "virtual http", but you can certainly do it for "cut-through proxy", assuming by this you mean have the PIX authenticate users before their traffic can pass through.

Re: TACACS+ vs. RADIUS

r-lemaster — Wed, 02 Feb 2005 12:37:40 GMT

Thank you for your reply. (Cut-through proxy AKA authentication proxy, AKA downloadable ACLs, depending on your reading materials). I don't know other terms for virtual http/telnet.

I was wondering if there any specific features that Cisco requires the use of TACACS+ and RADIUS isn't supported. I'd just like to avoid the unnecessary expense if RADIUS is supported for these functions.

I'm not talking about accounting or the differences between RADIUS or TACACS+, just the general function of authentication through PIX or routers.

Man, this site is slow.