Our company is changing it's name and I need to get everyone to log on via the AnyConnect client with the new FQDN, but also keep the old one as a backup I guess in case it goes wrong. I've registered the new FQDN and can ping it and it resolves our ASA's public IP.
Thing is we also have an SSL certificate on the ASA, if I manually type the new FQDN into the AnyConnect client I get this huge red screen saying the site is untrusted. What options do I have to back this smooth?
Can I add a new SSL cert to the firewall with the new and old FQDN?
If so does it create a request file so I can send off to Godaddy and then install it replacing the current one?
How can I add this new FQDN and make it first in the list?
If I have to manually edit the xml file where do I add the new FQDN, here is what I have currently?
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...