About this interactive
Single sign-on (SSO) means one set of credentials, for one account, gives a user the resources they need. The Single Sign-On lesson gives two reasons for it: it is convenient, and with only one password to remember, users can make that one long and strong instead of juggling many.
SSO needs interoperability: a central system that the user signs in to, which the other systems trust. Protocols such as LDAP, SAML, OpenID and OAuth carry that trust; the lesson's example is Active Directory, where signing in to a domain computer opens the shares and other resources the account is allowed. Linking separate services this way is called federation.
Some things look like SSO and are not. The same password reused on separate accounts is still many accounts, and reuse is risky. A password manager or a browser filling in a different password at each site saves typing, but each site still has its own account. A second factor added to each separate login is MFA, not SSO.
A quick test for each card: is there one account, signed in to once, that the other systems trust?
About TechKnowSurge
TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.
Explore free tools and programs →