topic Re: 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. in Network Access Control https://community.cisco.com/t5/network-access-control/my-customer-was-configuring-the-ise-fqdn-with-an-internal-domain/m-p/3465804#M519594 <HTML><HEAD></HEAD><BODY><P>This looks similar to <A _jive_internal="true" href="https://community.cisco.com/thread/87418">HOSTNAME CHANGE ON ISE 2.3</A></P><P>Please also review <A _jive_internal="true" href="https://community.cisco.com/docs/DOC-68164">How To: Implement ISE Server-Side Certificates</A></P></BODY></HTML> Wed, 22 Nov 2017 00:46:13 GMT hslai 2017-11-22T00:46:13Z 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 https://community.cisco.com/t5/network-access-control/my-customer-was-configuring-the-ise-fqdn-with-an-internal-domain/m-p/3465802#M519592 <HTML><HEAD></HEAD><BODY><P>My customer was configuring the ISE FQDN with an internal domain “internet.mil”&nbsp; 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”?</P></BODY></HTML> Tue, 21 Nov 2017 21:06:21 GMT https://community.cisco.com/t5/network-access-control/my-customer-was-configuring-the-ise-fqdn-with-an-internal-domain/m-p/3465802#M519592 aelghoba 2017-11-21T21:06:21Z Re: 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. https://community.cisco.com/t5/network-access-control/my-customer-was-configuring-the-ise-fqdn-with-an-internal-domain/m-p/3465803#M519593 <HTML><HEAD></HEAD><BODY><P><SPAN style="color: #000000; font-family: UICTFontTextStyleBody; font-size: 17px;">Yes you would get a Public certificate and apply that to the guest portal</SPAN></P></BODY></HTML> Tue, 21 Nov 2017 22:42:07 GMT https://community.cisco.com/t5/network-access-control/my-customer-was-configuring-the-ise-fqdn-with-an-internal-domain/m-p/3465803#M519593 Jason Kunst 2017-11-21T22:42:07Z Re: 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. https://community.cisco.com/t5/network-access-control/my-customer-was-configuring-the-ise-fqdn-with-an-internal-domain/m-p/3465804#M519594 <HTML><HEAD></HEAD><BODY><P>This looks similar to <A _jive_internal="true" href="https://community.cisco.com/thread/87418">HOSTNAME CHANGE ON ISE 2.3</A></P><P>Please also review <A _jive_internal="true" href="https://community.cisco.com/docs/DOC-68164">How To: Implement ISE Server-Side Certificates</A></P></BODY></HTML> Wed, 22 Nov 2017 00:46:13 GMT https://community.cisco.com/t5/network-access-control/my-customer-was-configuring-the-ise-fqdn-with-an-internal-domain/m-p/3465804#M519594 hslai 2017-11-22T00:46:13Z