
RADIUS vs LDAP: seven key differences between the two authentication protocols and tips for deploying them.
What replaces LDAP and Active Directory today: SAML and OIDC SSO, SCIM, cloud directories, FreeIPA and Samba, with a table to choose by situation.


Content writer, trio.so
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.
"Replace LDAP" usually means one of two things, and they have different answers.
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.
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.
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 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.
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.
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.
| Your situation | Usual route | Keep in mind |
|---|---|---|
| Mostly SaaS apps, Microsoft 365 | Microsoft Entra ID with SSO and SCIM | Old apps and devices that need LDAP need a plan |
| Mostly SaaS apps, Google Workspace | Google Workspace or Cloud Identity with SSO and SCIM | Secure LDAP depends on your edition |
| Mixed vendors, no preferred suite | An independent identity provider such as Okta | License cost per user |
| Windows domain that must stay, but no servers | Microsoft Entra Domain Services or AWS Managed Microsoft AD | Feature differences from your own domain controllers |
| Linux servers and in-house skills | FreeIPA | You run and patch it |
| Small Windows network, tight budget | Samba as an AD compatible domain | Test Group Policy and app compatibility first |
| Apps need LDAP only | OpenLDAP or 389 Directory Server, or an LDAP interface from your identity provider | LDAP skills needed |
Before you switch anything off, list what binds to your directory today. Common ones:
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.
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.

Related reading: LDAP vs Active Directory, Active Directory migration, Active Directory security and SSO integration with MDM.
trio.so supports SAML single sign-on and SCIM provisioning with Microsoft Entra ID.
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.
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.





Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.
Related
The related industry news, interviews, technologies, and resources.

RADIUS vs LDAP: seven key differences between the two authentication protocols and tips for deploying them.

Wondering how to optimize your IT strategy? The domainless enterprise model offers a revolutionary approach to managing modern IT landscapes.

Compare top 8 Directory as a Service platforms designed for mixed fleets and hybrid identity. Find the right solution for your organization.

An Active Directory migration checklist and project plan: assess, prepare, migrate users and computers, cut over, and the tools for each path.

How are things organized in a directory server? Explore its hierarchical structure, key components, best practices, and why they are essential.

Streamline your IT operations with our guide to organizing and cleaning up Active Directory.

Discover how active directory bridging integrates multiple platforms into one AD environment, enhancing security, scalability, and management efficiency.

Exploring the intricacies of Active Directory security, its potential vulnerabilities, and best practices for maintaining a robust defense against cyber attacks.
14-day free trial. No credit card required.
trio.so for MSPs: one console, separate clients