Cisco Anyconnect client Certificate Validation Failure
Posted on 2015-01-22
I am planning to move users in my organisation from a Cisco IPsec VPN to the newer Cisco AnyConnect SSL VPN client. We are using the Cisco ASA 5510 (in failover mode).
Previously while using the IPsec client we used pre-shared keys and a AAA (active directory server). As AnyConnect no longer supports pre-shared keys the only way for us to have two factor authentication is to use certificates. To further confound our situation Cisco also do not support using the ASA as a local CA for the issuance of these certificates while in failover mode. I have therefore setup a Microsoft Certificate authority.
1st of all I tested using a local CA (on the ASA itself) and issued certificates to my AnyConnect clients (with failover mode disabled - mainly did this to get the hang of it. This worked fine - clients connect no problem.
2nd I then enabled failover again - which disabled the local CA on the ASA and issued the CA certificate from my Microsoft CA to the ASA. I also then signed a requested certificate for the AnyConnect client and added it to the ASA. So far so good. I then attempted connecting by going to the ASAs external web address in my browser AsaAddress.domain.co.uk this automatically downloaded the version of AnyConnect I had uploaded to the ASA and prompted me to accept the certificate I had issued for this client. Great! I accepted the prompt and was connected. All seemed to work well.
3rdly and this is my problem - I then disconnected from the VPN and attempted connecting just by using the installed VPN client. (not by browser) No luck. Every time I try I get "No valid certificates available for authentication" and "certificate validation failure". This makes no sense. In the second step I had just connected and used the same certificate I issued for the client to authenticate with?
4th - I tried again to connect by going through the browser interface (which then uses the client anyway) and it worked fine?!
So the certificate is obviously fine so why am I getting these errors when using the client? My users will only be using the client so using the browser is not an acceptable workaround?
If anyone can help or has any ideas I would be most grateful!
I am using:
Cisco ASA 9.1(5)