10-24-2020 03:57 AM - edited 10-24-2020 03:58 AM
I've setup "AAA and Certificate" for tunnel group and import Root CA into CA certificate on the ASA.
I also setup "CertificateStore" as "Machine" and enable "CertificateStoreOverride" on the client profile.
According to the debug result, the VPN session still used user certificate instead of machine certificate for authentication.
Is it possible cause by same issuer for both user certificate and machine certificate?
How can I force to use machine certificate for authentication?
Solved! Go to Solution.
10-25-2020 01:05 AM
The root cause is I have too many VPN profile at local, so AnyConnect didn't choose the correct one.
It's working after I delete other VPN profile and keep the necessary one.
10-24-2020 02:46 PM - edited 10-24-2020 02:47 PM
Based on the input it should work. Did you make sure that you tried to disconnect and reconnect after the profile was downloaded first time to the client?
10-25-2020 12:37 AM
Yes, I try to reconnect the VPN after profile downloaded, but it still use the user certificate for authentication.
10-24-2020 09:15 PM
I was having this exact same issue and for some reason, by setting IKEv2 as the connection fixed my problem. Remove SSL from the connection profile and also the AnyConnect Profile.
Check out my post when I ran into this issue.
10-25-2020 01:03 AM
Thank you for inspiring me! I check the DART log then I found the root cause!
10-25-2020 01:05 AM
The root cause is I have too many VPN profile at local, so AnyConnect didn't choose the correct one.
It's working after I delete other VPN profile and keep the necessary one.
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