08-25-2018 11:35 PM - edited 08-26-2018 09:10 AM
Hi team,
I installed 2 separated certificates, 1 for portals with tag "portals" and another is for other usages.
When I accessed portal page with original URL like https://<ise ip or ADE-OS hostname>:8443/xxxxx...., portal certificate is used as expected. But when I accessed same portal with configured FQDN like https://mdsevices01.cert-test.com, admin certificate is used at the URL access once, then portal certificates will be used after redirecting the page to <ise ip>:8443. Is it expected behavior as design?
* FQDN configuration is as follows.
My customer would like not to show the admin cert to Mydevices portal operator or sponsors.
How can we specify the certificate for configured FQDN like mydevices01.cert-test.com?
Solved! Go to Solution.
08-27-2018 05:39 AM
08-28-2018 05:24 AM
08-26-2018 09:32 PM - edited 08-26-2018 09:36 PM
This is normal when you run different certs for admin and portal. ISE can’t issue a redirect without negotiating SSL. So you are going to 443 which is the admin cert. use HTTP instead of HTTPS in the first request and redirections will work. Note that Chrome will automatically go to SSL even if you type in http://. Chrome supports HSTS as does ISE.
08-27-2018 12:24 AM
08-27-2018 05:39 AM
08-28-2018 12:29 AM
08-28-2018 01:07 AM
08-28-2018 05:24 AM
08-30-2018 04:33 PM
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