01-16-2021 11:15 AM
Hello All ,
I have added an SSL cert for the ASA - ciscoasa.ladderbar.com (195.36.189.55) and applied the certificate on the SSL settings on the ASA so when users use anyconnect using the DNS name (ciscoasa.ladderbar.com) it works good and no risk message is shown , but when they use the IP it comes up with certificate not trusted message.
Same issue when I browse - https://195.36.189.55 - website shows not secure but https://ciscoasa.ladderbar.com - shows secure.
Any settings on the ASA that i might have missed ?
Thank you
Solved! Go to Solution.
01-16-2021 11:03 PM
01-16-2021 12:06 PM
Nothing that you missed here. That's the way it works. The IP address is not part of the certificate and with that not trusted by the client.
01-16-2021 12:20 PM
01-16-2021 11:03 PM
01-17-2021 12:49 AM
Hi , thanks for this , I thought I did put the ip in ... but I will rekey and make sure , also in the fortigates it works without adding the ip in the fortigates.
01-17-2021 01:05 AM
In my opinion it's not worth the effort to put the IP in the certificate. The CA needs a stricter validation process that you must follow to get the certificate, the certificates are more expensive and if you are using Windows, it will likely not work with older versions than Win10.
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