trio.so
Explained

LDAP Alternatives: What Replaces LDAP and Active Directory Today

What replaces LDAP and Active Directory today: SAML and OIDC SSO, SCIM, cloud directories, FreeIPA and Samba, with a table to choose by situation.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

The modern alternatives to LDAP are single sign-on standards (SAML and OpenID Connect) for signing users in to apps, SCIM for creating and removing user accounts, and a cloud directory or identity provider such as Microsoft Entra ID, Google Workspace or Okta to hold the users. If you need a self-hosted replacement for Active Directory instead, the usual choices are FreeIPA for Linux-heavy environments and Samba for an Active Directory compatible domain. Most companies end up with a mix, because printers, NAS devices, Wi-Fi authentication and older apps often still need LDAP or Kerberos.

If you are planning a move off an on-premises directory, the table near the end matches each situation to a route; the sections before it explain what each option replaces and what it does not.

Two jobs: replacing the protocol and replacing the directory

"Replace LDAP" usually means one of two things, and they have different answers.

  • Replacing the protocol. Apps that "bind" to an LDAP server to check a password or look up a group. The modern replacement is single sign-on: the app trusts an identity provider through SAML or OpenID Connect, and user accounts are created and removed through SCIM.
  • Replacing the directory. The server that holds users, groups and computers, most often Active Directory. The replacement is a cloud directory, a managed domain service, or another self-hosted directory.

LDAP (Lightweight Directory Access Protocol) itself is a standard way to read and write a directory over the network, on port 389, or 636 for LDAPS. Active Directory uses LDAP for directory access and Kerberos for sign-in, plus Group Policy and DNS. For the details, see LDAP vs Active Directory.

Is LDAP still used?

Yes, widely. Active Directory, OpenLDAP and 389 Directory Server all speak it, and many systems still expect it: network printers and scanners, NAS storage, Wi-Fi and VPN authentication through RADIUS, Linux servers, and older business apps. What has changed is that new apps, especially SaaS, almost never ask for LDAP. They expect SAML or OpenID Connect for sign-in and SCIM for accounts.

Modern alternatives to the LDAP protocol

SAML and OpenID Connect for single sign-on

With SAML 2.0 or OpenID Connect (OIDC), an app never sees the user's password. It sends the user to the identity provider, which signs them in, applies multi-factor authentication and returns a signed answer. SAML is common in business SaaS apps; OIDC, built on OAuth 2.0, is common in newer apps and mobile apps.

LDAP vs SAML: LDAP is a directory protocol: the app asks the directory to check a password it received. SAML is a single sign-on protocol: the app trusts a signed statement from the identity provider and never handles the password. That is why SAML is easier to secure with multi-factor authentication.

SCIM for user provisioning

SCIM 2.0 is a standard API the identity provider uses to create, update and disable accounts in each app. Where an app used to read users from LDAP, SCIM pushes them in, and removes access as soon as someone leaves.

Kerberos and RADIUS where they still fit

Windows sign-in on a domain uses Kerberos, and Wi-Fi with 802.1X usually uses RADIUS, often backed by a directory. These don't disappear when you move apps to SSO. Plan for them separately.

Active Directory alternatives

Cloud directories and identity providers

  • Microsoft Entra ID (formerly Azure AD): Microsoft's cloud identity service, with single sign-on, multi-factor authentication, Conditional Access and SCIM provisioning. It does not offer LDAP to apps by itself. For apps that need LDAP or Kerberos, Microsoft offers Microsoft Entra Domain Services, a managed domain. Moving users from Active Directory is covered in our Active Directory migration checklist.
  • Google Workspace and Cloud Identity: Google's directory, with SAML and OIDC single sign-on and SCIM provisioning. Its Secure LDAP service, available in some editions, gives older apps an LDAP endpoint.
  • Okta and other identity providers: independent identity platforms with single sign-on, multi-factor authentication and provisioning. Okta also offers an LDAP interface for apps that cannot use SSO.
  • Directory-as-a-service products: some vendors host a cloud directory with LDAP and RADIUS endpoints built in. See our directory-as-a-service comparison.

Managed directories in the cloud

If you need a real domain without running domain controllers, Microsoft Entra Domain Services and AWS Directory Service (AWS Managed Microsoft AD, or Simple AD for small needs) host it for you. Apps keep LDAP and Kerberos, and you stop patching the servers.

