My customer was configuring the ISE FQDN with an internal domain “internet.mil” which is not publicly owned by the customer. For digital SSL certificate, the ISE shall shares its FQDN so a conflict appears as this domain is not owned by the customer. The

[aelghoba]

My customer was configuring the ISE FQDN with an internal domain “internet.mil”  which is not publicly owned by the customer. For digital SSL certificate, the ISE shall shares its FQDN so a conflict appears as this domain is not owned by the customer. The customer has another public domain “KNG.gov”. Can the customer configure the ISE with the public domain owned by the customer while keep serving users and computers member in the internal domain “internet.mil”?

[Jason Kunst · Accepted solution]

Yes you would get a Public certificate and apply that to the guest portal

[hslai]

This looks similar to HOSTNAME CHANGE ON ISE 2.3

Please also review How To: Implement ISE Server-Side Certificates