Single Sign-On (SSO): Definition, Process, Limits

Access & IdentitiesAlso known as: SSO, Single Sign-On, Single Sign On, Single Sign-on
In brief

Single Sign-On (SSO) is an authentication method in which a person logs in once at a central identity provider and can then use multiple connected applications without entering a password again. The applications trust a signed confirmation from the identity provider, usually transmitted via SAML 2.0 or OpenID Connect.

Key Takeaways

  • With SSO, a single login is enough for all connected applications.
  • SSO is usually based on SAML 2.0 or OpenID Connect and an identity provider.
  • SSO does not create accounts; provisioning handles that, for example via SCIM.
  • Many SaaS providers only offer SSO on higher pricing tiers.

How does Single Sign-On work?

With Single Sign-On, the identity provider handles authentication for all connected applications.

  • The person logs in once at the identity provider, for example with a password and second factor.
  • When they open an application, it checks with the identity provider.
  • The identity provider confirms the existing session with a signed response.
  • The application opens without asking for another password.

Why is SSO important for small and medium-sized businesses?

SSO reduces the number of passwords and centralizes security policies in one place. Multi-factor authentication is enforced once in the identity provider instead of in every application. Upon departure, disabling the account in the identity provider ends login access to all connected applications. Because SSO costs extra on many SaaS plans, small businesses usually connect only part of their applications.

What are the limitations of SSO?

SSO only protects applications that are actually connected.

  • Applications without SSO keep their own separate passwords.
  • Local accounts, API keys, and open sessions may remain active after an account is disabled in the IdP.
  • SSO does not create accounts and does not remove licenses.

Example: Single Sign-On (SSO) in practice

Real-world example

Example: A management consultancy with 40 employees uses Google Workspace as its identity provider. 12 of 20 applications are connected via SAML. Instead of managing around 15 passwords as before, each consultant now manages 8. When a consultant leaves, IT disables her Google account, blocking the 12 SSO applications, while the tool admins disable the remaining 8 accounts individually.

Single Sign-On (SSO) vs. Password Manager

AspectSingle Sign-On (SSO)Password Manager
PrincipleApplications trust a central loginStores separate passwords per application
Passwords per applicationEliminated for connected applicationsRemain in place and are autofilled
PrerequisiteApplication supports SAML or OpenID ConnectApplication has a login form
Central revocationDisabling in the identity provider takes effect across all connected applicationsAccounts must be disabled or passwords changed individually

Single Sign-On replaces separate passwords with a central login, whereas a password manager continues to manage separate passwords for each application.

How does Sovaro help with Single Sign-On (SSO)?

How Sovaro helps

Sovaro is not an SSO service and not an identity provider. Sovaro detects apps via its agent and browser extension, even without SSO, and displays them per person alongside licenses and devices. Upon departure, Sovaro shows all known access rights and devices and distributes the tasks for them, including for applications outside SSO.

Frequently Asked Questions about Single Sign-On (SSO)

Sources

See Sovaro with your own data.

Connect Google Workspace or Microsoft Entra, share the setup link, and see devices, apps, and licenses per person in one place.

14-day free trial, no payment details required. Cancel monthly.