Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Single sign-on (SSO) is an authentication method that lets users log in once with a central identity provider and then access multiple applications without signing in again.

What Is Single Sign-On (SSO)?
Single sign-on (SSO) is an authentication approach that allows a user to sign in once, with one set of credentials, and then reach many different applications without logging in to each one separately. Behind the scenes, a central identity provider confirms who the user is and passes that confirmation securely to each application.
For employees, SSO means fewer passwords to remember and fewer login prompts. For security teams, it means one place to enforce strong authentication, apply access policies, and switch off access when someone leaves. Done well, it improves both convenience and security at the same time, which is rare.
SSO relies on a trust relationship between two parties:
When a user opens an application, it redirects them to the identity provider. If they already have an active session, the IdP issues a signed token or assertion straight away; if not, it asks them to authenticate first, typically with a password and multi-factor authentication. The application verifies the signature on the token and logs the user in without ever seeing their password.
| Protocol | Typical use | Notes |
|---|---|---|
| SAML 2.0 | Enterprise web applications | XML-based assertions, widely supported by business software |
| OpenID Connect | Modern web and mobile apps | Identity layer built on OAuth 2.0, uses JSON Web Tokens |
| OAuth 2.0 | Delegated authorisation for APIs | Grants access to resources, not designed for authentication on its own |
| Kerberos | On-premises Windows networks | Ticket-based SSO inside Active Directory domains |
Concentrating authentication in one place also concentrates risk. If an attacker compromises a user’s SSO session, they may gain access to every connected application. If they compromise the identity provider itself, the impact can be enormous.
Real incidents illustrate this. In the SolarWinds campaign uncovered in December 2020, attackers used a technique known as Golden SAML, stealing the signing key from an on-premises federation server to forge authentication tokens for cloud services. In October 2023, Okta disclosed that attackers had accessed its customer support system and obtained files that included session tokens belonging to some customers.
Other risks include stolen session cookies, which bypass MFA entirely and are closely related to session hijacking, and applications left outside SSO that still use local passwords.
SSO handles authentication, but users also need accounts created and removed in each application. Standards such as SCIM (System for Cross-domain Identity Management) automate this, so that joiners receive access on day one and leavers lose it immediately. Combined with role-based access control, this makes access management far more reliable than manual processes.
At Privia Security, our Multi-Factor Authentication (2FA) Solutions strengthen your SSO sign-ins, and our penetration tests assess how attackers could abuse your identity platform.
SSO is generally more secure than separate passwords for every application, because it reduces password reuse and lets you enforce strong MFA and access policies in one place. However, it does concentrate risk, so the identity provider, its administrator accounts, and its signing keys must be protected very carefully and monitored closely.
SSO is about convenience and central control: one login gives access to many applications. MFA is about the strength of that login: it requires two or more independent factors. The two work best together, with MFA enforced at the identity provider so that every application connected through SSO benefits from strong authentication.
Both enable SSO. SAML 2.0 is an older, XML-based standard widely used by enterprise web applications. OpenID Connect is a newer identity layer built on OAuth 2.0, using JSON Web Tokens, and it is better suited to modern web, mobile, and API-driven applications. Many identity providers support both protocols.
If the identity provider is unavailable, users may be unable to sign in to any connected application, so resilience planning matters. Cloud identity providers offer high availability, and organisations should keep secured emergency access accounts and documented procedures for outages, tested as part of business continuity planning.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.