Which feature exactly we loose when Guest Originating URL not supported

[engahmedsaied]

Hello,

In certain WLCs with ISE compatibility we see that Guest Originating URL is not supported but guest is supported

Guest	RADIUS CoA, URL Redirection + SessionID, Local Web Auth
Guest Originating URL	RADIUS CoA, URL Redirection + SessionID, Local Web Auth

just to confirm which we will loose if our WLC doesn't support Guest Originating URL

"Guest user is not redirect back to the original URL"  only this if we understand correct ? or something more we can loose ?!

Thanks.

[emerson.albuquerque1]

Hello all,

I found this link about Web Authentication Redirection to Original URL Overview.

I believe it will help us.

https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ibns/configuration/15-e/ibns-15-e-book/ibns-webauth-origin-url.html#concept_1C6F778806A94FBBBD14A45C7D7C4372

[thomas · Accepted solution]

Found  ISE 2.6 Admin Guide > Authentication Success Settings for Guest Portals by searching "cisco Guest Originating URL" :

Originating URL

After successfully authenticating to the network, redirect the user’s browser to the original website that the user is trying to access, if available. If not available, the Authentication Success page displays. Make sure that the redirect URL is allowed to work on port 8443 of the PSN by the access-control list on the NAD and by authorization profiles configured in ISE for that NAD. For Windows, MAC and Android devices, control is given to the Self-Provisioning Wizard app, which does provisioning. Therefore, these devices are not redirected to the originating URL. However, iOS (dot1X) and unsupported devices (that are allowed network access) are redirected to this URL.