Assuming Chrome stops due to the web portal is presenting the ISE server certificates for admin, the only workaround is to include the portal FQDNs in those certificates' SAN fields.
Assuming Chrome stops due to the web portal is presenting the ISE server certificates for admin, the only workaround is to include the portal FQDNs in those certificates' SAN fields.
I have deployed sponsors portal using the same certificate that we use for Admin because it has wildcard SAN entry, but we use FQDN which does not explicitly exist in certificate (so we rely on wildcard). Due to HSTS both Chrome and Firefox report there's a problem with the certificate. In fact, the page loads fine on first attempt, but all consecutive attempts fail and certificate is blamed. What is the fix for this please?
@Bryan Byers The link you provided points to this very same conversation :)
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
