09-17-2014 06:01 AM - edited 03-10-2019 10:02 PM
I'm currently rebuilding all of my VPN profiles after it was found that we were using TACACS+ for authentication to the VPNs, that would also allow users to SSH all of the network infrastructure. The new profiles will be radius based and will take some time to get them to the users.
In the meantime I'm looking to create a new shell profile for the VPN users that will only allow them to authenticate to the VPN and not gain access to the CLI of the infrastructure.
Thanks
09-22-2014 08:12 AM
Hi,
did you find any solution for this??
I am also stuck on the same issue...
09-23-2014 05:09 AM
I haven't found one yet. I think if i setup a service selection rule it should work but I haven't found anything formal to confirm yet.
09-24-2014 11:52 PM
Hi,
i tested this with Cisco ACS 5.5 with TACACS for VPN tunnel it doesn't work.
It gives you an error which is stated that service protocol used is for device administration.
So it doesn't all VPN authentication to work. but for radius this works properly.
Thanks & Regards,
Nitesh
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide