What Is Single Sign-On?
Single sign-on, or SSO, means you prove who you are once and then use several separate apps without proving it again. Wikipedia describes it as a scheme that lets a user log in with a single ID to any of several related, yet independent, software systems.1
Think of a night-class building with one front desk. You show your ID there. After that, each classroom door opens for you. You don't stop at every door and show it again.
It isn't the same as reusing one password
Here's the part people mix up. Typing the same password into ten apps is a habit. It isn't SSO.
Wikipedia draws the line clearly. It calls the first case "same sign-on." Each app still asks you to log in, but the apps check your credentials against the same directory server. With true SSO, one single authentication gives you access to multiple applications.1
So with the habit, you log in again and again. With SSO, you log in once and the apps are told you've already done it.
Why apps need a go-between
Different apps check people in different ways. An SSO system has to cope with that. The source says it must store the credentials used for the first login and translate them into what each mechanism needs.1
You don't see any of that. You see one sign-in screen.
A simple version can use cookies, which are small files a website saves in your browser. It only works if the sites share a common parent domain.1 Within one security domain, SSO is relatively easy to accomplish.2 Across domains it gets harder, and a standard such as SAML helps. The SAML page explains it. One source says SAML SSO is most commonly used to sign in to cloud-based business software.2
Signing out works the same way
The reverse has a name too: single log-out. One action of signing out ends access to multiple systems.1
Not every set-up does this. Whether a given app signs you out when you leave another is something to check in that app's own help pages.
The trade-offs
SSO gives you something to be careful with. Wikipedia calls it "keys to the castle." Once you've signed in, you can reach many resources. If someone else gets your credentials, they can reach them too. The source says SSO should ideally be combined with strong authentication methods such as smart cards and one-time password tokens.1 The multi-factor page covers that pairing.
There's a second catch. Everything leans on one sign-in system. If that system is down, people can be locked out of every app tied to it.1
That's a fair reason to plan ahead. A business that relies on SSO should know what it does when the sign-in system isn't reachable.
What to take to your own set-up
Three questions help when someone offers you SSO for your team:
- Which apps will use it, and do they all support it?
- What is the second check, besides the password?
- What's the plan if the sign-in system goes down?
The next page, identity providers and service providers, names the two sides of every SSO set-up. Start there if you want to read the setup screens in your own admin panel.
Cited material
- Single sign-on, Wikipedia
- SAML, Wikipedia