01-22-2016 05:52 AM - edited 03-12-2019 12:10 AM
Hi All,
I have noticed something interesting . When one creates a username on an ASA for local authentication of VPN users, the user can SSH into the device.
I changed the user service type to remote-access only and changed the privilege to 0 but still it could login.
How can you stop this and only allow vpn login and no ssh/telnet .
I guess level 0 and 1 are the same or very minor differences.
Many thanks
01-22-2016 06:56 AM
01-22-2016 07:21 AM
got you so if the authorisation is place it stops users login with service type set to remote and allow all other user logins ?
I think what you are saying is Authentication always happens first and the ASA allows the client to log in after this as no authorisation is in place? If so when does it check the privilege level to allow access to enable mode?
does it no perform authorisation in unprivileged mode and performs this when one types enable
01-22-2016 07:31 AM
It seems from the cisco documentation, that if "aaa authorization exec Local" in place, and user type is "remote access", that user won't be able to have a ASDM/SSH/Telnet session opened (authentication won't be successful). And if user type is "remote access" the privilege level does not play role. The user with privilege level 15 and service type "remote-access" won't be able to pass the authentication of ASDM/SSH/Telnet session.
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