Authentication & Password

Single Sign-On (SSO)

About 4 min read

What Is Single Sign-On (SSO)

Single Sign-On (SSO) is a mechanism that allows access to multiple related services and applications with a single authentication. For example, logging into your Google account gives you access to Google services such as Gmail, Google Drive, and YouTube without re-authenticating. This is a typical example of SSO.

In enterprise environments, a single login to the company portal provides access to multiple systems including email, chat, attendance management, and expense reporting. It dramatically reduces the number of passwords users need to manage and prevents password reuse that causes credential stuffing.

Major SSO Protocols

Several protocols are used as the technical mechanisms to implement SSO.

  • SAML 2.0: A protocol approved as an OASIS Standard in March 2005. Exchanges XML-based assertions (authentication information) between the IdP (Identity Provider) and SP (Service Provider). Examples of IdP products include Okta, Microsoft Entra ID (renamed from Azure AD in July 2023), and OneLogin
  • OpenID Connect (OIDC): A protocol that adds an authentication layer on top of OAuth 2.0. Under the OpenID Connect Core 1.0 specification, the result of authentication is returned in an ID Token in JSON Web Token (JWT) format, and basic profile information about the End-User can be obtained in a REST-like manner. Google's developer documentation states that its OAuth 2.0 implementation for authentication conforms to the OpenID Connect specification and is OpenID Certified
  • Kerberos: A ticket-based authentication protocol used in Active Directory environments. Microsoft's documentation states that in Windows Server, the Key Distribution Center (KDC) runs on every domain controller and uses the domain's Active Directory Domain Services database as its account database

As of October 2026, NIST SP 800-63C-4 gives the ID Token in OpenID Connect and the SAML Assertion format as examples of assertions used in federation protocols.

Benefits and Risks of SSO

SSO offers benefits in both convenience and security, but also has inherent risks.

Benefits

  • Eliminating Password Fatigue: With only one password to remember, users are more likely to set a strong one
  • Centralized Security Management: By centralizing the authentication infrastructure, two-factor authentication and access policies can be uniformly applied across all services
  • Reduced IT Management Costs: Password reset requests decrease, and disabling a departing employee's account on the IdP also stops sign-ins through that IdP to each connected service

Risks

  • Single Point of Failure: If the IdP goes down, users cannot log in to the connected services that authenticate through it. Sign-in availability for those services depends on the IdP's availability
  • Blast Radius of Compromise: If an SSO account is hijacked, an attacker can sign in to the connected services with that account at once. The impact of a single credential leak extends across the connected services
  • Vendor Lock-in: Dependency on a specific IdP may increase migration costs

To mitigate risks, it's essential to set up strong authentication using passkeys or FIDO2 security keys on your SSO account.

Safe SSO Operations

Here are practical tips for operating SSO safely.

  • IdP Account Protection: Authentication methods available for the IdP account that serves as the SSO entry point include hardware security keys and passkeys. NIST SP 800-63B requires verifiers at AAL2 to offer at least one phishing-resistant authentication option, and treats use of the public switched telephone network (SMS or voice) for out-of-band verification as restricted
  • Proper Session Management: NIST SP 800-63B recommends that, at AAL2, the overall reauthentication timeout be no more than 24 hours and the inactivity timeout no more than 1 hour. For services that require a higher assurance level, re-authentication (step-up authentication) can raise the session's assurance level
  • Access Log Monitoring: Mechanisms that detect and alert on logins from unusual locations or devices
  • Principle of Least Privilege: Integrate with IAM to grant users access only to the minimum services required for their role
  • Emergency Access Procedures: Microsoft's documentation for Microsoft Entra ID recommends creating two or more emergency access accounts for emergency or "break glass" scenarios in which normal administrative accounts can't be used, as cloud-only accounts that aren't federated or synchronized from an on-premises environment

To learn more about this topic, see Two-Factor Authentication (2FA): The Best Defense for Your Accounts.

Common Misconceptions

Implementing SSO solves all password management problems
SSO reduces the number of passwords, but services that don't support SSO still require individual passwords. Also, if the SSO account password itself is weak, all services are at risk. Passwords for services that don't support SSO can be managed with a password manager.
Using SSO automatically improves security
SSO enables centralized authentication management, but doesn't inherently strengthen security. Without two-factor authentication, with overly long session timeouts, or without access log monitoring, risks can actually increase with poor operational practices.
Share

Related Terms

Related Articles