Skip to content

Blog

Types of SSO and the protocols behind them

The types of SSO, from SAML and OIDC to social login, Kerberos and password vaults: what each one does, and which ones a small business actually needs.

· 9 min read

There are four main types of SSO: federated SSO over SAML or OpenID Connect, social login, network SSO with Kerberos inside a Windows domain, and password-vault SSO that stores and fills in passwords for you. Only the first one is what a SaaS pricing page means when it says "SSO". The others share the name because, to the person logging in, they feel similar.

For a small business on Google Workspace or Microsoft 365 and a pile of cloud tools, two of the four matter. Here is what each one is, which protocols sit behind it, and how to tell them apart before you pay for the wrong one.

Why "SSO" means several things

"Single sign-on" describes an experience, not a technology: you sign in once and get into several things. Over thirty years, very different systems have delivered that experience.

It started with office networks, where logging in to your Windows PC also got you into the file server and the intranet. Then came corporate portals that remembered your passwords and typed them for you. Later, websites began letting you "log in with" an account you already had elsewhere. Today, the version most people mean is a cloud tool handing your login to your company's identity provider.

All four get called SSO, by vendors and by people. When a tool says "SSO is on the Enterprise plan", it means the last one, and specifically one of two protocols. When a password manager says "SSO", it usually means something else. Knowing which is which saves you buying the wrong thing. If you want the basics first, what SSO is, in plain English is the place to start.

Federated SSO: SAML and OIDC

Federated means two separate organizations, your company and the tool's vendor, agree to trust each other's word about identity. Your identity provider (Google Workspace, Microsoft Entra ID, Okta) checks who someone is, and the tool accepts a signed statement from it instead of checking a password itself. How federated SSO works covers the trust model in depth.

Two protocols do almost all of it. The older is SAML 2.0, an XML-based standard from OASIS, published in 2005. It is the most widely supported SSO option in business software, and it is what most "SAML SSO" lines on pricing pages refer to; what SAML is explains the moving parts. The newer is OpenID Connect (OIDC), a JSON-based standard from the OpenID Foundation, published in 2014 and built on OAuth 2.0. It is common in newer tools, mobile apps and developer platforms, and what OIDC is covers it.

Both do the same job: the person is redirected to the identity provider, signs in there (with MFA), and comes back with a signed message that the tool checks. SAML vs OIDC compares them in detail. For a buyer, the difference rarely matters. What matters is whether the tool supports either one on the plan you are on.

Federated SSO is the type that can be enforced: the tool can refuse every login that does not come through your identity provider. That enforcement is what tools charge for, and it is what auditors and customer contracts usually mean when they ask for SSO.

A few older federation protocols still turn up: WS-Federation in Microsoft-heavy setups, and CAS in universities. A small business is unlikely to configure either.

Social login

Social login is the "Sign in with Google", "Sign in with Microsoft" or "Sign in with Apple" button. Technically it is usually OpenID Connect, so it is federated SSO too. What makes it a separate type in practice is who controls it.

The user chooses it. Nobody at your company set it up; the tool offers it to everyone who visits the login page. Because of that, it is not enforced. People can also sign up with an email and password, so you cannot be sure everyone is using it. And it is usually free, on every plan, because it costs the tool nothing and makes sign-up easier.

For a small company on Google Workspace, social login is underrated. When your people sign in to a tool with their work Google account, they get Google's MFA and your Google password rules, and suspending them in Google stops them starting new sessions in that tool. What you do not get is a guarantee: anyone who signed up with a password, or still has an open session, is unaffected. Google Workspace as your identity provider covers how far the free version gets you and where the paid, enforced version starts.

Enterprise network SSO: Kerberos and Active Directory

Before cloud tools, single sign-on meant the office network. A person logged in to a Windows PC joined to the company's Active Directory domain, and from then on the file shares, printers, intranet and internal apps let them in without asking again.

The protocol underneath is Kerberos, designed at MIT; its current version, Kerberos 5, is specified in RFC 4120. When you log in to the PC, a server called the key distribution center gives you a ticket, and your computer shows tickets to each internal service instead of sending a password. Directory lookups in the same networks typically use LDAP, the directory protocol covered in SSO vs LDAP.

This is real SSO, and still everywhere in large organizations. But it was built for machines on a company network talking to servers on the same network. Cloud tools on the open internet do not join your Windows domain. Big companies bridge the two by connecting Active Directory to a cloud identity provider, which then does SAML or OIDC to the SaaS tools. A company that has never had an office server room can skip this type entirely.

Password-vault SSO

Password-vault SSO (also called form-fill or password-based SSO) does not replace passwords at all. A portal or browser extension stores a separate password for each tool and fills it in when you click the tool's icon. You sign in once to the vault; the vault signs in to everything else on your behalf.

It feels like SSO, and some identity providers offer it for tools that do not support SAML or OIDC. But underneath, each tool still has its own password, which can be phished, reused or kept by someone who saw it. The tool cannot enforce anything, because it does not know an identity provider exists. And leavers keep working passwords unless every one of them is rotated.

A password manager with a shared company vault is the do-it-yourself version of the same idea. It is useful and often necessary, for different reasons; SSO vs a password manager covers where it helps and where it does not.

