<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
0D51Y00009hLQCbSAOOkta Classic EngineSingle Sign-OnAnswered2024-07-29T09:00:19.000Z2020-10-14T14:00:16.000Z2020-10-22T19:55:00.000Z

th7zc (th7zc) asked a question.

How Single Sign-on works for different applications with different authentication methods

Hi,

We have applications integrated with OKTA. App A uses SAML authentication while app B uses OIDC authentication. A user logs onto app A after OKTA authentication. Is it possible for the user to have access to app B from app A without a second log on?

fx


  • Hello Feng,

     

    When the user logs into Okta, they will not have to login again during that session time for any application that is integrated into Okta. Okta will, in most cases, automatically log you in to those applications when you attempt to access them. Exceptions are if you launch an app that doesn't support SP-initiated login flows, or if you have application level security policies that require it.

     

    Let us know if you have any other questions!

    Thanks,

     

    Tim

    Okta Inc

    Expand Post
  • User1581544194309277450 (Vendor Management)

    Hello Feng

     

    Indeed, when a user logs into Okta they will not have to log in again for other Okta apps.

     

    To answer your question, this should be possible, as an active session in Okta would still be available. However, the app A must have the option to add app B in it.

     

    Hope this helps.

     

    If you still need further info on this, feel free to open a ticket with Support.

     

    Thank you

    Andrei.

     

     

    Expand Post
This question is closed.
Loading
How Single Sign-on works for different applications with different authentication methods