single sign-on (SSO) (noun) [Word Notes]

Oct 27, 2026 · Summarized Nov 1, 2026

Listen in Apple Podcasts Pocket Casts Castro

Key takeaways

Single sign-on lets a user or application authenticate once with a trusted source and then access multiple applications with one set of credentials.
Before SSO, each workload independently checked a user ID and password, forcing users to repeat the process for every application or network.
The episode criticizes the practice of blaming users for weak or reused passwords when they were managing an identity system originally designed in the early 1960s.
SSO reduces the number of passwords a user must remember, but it does not prevent the user from choosing a weak password such as “12345.”
Two-factor authentication can improve the security of an SSO arrangement, because one password alone remains vulnerable.
SAML is described as an XML-based technology commonly used for enterprise applications, while OAuth is used primarily for open-internet authorization; OAuth itself does not authenticate users.
“Log in with Facebook” or “log in with Google” is an example of identity federation and SSO, with OAuth allowing third-party services to use account information without exposing the user’s password.

Summary

Single sign-on is introduced as a Zero Trust authentication tactic

The Word Notes episode defines single sign-on, or SSO, as a session and user authentication Zero Trust tactic that lets a person access multiple applications with one set of login credentials. Its basic promise is that users authenticate to a trusted source once, rather than repeatedly presenting separate credentials to every application or network they use. The episode begins tracing the problem back to the 1960s, when computing pioneer Dr. Fernando Corbató introduced passwords as a way to control access to computers. The narrator says passwords became a major attack vector once the internet began supporting online transactions at scale in the mid-1990s. Before SSO, identity and access management amounted to a user or application sending credentials to a workload; the workload checked whether the presented user ID and password matched credentials stored locally, then granted or denied access. The episode argues that the resulting password burden has often been unfairly placed on users. People had to remember many passwords, while security leaders blamed them for choosing weak passwords or reusing them. The recurring lists of passwords such as “12345” and “password,” the narrator says, amount to victim-blaming because users are being faulted for struggling with a stopgap system designed in the early 1960s.

Before SSO, every application demanded another password

The pre-SSO process required users to repeat the same identity-checking handshake for every application and network. Each workload independently verified the credentials that a user supplied, so someone working across many systems was expected to maintain a large collection of passwords. The episode presents this as a usability and security failure: the more credentials people had to remember, the greater the temptation to choose simple passwords or reuse the same one. SSO changes the arrangement by allowing the user or application to assert an identity once to a trusted source. When the user later requests access to another workload—whether software, hardware, or another network—the workload and trusted identity source determine whether that request is valid. The user therefore needs to remember only one password rather than one password for every service. The narrator immediately identifies the limitation: consolidating access does not automatically produce a strong password. A user could still choose “12345” as the one password protecting all of those applications. The episode says two-factor authentication can improve that situation and points listeners to another WordNotes episode for an explanation. SSO simplifies identity and access management, but it is not presented as a complete authentication-security solution by itself.

SAML and the OpenID/OAuth combination enabled modern SSO

The episode says two technology families emerged in the early 2000s to make SSO possible: SAML and the OpenID/OAuth pair. SAML stands for Security Assertion Markup Language and is described as a heavyweight, XML-based language that lets one computer perform authentication and authorization on behalf of other computers. The OpenID/OAuth history is described as more confusing and marked by “internet drama.” The narrator emphasizes a distinction that is easy to miss: despite OAuth’s name—often expanded as “open authentication”—OAuth does not authenticate anything. Instead, OAuth authorizes a machine to log into another machine on behalf of a human. OpenID performs the authentication portion. By 2014, the episode says the technologies had settled into clearer roles. Citing CSO Magazine, it reports that most network operators use SAML for enterprise applications and OAuth for open-internet solutions. The resulting division of labor is not presented as a debate over which technology universally wins; rather, the episode concludes that both approaches contributed to making SSO practical in different environments.

A Facebook or Google login illustrates identity federation

The episode’s “nerd reference” is a 2020 IonTech YouTube explanation by Jen English. It uses a familiar experience: a person visits an application or website, chooses “log in with Facebook” or “log in with Google,” and is signed in to a third-party site without creating a separate account. The point is that this is not magic; it is single sign-on. English’s explanation again defines SSO as a service that lets a user use one set of credentials, such as a username and password, across multiple applications. The episode calls SSO a federated identity-management arrangement, meaning that using it can also be described as identity federation. In the Facebook example, OAuth provides the framework that allows account information to be used by a third-party service without exposing the user’s password. The episode closes by returning to its main conclusion: SSO greatly simplifies identity and access management, although reaching this point took roughly 50 years from Corbató’s password idea in the early 1960s. The credits identify Tim Nodar as the writer, Peter Kilpe as executive producer, John Petrick and Rick Howard as editors, and Elliot Peltzman as responsible for the mix, sound design, and original music.

Show notes

Please enjoy this encore of Word Notes.

A session and user authentication Zero Trust tactic that allows a user to access multiple applications with one set of login credentials.

CyberWire Glossary link: ⁠https://thecyberwire.com/glossary/single-sign-on⁠

Audio reference link: English, J., 2020. What is Single Sign-On (SSO)? SSO Benefits and Risks [Video]. YouTube. URL ⁠https://www.youtube.com/watch?v=YvHmP2WyBVY

Follow this show on AudioBrevity and new episodes get summarized for you. Create a free account