With SSO, a central domain performs authentication and then shares the session with other domains.

Identity Provider (IdP) session, if the user chose to log in through an Identity Provider (such as Google, Facebook, or an enterprise SAML Identity Provider)

Local session maintained by the applicationĪuthorization Server session, if SSO is enabled There may be up to three different sessions for a user with SSO: Single Sign-on and Single Logout are possible through the use of sessions. If the user is already logged in at the authentication domain, they can be immediately redirected to the original domain without signing in again. Whenever users go to a domain that requires authentication, they are redirected to the authentication domain where they may be asked to log in.

Instead of having to remember separate sets of credentials for each application or service, users can simply log in once and access your full suite of applications. SSO provides a seamless experience for users when using your applications and services. Likewise, if you log out of your Gmail or other Google apps, you are automatically logged out of all the apps this is known as Single Logout. The user signs in only one time, hence the name of the feature (Single Sign-on).įor example, if you log in to a Google service such as Gmail, you are automatically authenticated to YouTube, AdSense, Google Analytics, and other Google apps. Single Sign-on (SSO) occurs when a user logs in to one application and is then signed in to other applications automatically, regardless of the platform, technology, or domain the user is using.

Microsoft sso login