SSO vs LDAP is not a contest: LDAP is a protocol for looking people up in a directory and checking their passwords against it; SSO is a way of letting one login carry across many tools. LDAP is plumbing from the era of office servers, where every app checked your password itself against a central directory. SSO, as cloud tools use it, means apps never see your password at all.
If your company runs on Google Workspace or Microsoft 365 and cloud tools, you can probably skip LDAP entirely. The few places it still turns up are worth knowing, though, because they are the ones a cloud identity provider does not cover by default.
LDAP in plain terms
LDAP stands for Lightweight Directory Access Protocol. A directory is a structured list of people, groups and devices: names, emails, phone numbers, which groups someone is in, a password hash. LDAP is the language apps use to talk to that list.
It does two jobs. The first is lookups: "Give me everyone in the Finance group", or "What is the email for user sam?" An app sends a search, and the directory answers. The second is password checks: an app asks for your username and password, then tries to "bind" to the directory as you. If the bind works, the password is right. That is how LDAP gets used for login.
LDAP first appeared as an IETF standard in 1993 (RFC 1487), as a lighter way to reach X.500 directories. The version in use today, LDAPv3, is defined in RFC 4511 (2006) and its companions. The best-known LDAP directory is Microsoft Active Directory, which runs Windows domains and speaks LDAP alongside Kerberos. OpenLDAP is the common open-source one.
LDAP was designed for a world where the apps, the directory and the people were all on the same company network. It assumes the app is trusted to handle your password. The standard says as much: RFC 4513, the companion that covers LDAP authentication, notes that a simple name-and-password bind "discloses the password to the server", and strongly discourages clear-text passwords over networks that are not encrypted. In practice that means LDAP should always run over TLS, which LDAP-capable apps and devices call LDAPS or StartTLS.
SSO in plain terms
Single sign-on (what SSO is) means you log in once, to an identity provider such as Google Workspace, Microsoft Entra ID or Okta, and the tools you use accept that login instead of asking for their own. For cloud tools it runs over the web with SAML or OpenID Connect: the tool sends you to the identity provider, you sign in there (with MFA), and you come back with a signed message saying who you are. How SSO works traces it step by step.
The key property: the tool never sees your password. It trusts the identity provider's signature, not a credential you typed into it.
LDAP vs SAML
People search "LDAP vs SAML" because both get described as ways to log in with your company account. They work in opposite ways.
| LDAP | SAML | |
|---|---|---|
| What it is | A directory protocol: query and authenticate | A federation protocol: pass a signed login statement |
| Who sees the password | The app, which forwards it to the directory | Only the identity provider |
| Where it runs | Usually inside a network, app to directory server | Over the web, through the user's browser |
| What the app gets | Yes or no on the password, plus directory data | A signed assertion about the person |
| Single sign-on? | No. Same password everywhere, typed every time | Yes. One login, accepted by many tools |
| MFA | Not part of the protocol; added by other means | Whatever the identity provider enforces |
| Typical users | Wi-Fi, VPNs, file servers, older on-premise apps | Cloud business tools: Slack, GitHub, Figma |
So is LDAP SSO? Not really. LDAP gives you one password for many systems, which is useful, but you still type it into each one, and each one handles it. That is sometimes called "same sign-on" to tell it apart. True single sign-on means signing in once and not being asked again. What SAML is and the types of SSO cover the federated kind in more detail.
The two do often work together in larger companies: the identity provider checks passwords against Active Directory over LDAP behind the scenes, then issues SAML assertions to cloud tools. LDAP holds the people; SAML carries the login out to the web.
The same comparison holds for OpenID Connect, the newer federation protocol behind most "Sign in with Google" buttons. Like SAML, it hands the app a signed statement instead of a password, so everything in the SAML column above applies to it too. SAML vs OIDC covers how those two differ from each other.
Where small businesses still meet LDAP
Is LDAP still used? Yes, constantly, in large organizations and in a handful of places a small business might hit.
The most common is office Wi-Fi with individual logins. Enterprise Wi-Fi (WPA2- or WPA3-Enterprise) usually checks credentials through a RADIUS server, which often checks them against a directory over LDAP. Close behind are VPNs and firewalls that want a company login rather than one shared password. Network storage and printers are another: NAS boxes and office scanners often offer LDAP for user accounts. Self-hosted software is a fourth, since older or self-hosted versions of wikis, issue trackers and Git servers often support LDAP and not SAML. And Linux servers that should accept company accounts instead of local ones usually reach for LDAP too.
If none of those apply, you do not need LDAP. If one does, you do not need to run a server room to get it.
Cloud directories instead
Do you need Active Directory? For a cloud-first small business, almost certainly not. Your directory already exists in Google Workspace or Microsoft 365, and you can reach it from older systems without running your own domain controller.
Google Workspace Secure LDAP. Google runs an LDAP service on top of your Workspace directory, so LDAP-only apps and devices can authenticate your users. Per Google's help page, read on 27 October 2026, it is supported on Business Plus, Enterprise Standard and Enterprise Plus, Frontline Standard and Frontline Plus, Education Fundamentals, Standard and Plus, and Enterprise Essentials Plus. It is not listed for Business Starter or Business Standard.
JumpCloud Cloud LDAP. JumpCloud sells a hosted LDAP directory as an à la carte item at $3 per user a month billed annually, or $4 billed monthly, per its pricing page the same day. The same page lists Cloud RADIUS, the piece enterprise Wi-Fi and many VPNs talk to, at the same $3 and $4. JumpCloud pricing covers its packages.
Microsoft Entra Domain Services. For Microsoft shops, Azure offers a managed domain with LDAP and Kerberos, so legacy apps can use your Entra ID users without you running servers. It is billed as an Azure service, by the hour; Microsoft Entra ID pricing covers the Entra tiers themselves.
Can Google Workspace do LDAP? Yes, on the editions above. Can it do SAML SSO? Yes, as an identity provider for apps you add in the Admin console; what an identity provider is covers that side, and Google Workspace as your identity provider covers what it costs.
None of these is a reason to adopt LDAP for cloud tools. Slack, Figma and the rest do not speak LDAP; they speak SAML or OpenID Connect, usually only on a higher plan. That cost, the SSO tax, is a separate problem from your directory.
Moving off an old office server
Some small companies inherited a Windows server in a cupboard that still runs Active Directory for a few PCs and a file share. Getting off it is mostly a matter of order.
List what still talks to it. Check the Wi-Fi, the VPN, the printers, the NAS and any app that asks for a "domain" login. Each one is either moving to a cloud equivalent or needs a hosted LDAP or RADIUS service to point at.
Make the cloud directory the source of truth. Every person who has a domain account should have a Google Workspace or Microsoft 365 account, with MFA on. From that point, new hires go into the cloud directory first and nowhere else.
Repoint the stragglers one at a time. Move each LDAP-only device to Secure LDAP, a hosted LDAP service or its own cloud login, and test it before you touch the next one.
Switch the server off last, after a quiet week with nothing failing. Keep a backup of its directory in case something forgotten turns up.
A five-person office with one NAS can do this in an afternoon. A 50-person company with enterprise Wi-Fi and a VPN should plan it as a short project, with someone owning each system.
What neither one does
LDAP and SSO share a blind spot. Both are about checking who someone is when they try to get in. Neither one goes to Slack, GitHub or HubSpot and removes the account of someone who left. With LDAP, disabling a user in the directory stops future password checks. With SSO, suspending them in the identity provider stops future logins. In both cases, the accounts in each tool stay, often with a paid seat, until someone deletes them. That is provisioning, covered in SCIM vs SAML, and the manual version is an employee offboarding checklist.
Where SmashSSO fits
SmashSSO is not a directory, an LDAP service or SSO. It does not check passwords and does not sit in anyone's login.
It uses the directory you already have. It reads your people from Google Workspace with read-only access, shows who has an account in each cloud tool and with what role, and flags accounts that match nobody. When someone is suspended in Google Workspace, it alerts you and shows every tool where they still have access, and it can remove them through the tool's member API where you have added a token, or through an agent in your own Chrome where you are already signed in as an admin. That browser has to be open, and agent runs can fail when a tool redesigns its screens. It needs Google Workspace as the directory, so it is no help to a company that lives in Active Directory.
It costs a flat fee from $199 a month billed annually (pricing). If a contract needs enforced login through an identity provider, you need SSO for those tools.