In the latter case, each connection uses a separate XML profile so it should be possible to have each profile's certificate match section specify the desired certificate while continuing to use the default "automatic certificate selection".
If I have multiple certs in my keychain it will pick the first one installed I believe.
I have had a scenario where I could not VPN into a different connection (separate ASA, not cert based) until I removed my certificate for my original VPN profile. So it looks like it has 'automatic certificate selection' enabled by default
I'm not a Mac user but the other solutions that come to mind would be based on using OS X features alone. For example, removing and replacing the certificate from your keychain to match the desired connection. You could also setup a separate user with their own keychain or other such workarounds.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
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...