Self-hosted and open-source options

  • FreeIPA: an identity system for Linux that combines 389 Directory Server, MIT Kerberos, a certificate authority and DNS. It can set up a trust with Active Directory. A good fit for Linux-heavy environments with in-house skills.
  • Samba: can run an Active Directory compatible domain controller that Windows PCs join, with Group Policy support. A free Active Directory alternative for smaller Windows networks, with fewer features than the newest Windows Server.
  • OpenLDAP and 389 Directory Server: plain LDAP servers. A lighter choice when apps need an LDAP directory but not the rest of Active Directory. They need LDAP skills to run.

Which LDAP or Active Directory alternative fits your situation

Your situationUsual routeKeep in mind
Mostly SaaS apps, Microsoft 365Microsoft Entra ID with SSO and SCIMOld apps and devices that need LDAP need a plan
Mostly SaaS apps, Google WorkspaceGoogle Workspace or Cloud Identity with SSO and SCIMSecure LDAP depends on your edition
Mixed vendors, no preferred suiteAn independent identity provider such as OktaLicense cost per user
Windows domain that must stay, but no serversMicrosoft Entra Domain Services or AWS Managed Microsoft ADFeature differences from your own domain controllers
Linux servers and in-house skillsFreeIPAYou run and patch it
Small Windows network, tight budgetSamba as an AD compatible domainTest Group Policy and app compatibility first
Apps need LDAP onlyOpenLDAP or 389 Directory Server, or an LDAP interface from your identity providerLDAP skills needed

What still needs LDAP or Kerberos

Before you switch anything off, list what binds to your directory today. Common ones:

  • Network printers and scanners that look up users or email addresses.
  • NAS and file servers.
  • Wi-Fi and VPN authentication through RADIUS.
  • Linux servers that use the directory for sign-in.
  • Older business apps, and anything with a domain controller's name hard-coded.

Each needs a new home: SSO if the vendor supports it, an LDAP interface from your identity provider, a managed domain, or a small LDAP server kept for that purpose. Run the old and new side by side until nothing uses the old directory. Our guides on Active Directory security and cleaning up Active Directory help while both run.

Choosing the right alternative: factors to consider

  • Apps: how many support SAML or OIDC and SCIM, and how many only speak LDAP.
  • Devices: Windows PCs joined to a domain, Macs, Linux, phones. How will each sign in and get settings? For Macs, see how to add a Mac to Active Directory.
  • Security: multi-factor authentication, Conditional Access, and how quickly access ends when someone leaves.
  • Cost: per-user licenses for cloud services against the servers and time for self-hosted ones.
  • Skills: FreeIPA, Samba and OpenLDAP need people who can run them.
  • Lock-in: standards such as SAML, OIDC and SCIM make it easier to change providers later.

Managing this across many devices

Once users live in a cloud directory, the device side should follow the same identities. trio.so supports SAML single sign on, and SCIM 2.0 user provisioning with Microsoft Entra ID. Users can be synced from Microsoft Entra ID or Google Workspace. It does not act as an LDAP server. See single sign on.

The trio.so Authentication and Security settings, Sign-in tab, with single sign on through Microsoft Entra ID turned on.
Single sign on with Microsoft Entra ID in the trio.so settings.

Related reading: LDAP vs Active Directory, Active Directory migration, Active Directory security and SSO integration with MDM.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Sign users in without an LDAP server

trio.so supports SAML single sign-on and SCIM provisioning with Microsoft Entra ID.

Start free trial

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

For signing users in to apps, SAML or OpenID Connect single sign-on with an identity provider, plus SCIM to create and remove accounts. For the directory itself, a cloud directory such as Microsoft Entra ID or Google Workspace, or a self-hosted one such as FreeIPA.

Yes. Active Directory, OpenLDAP and many printers, NAS devices, VPNs and older apps still use it. New SaaS apps generally use SAML or OpenID Connect instead.

For cloud-first companies, Microsoft Entra ID or Google Workspace with single sign-on. If you need a domain without servers, a managed service such as Microsoft Entra Domain Services. For self-hosting, FreeIPA (Linux) or Samba (Windows-compatible).

Yes. Samba can run an Active Directory compatible domain, and FreeIPA and OpenLDAP are free and open source. You pay in setup and running time instead of licenses.

LDAP lets an app read a directory and check a password it was given. SAML lets an app trust a signed sign-in from an identity provider, so the app never handles the password and multi-factor authentication happens at the provider.

Related

From the blog

The related industry news, interviews, technologies, and resources.