Portal Sponsor

[TiUM]

Is there a way to open the sponsor portal via the FQDN? Because i have one created and added in our DNS and mapped to ISE, example: mycompany.sponsor.com

But the problem is that the portal does not open if i use that address, only with the "hash" that is created byitself like mycompany.sponsor.com/jasjd?ajshdjkashdjk?8jkashdjas

How can i mitigate this?

[marce1000]

 - FYI : https://community.cisco.com/t5/network-access-control/how-do-i-query-the-sponsor-portal-fqdn-to-the-dns-server/m-p/4053397

 M.

[TiUM]

That is what i have configured. But the portal does not open with the the link provided. Only with the "stupid" algorithm that he creates, instead od mycompany.sponsor.com only opens with mycompany.sponsor.com/jkshfhsaduif?uiwhyuiwhu -> this is not supposed to happen

[Greg Gibbs · Accepted solution]

A couple of things here:

1. I assume your example would be something like 'sponsor.mydomain.com' as you would not likely have a DNS domain called sponsor.com, correct?
2. When accessing the sponsor FQDN (e.g. sponsor.domain.com), ISE internally redirects to the port number (default 8445) and internal portal ID. This is how ISE supports multiple portals. The URL format you see should be in the form of 'https://sponsor.domain.com:8445/sponsorportal/PortalSetup.action?portal=<portalID>'
   Could there be something in the path between the client and ISE that is hashing the URL in your environment (WAF, load balancer, NGFW, etc)?