10-27-2022 11:53 AM
Hi everyone, we are configuring Microsoft Proxy APP to access our Internal ISE Sponsor Portal but but, it is timing out after redirecting to the Portal. Has anyone implemented this solution by any chance? Next a diagram that explains the situation.
Solved! Go to Solution.
11-13-2022 04:25 AM
I think it’s about url. Sponsor portal runs on port 8443, but ISE will redirect you to this port from http://sponsor.domain.com. You can test it and call http://sponsor.domain.com:8443 from LAN - you will get an error (I’m sure to 98,3%, but not 100%; it’s a while since I configured sponsor portal last time)
So you have to call portal url without port (more specific - ISE looks for host entry in HTTP GET request) and if in your request from proxy host is something else, you won’t receive sponsor portal.
You can verify very simple what happens with tcp dump, available on ISE under troubleshooting tab.
11-11-2022 02:02 PM
Never seen or heard of it.
Does it work without the Proxy Connector?
Sorry, but this looks like a question for Microsoft. 8-)
11-13-2022 04:25 AM
I think it’s about url. Sponsor portal runs on port 8443, but ISE will redirect you to this port from http://sponsor.domain.com. You can test it and call http://sponsor.domain.com:8443 from LAN - you will get an error (I’m sure to 98,3%, but not 100%; it’s a while since I configured sponsor portal last time)
So you have to call portal url without port (more specific - ISE looks for host entry in HTTP GET request) and if in your request from proxy host is something else, you won’t receive sponsor portal.
You can verify very simple what happens with tcp dump, available on ISE under troubleshooting tab.
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