The types side by side

TypeHow it worksCan be enforced?Typical cost to a small teamWhere you meet it
Federated (SAML/OIDC)Signed message from your identity providerYesOften a Business or Enterprise plan per tool"SAML SSO" on pricing pages
Social loginUsually OIDC, chosen by each userNoFree on most plans"Sign in with Google" buttons
Network (Kerberos)Tickets inside a Windows domainYes, on the networkWindows servers and admin timeOffices with Active Directory
Password vaultStored passwords filled in for youNoPassword manager or IdP add-onTools without SAML or OIDC

SSO protocols, and the ones that are not SSO

People also search for "SSO protocols", and the honest list is short. SAML 2.0 and OpenID Connect carry logins to cloud tools. Kerberos carries them inside a Windows network. WS-Federation and CAS are older federation protocols you will meet only in specific corners.

Three names get mixed into that list that do not belong. OAuth 2.0 is about permission, not identity: it lets one app act on your behalf in another, such as a scheduling tool reading your calendar. OpenID Connect adds the identity layer on top of it, which is why "Sign in with Google" works, but OAuth on its own does not tell a tool who you are. SAML vs OAuth untangles that one. LDAP is a directory protocol: it lets an app check a password against a central list, but you still type the password into each app. SCIM is a provisioning standard: it creates and removes accounts, and it does not log anyone in at all. SCIM vs SAML explains why the two are bought together and do different jobs.

How to tell which type a tool means

Pricing pages are vague on purpose, so read the words closely. "SAML SSO", "SAML-based SSO" or "SSO with your identity provider" means federated SSO, the enforceable kind. "Google sign-in", "Sign in with Microsoft" or "social login" means the free, unenforced kind. "SSO" next to a list of identity providers such as Okta and Entra ID usually means federated SSO too, and often sits on the top plan.

When the page is unclear, the help center is not. Search the tool's documentation for "SAML". If the setup guide asks for an entity ID, a certificate and a sign-in URL, it is SAML. If it asks for a client ID and an issuer URL, it is OIDC. If the only option is a "Sign in with Google" button on the login page, you have social login and nothing to enforce.

Which matter for a small team

For a 5 to 50 person company on Google Workspace or Microsoft 365, the order of usefulness is fairly clear.

Start with social login on your work account, wherever a tool offers it on your current plan. It is free, and it brings your MFA with it. Then add a password manager for the tools that have no Google or Microsoft sign-in, and for the shared logins every company has. Add enforced federated SSO only for the tools where a customer, an auditor or a real risk makes it worth the upgrade, and expect to pay for each tool's higher plan; the SSO tax shows how much that adds up to. Leave Kerberos and Active Directory alone unless you already run Windows servers.

The size of the company changes the weighting, not the order. A five-person agency can run happily on Google sign-in and a password manager for years. A 50-person software company selling to larger customers will hit a security questionnaire that names SAML, and will need federated SSO for the handful of tools that hold customer data.

Notice what none of the four does: none of them creates accounts for new people or removes them when they leave. Every type of SSO handles the moment of login. The accounts, and the paid seats, are a separate job, usually called provisioning. User provisioning covers that side.

Where SmashSSO fits

SmashSSO is not a fifth type of SSO. It does not sit in front of any login, does not store passwords and does not fill them in. Your people keep signing in however they do now, whether that is "Sign in with Google", SAML or a password.

What it handles is the accounts. It reads your people from Google Workspace with read-only access, shows who has an account in each tool and with what role, and adds, changes and removes people by role from one place, through a tool's member API where you have added a token or through an agent in your own Chrome, in tabs where you are already signed in as an admin. That browser has to be open, and agent runs can fail when a tool changes its screens; a failed run says so. It costs a flat fee from $199 a month billed annually (pricing). If a contract requires enforced federated SSO, you still need it for the tools in scope.

FAQ

What are the types of SSO?
There are four main kinds: federated SSO over SAML or OpenID Connect, which is what SaaS pricing pages mean; social login such as "Sign in with Google"; network SSO with Kerberos inside a Windows Active Directory domain; and password-vault SSO, which stores passwords and fills them in. Only federated SSO can be enforced in cloud tools.
Is social login SSO?
In practice, yes. "Sign in with Google" or "Sign in with Microsoft" usually runs on OpenID Connect and lets one account log in to many tools. What it lacks is enforcement: people can still create password accounts, so you cannot require it for everyone.
What is the most common SSO protocol?
For workplace cloud tools, SAML 2.0 is the most widely supported. OpenID Connect is common in newer tools, mobile apps and social login. Inside Windows networks, Kerberos does the job.
Are OAuth, LDAP and SCIM SSO protocols?
No. OAuth 2.0 grants one app permission to act in another, and OpenID Connect adds the identity layer on top of it. LDAP checks passwords against a directory but you still type the password into each app, and SCIM creates and removes accounts without logging anyone in.
Is a password manager a kind of SSO?
Not really. It stores a separate password for each tool and fills it in, so it feels similar, but every tool still has its own password and cannot enforce anything. Some products call this password-vault SSO.

Keep reading

Stop paying for a login button.

Sign in with Google Workspace, connect your tools, and see who has access to what in minutes.

Sign up with Google