The problem is that I want to configure a local database on the ASA in order to authenticate WebVPN users, but it looks like ASA is using the same database for authenticating users for SSH access. Is there any way to define which users are going to be authenticated only for WebVPN and not for SSH?
even i had the same problem, let i had come to know that user will need to authentication via the users created locally for logging in to the device, in such case, i would advice you to login via TACACS, that would be really helpful to track the users who ever logs in via VPN.
Actually, I don't want to use TACACS+ for user authentication, because there's going to be only 7-10 WebVPN users, so deploying TACACS+ server doesn't make any sense. But I was really surprised when I found that there's no any possibility to determine which users are only for WebVPN access and which are only for SSH access.
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...