What we are considering is having the anyconnect client initially connect to the Cisco ASA, then have the ASA pass the authentication information back to the RADIUS server. This RADIUS server will then decide whether the user is allowed to connect or not based on what certificate, username, and password they provide.
PEAP - TLS allows for the use of certificates, and for usernames and passwords all to be validated in RADIUS. Our question is whether or not the AnyConnect client can provide this authentication information in the PEAP-TLS format or not, and if it can, how do we configure it.
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...