Symptom
Unable to open the sponsor portal when it has a custom FQDN
Conditions
ISE 3.2 P2,P3
Use more than 1 Nic
Configure custom FQDN in the Sponsor Portal
Host the Sponsor Portal in any extra nic
Workaround
Replace the FQDN in the test url with the FQDN configured in the sponsor portal and use that URL to access the sponsorportal.
for example, if sponsor.portal.com is the FQDN configured in the portal settings and ise1.portal.com:8555/sponsorportal/PortalSetup.action?portal=bd48c1a1-9477-4746-8e40-e43d20c9f429 is the test URL, access it using:
sponsor.portal.com:8555/sponsorportal/PortalSetup.action?portal=bd48c1a1-9477-4746-8e40-e43d20c9f429
instead of just sponsor.portal.com
Further Problem Description
This is a regression of the defect CSCwa62202
