Think about a situation in which a single page on your website is unable to handle both authenticated and unauthenticated states (protected url). You can include the skip
query parameter in the authorization url which then diverts the visitor to another page dedicated to handling unauthenticated sessions.
Users will not be prompted for any login credentials in this workflow, but the login page will be completely disregarded and skipped to the specified URI. 💊
If enabled, the Forwarder feature ensures that the SSO is on the same domain as the Referrer
.
Say you have a single SSO Login application that is replicated across multiple domains as belows:
sso.domain.x
sso.domain.y
sso.domain.z
If the login was initiated from domain.z
to sso.domain.x
, the page will be redirected to the same address pattern but on domain.z
rather than sso.domain.z
.
This is a workaround for the login page's IFrame embedding issues caused by some desktop and mobile devices' restrictive cookie policies, which prevent cross-domain cookie sharing. 💊
Similar to the Forwarder feature, except that the logic is applied to the redirect_uri
query parameter rather than the entire SSO domain.