We've implemented Okta SAML SSO with our layer-3 Captive Portal redirect page for IP-User mapping. The solution works, but users are landing on a "User Authenticated" web page, rather than the website they originally browsed to. Users now have to re-browse to the website first landed on, or browsed to to access the site. I figured SAML SSO would allow a transparent authentication to occur and return the requested webpage to the user. Anyone have this issue?
@Greg_FreyI am facing similar challenge where the Okta response is stopping at "<firewall ip>:6081/SAML20/SP/ACS" page. I did change the redirect host to FQDN under Captive Portal page. Do you need similar settings on the Okta side? Can you please help with the Okta settings?
The URL needs to match. In this case, the FQDN was similar on both the PanOS configuration for the redirect host, and the Okta URL.
Redirect Host: <FQDN>
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!
The Live Community thanks you for your participation!