<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content

Why Okta is Not Redirecting to Configured URL when Accessing Deep Links

Single Sign-On
Okta Classic Engine
Okta Identity Engine

Overview

This article explains why Okta may not redirect the end user to the configured URL when accessing a deep link via SAML SP initiated flow, and provides a solution to the issue.

Applies To

  • Application deep link URL
  • SAML SP Initiated flow
  • RelayState

Cause

This issue occurs when the deep link URL is configured to use port 80 (http://). Okta does not allow deep links to be accessed over an unsecured connection, so it redirects the user to the SP landing page instead.

Solution

To resolve this issue, ensure that the deep link URL is configured to use https://
This will allow the deep link to be accessed securely without being redirected to the SP landing page.

Additionally, it is recommended to use the "RelayState" parameter in the SAML request to ensure that the user is redirected to the correct page after authentication. The RelayState parameter should contain the URL of the page the user wants to access after authentication.

 

Related References

Loading
Why Okta is Not Redirecting to Configured URL when Accessing Deep Links | Okta Support