<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
0D54z00007fVyJpCAKOkta Classic EngineAuthenticationAnswered2024-04-16T11:04:22.000Z2022-05-23T07:43:05.000Z2022-05-24T15:44:43.000Z
  • Mihai N. (Okta, Inc.)

    Hi @7dsto (7dsto)​ , Thank you for reaching out to the Okta Community!

     

    Your post is rather lacking in details, but if I understand you correctly, your users are experiencing an unexpected behaviour in the login flow. 

    If in the example given by you the IDP is Okta, the behaviour after initiating the login would vary depending on the application (Service Provider - SP) itself and the SSO method used for the implementation (SWA, SAML, OIDC). In addition to that, some applications do not support IDP initiated login, as such, the users will first have to navigate to the SP page, initiate login from there and then be redirected to Okta for authentication, then redirected back to the respective resource.  

    Hope it helps!  

    Expand Post
This question is closed.
Loading
Bypass App login page after successful authenticating OKTA SSO and MFA