Hello Shikha,

Thanks for your question on our community site. We really would need to know which application you are referring to for deep linking.

There are many different applications and they handle deep linking differently.

Here are some examples of common deep linking scenarios.

KB article for deep linking Sharepoint applications - https://support.okta.com/help/s/article/How-can-I-create-a-chiclet-that-sends-users-to-a-deep-link-in-Sharepoint.

Developer's help guide for deep linking - https://developer.okta.com/docs/api/resources/idps#redirecting-with-saml-deep-links

Redirecting with SAML Deep Links

Use SAML deep links to automatically redirect the user to an app after successfully authenticating with a third-party IdP. To use deep links, assemble these three parts into a URL:

1) SP ACS URL, for example: https://{myOktaDomain}.com/sso/saml2/:idpId

2) The app to which the user is automatically redirected after successfully authenticated with the IdP, for example: /app/:app-location/:appId/sso/saml

3) Optionally, If the app is an outbound SAML app, you can specify the relayState passed to it, for example: ?RelayState=:anyUrlEncodedValue

The deep link for steps 1-3 is: https://{myOktaDomain}.com/sso/saml2/:idpId/app/:app-location/:appId/sso/saml?RelayState=:anyUrlEncodedValue

​​​​​​​Blog about Relay State:

https://support.okta.com/help/s/question/0D50Z00008G7V4ESAV/okta-saml-relay-state-processing-on-external-webapp

Okta IDP initiated RelayState - https://stackoverflow.com/questions/37882721/okta-idp-initiated-relaystate

Once again thank you for choosing Okta as your IdP. If you need further assistance please do not hesitate to call our support phone number at 1-800-219-0964.

Hey OKTA team,

I work for Bynder (a SaaS company) and one of our shared customers is having a problem with accessing deep links when their users use OKTA to login (via SAML 2.0). If the users click on a deep link to our application in an e-mail, they are redirected to the login page of our app with this URL (example) www.[customersdomain].com/login/redirectToken/DBB2DC3E-A0EB-47A8-A74F35D3ADF4D346/ When they then login via OKTA, they get redirected to the homepage of our application, instead of the location that the deep link actually directs to.

The problem only occurs for SSO logins, not for logins via a username/password combination for our application, which is why we would like your help. Could you point us in the right direction to solve the issue?

Thanks!