What is exactly "Use Auth0 instead of the IdP to do Single Sign On"

Can anyone help me understand what does “Use Auth0 instead of the IdP to do Single Sign On” do ?

What’s the difference between on and off ?

Thanks

:wave: @westwin this article here https://auth0.com/learn/how-to-implement-single-sign-on/ explains the use of this feature better than I can. Let me know if that clarifies things!

Thanks kim for your reply.

Per the explanation of “Enabling Single Sign On means that if the user is already logged in through Auth0, the Identity Provider (for example Facebook) login dialog won’t be prompted again, and he will be automatically logged in the specified application.”

Does it mean that if the switch is on,

  1. Auth0 will save a SSO cookie to indicates that the user has logged in
  2. When user initiates the second login from app, the browser will be redirected to Auth0, Auth0 then just issue sso token instead of redirecting to facebook to check facebook sso cookie ?

Thanks

:wave: @westwin if the session is still valid it will just be able to keep the user logged in - I’d have to check if there are any specifics around how it works for Facebook.

For anyone coming across this post, the "Use Auth0 instead of the IdP to do Single Sign On" setting is now become the Seamless SSO, where it is applied in the tenant level instead of application level ("Use Auth0 instead of the IdP to do Single Sign On" was at the application level) . All new Auth0 tenants come with seamless SSO` enabled, where as legacy tenants can choose to enable it feature. Any further details can be found here: https://auth0.com/docs/sso/current/setup

1 Like