Anyone know in what IOS did we gain the functionality of forcing authentication over a given port to a TACACS server?
The syntax is as follows...
tacacs-server host hostname [single-connection] [port integer] [timeout integer] [key string]
Reason being, our TACACS server has users organized into differernt functional groups that each use a different port for authentication. The default port is 49, but due to my area of responsibility, I happen to fall into the group that is set to use port 52.
I have been temporarily given access to the port 49 group so that I can authenticate to this switch and make the necessary changes to port 52, but the CatOS is 5.5(16) and when configuring the TACACS settings, port numbers are not valid arguments in the syntax.
I think this feature was first introduced with IOS version 10.0, but just looking for assurance.
"Be the packet"
The syntax is as follows...
tacacs-server host hostname [single-connection] [port integer] [timeout integer] [key string]
Reason being, our TACACS server has users organized into differernt functional groups that each use a different port for authentication. The default port is 49, but due to my area of responsibility, I happen to fall into the group that is set to use port 52.
I have been temporarily given access to the port 49 group so that I can authenticate to this switch and make the necessary changes to port 52, but the CatOS is 5.5(16) and when configuring the TACACS settings, port numbers are not valid arguments in the syntax.
I think this feature was first introduced with IOS version 10.0, but just looking for assurance.
"Be the packet"