Simple LDAP Login
Connect WordPress accounts to Active Directory or OpenLDAP, with group access rules and automatic account creation.
Solid choice
Simple LDAP Login is a solid plugin choice in 2026, with a few things worth checking first. It runs on 1K+ sites, is rated 4.3/5 and was last updated 1 day ago, and scores 79/100 on our health check.
- Actively developed — last update 1 day ago
- Tested with the latest WordPress (7.1)
- Momentum — downloads up 222.1% vs the previous 30 days
- Needs PHP 8.1 or newer
How does it stack up?
Side-by-side on installs, updates, ratings & supportDaily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Simple LDAP Login stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| active directory | #20 |
| authentication | >100 |
| ldap | #2 |
| login | #93 |
Version adoption
Share of active sites per release.
Rating breakdown
★★★★★★★★★★ 4.3 from 18 reviews
About Simple LDAP Login
From the official readme · v2.0.1Description
LDAP login for WordPress
Simple LDAP Login lets staff sign in to WordPress with their existing Active Directory or OpenLDAP account. Simple LDAP Login checks directory credentials, applies group access rules, and can create a WordPress account after a valid login.
Use it for staff sites, company intranets, and other WordPress sites that share an LDAP directory. Free includes LDAP password login, encrypted connections, group restrictions, and local administrator recovery. No paid license or PaidCommunities account is required for these features.
Need backup servers or single sign-on? Simple LDAP Login Pro adds backup LDAP servers, server SSO, automatic LDAP field mapping, group role rules, and profile updates. Enterprise adds scheduled account management, multisite membership rules, and audit history.
Use the directory accounts you already have
Connect to Active Directory or OpenLDAP. Authenticate existing WordPress users, or create accounts after their first valid directory login. Set the default WordPress role for new accounts and map standard profile fields to your directory attributes.
Control access with LDAP groups
Limit login to members of one or more LDAP groups. Active Directory checks include nested and primary groups. Keep account creation off when only existing WordPress users should have access.
Protect directory connections
Use StartTLS or LDAPS with a trusted server certificate. A failed TLS connection stops the login attempt. Plain LDAP requires an explicit setting. LDAP passwords are not stored as WordPress passwords.
Keep a local way to recover access
Choose local administrator accounts that can sign in with their WordPress passwords. Connection and login tests let you check the setup before you enable LDAP. These tests do not create users or login sessions.
Free features
- Active Directory and OpenLDAP password login.
- One LDAP server, with configurable port and connection timeout.
- StartTLS and LDAPS with certificate checks.
- Login restrictions based on LDAP groups.
- Nested and primary Active Directory group checks.
- Optional WordPress account creation and a default role.
- Directory attribute mapping for standard profile fields.
- The
sll_user_meta_datafilter for integration-supplied metadata. - Local administrator recovery and LDAP-only login settings.
- Site settings and central network settings for WordPress multisite.
- Separate connection and login tests.
- Translations for 24 locales.
Pro and Enterprise
Pro: USD 99 per year for one site. Add backup LDAP servers, single sign-on from a trusted web server, automatic LDAP field mapping, group-to-role rules, and profile updates at login.
Enterprise: USD 499 per year for one site. Includes Pro plus scheduled account import, access and session removal, multisite membership rules, and audit history with retention and CSV export.
Both plans use the same paid plugin ZIP. Pro replaces Free; you do not run both plugins together. Your license selects the available features. Purchase links open each plan’s checkout on PaidCommunities.
Upgrading from version 1.x
Back up the database and test the upgrade on a site copy. Version 2.0 requires WordPress 6.5 and PHP 8.1 or later.
Backup LDAP servers, server SSO, and automatic LDAP-to-user-meta mapping require Pro or Enterprise in version 2.0.1. If your 1.x site uses these features, install the Pro ZIP directly and activate a paid license. Free keeps the saved settings but does not run these paid features.
The sll_user_meta_data filter works in Free without a license. Integrations can supply custom metadata through this filter. Automatic LDAP attribute mappings require Pro or Enterprise.
Older settings are backed up before migration. Existing sites keep the legacy administrator recovery rule. If a saved search password cannot be read, enter it again.
Support and contributions
Read the setup guide and plugin documentation. Use the WordPress.org support forum for help with Free. Report bugs or contribute code in the GitHub repository. Do not include directory passwords, license keys, or other secrets in a public support request.
External services
LDAP requests go only to the directory servers that an administrator configures. Free LDAP login does not require an external license service.
The optional Go Pro tab links to PaidCommunities checkout. It does not load commerce scripts or send license requests. When you open a purchase link, PaidCommunities receives the product and plan IDs, your IP address, and browser details. It also receives the purchase and payment details that you enter during checkout.
The paid plugin uses PaidCommunities for license activation and updates. Activation sends the license key, site domain, plugin version, and product ID. Later checks use a site activation secret. Requests also include the server IP address and standard WordPress HTTP headers. LDAP settings, bind passwords, login passwords, and directory user records are not sent to PaidCommunities. Login uses saved license status and does not contact the service.
Free keeps WordPress.org updates. A purchase or license activation does not install the paid plugin automatically.
- Simple LDAP Login privacy policy
- Simple LDAP Login terms and conditions
- PaidCommunities service documentation
- PaidCommunities checkout documentation
Developer Hooks
Use WordPress add_filter() and add_action() in an integration plugin. Register callbacks before login. Set the accepted argument count when a callback needs more than one argument. Filters must return the value described below.
Login and account filters
sll_get_setting( $value, $key ): Return a setting value. The old global settings object also uses this filter.sll_force_ldap( $allow_recovery ): Returnfalseto require LDAP for administrators in legacy recovery mode. The inverted name is retained for compatibility. Selected recovery accounts and Off mode do not use this filter.sll_remove_default_authentication_hook( $exclusive ): Returntrueto block local password fallback, orfalseto allow normal fallback. The filter no longer removes WordPress authentication handlers. Group denial still blocks fallback for users without a recovery exception.sll_ldap_auth( $bound ): Receives a boolean bind result for password login and server SSO. Returnfalseto reject it. A callback cannot make a failed bind or invalid directory identity valid.sll_user_has_groups( $allowed ): Return a boolean group access result. This filter also runs when no required groups are configured.sll_user_data( $data ): Return the array passed towp_insert_user(). It runs only for new accounts. Fields includeuser_login,user_nicename,user_pass,user_email,display_name,first_name,last_name,user_url, androle. The local password is random, not the LDAP password.sll_user_meta_data( $values ): Return an array of metadata names and scalar values, orfalseto skip writes. This filter works in every edition without a license. Free supplies an empty array. Licensed Pro supplies values from its automatic LDAP mappings. Integrations can add values in either edition.sll_account_verified( $user, $entry ): Return theWP_Useror aWP_Errorto reject the directory account before account update actions. A new account can already have been created at this point.
Metadata names receive the saved LDAP and WordPress suffixes. For example, department writes department_ldap and department_wp with the default settings. Local edits remain until the callback’s source value changes. Protected account keys and non-scalar values are rejected. Selected local recovery accounts do not receive these directory updates.
Example: supply a custom value without the Pro mapping feature:
add_filter( 'sll_user_meta_data', function ( $values ) {
$values['directory_source'] = 'staff';
return $values;
} );
Directory and settings filters
sll_ldap_hosts( $hosts, $settings ): Return server addresses. Free supplies the primary server. The licensed paid module supplies backup servers.sll_ldap_attributes( $attributes ): Return LDAP attribute names to request. Invalid attribute names are removed.sll_ldap_entry( $data, $connection, $entry, $username ): Return the verified directory attribute array, orWP_Errorto reject it. The connection and entry are the bundled LdapRecord objects. The array includesdn.sll_mapped_user_meta_data( $values, $entry ): Supplies initial metadata values beforesll_user_meta_data. Pro uses this hook for licensed LDAP mappings. Integrations that only supply custom values should usesll_user_meta_data.sll_settings_defaults( $defaults ): Return the default settings array.sll_validate_setting( $result, $key, $value, $settings ): Returnnullto use built-in validation, a validated value to store it, orWP_Errorto reject the save.sll_settings_tabs( $tabs ): Return an array of settings tab keys and labels.
Actions
sll_loaded( $settings, $auth ): Shared settings and authentication services are ready.sll_account_loaded( $user, $entry ): The directory account resolved to a WordPress user and passedsll_account_verified. Account modules use this action to update data. It can also run during scheduled imports.sll_auth_success( $user ): An LDAP account passed the WordPress user check. It runs for new and existing accounts. Later authentication filters can still reject login; use WordPresswp_loginfor a completed login.sll_auth_failure(): A password login received an LDAP error. It does not report every WordPress login failure.sll_settings_saved( $settings, $before, $after ): A settings save succeeded. The arrays contain the previous and new settings.sll_settings_notices(): Add settings-page notices.sll_access_settings( $admin ),sll_profile_settings( $admin ), andsll_advanced_settings( $admin ): Add controls to the corresponding settings section.sll_settings_page_{tab}( $admin ): Render a custom page for a registered tab without the standard settings form.sll_settings_tab_{tab}( $admin ): Add controls for a registered tab inside the standard settings form.
Existing filter names and argument order are retained. Callbacks that use the removed adLDAP object or that permit failed LDAP binds must change. Do not send passwords or directory records to external services from a callback.
Installation
- Install PHP 8.1 or later with the LDAP, OpenSSL, and iconv extensions.
- Upload the release ZIP through Plugins > Add New Plugin, or use the WordPress plugin directory.
- Activate Simple LDAP Login.
- Open Settings > Simple LDAP Login. For network activation, use Network Admin > Settings.
- Enter the directory connection details. Use StartTLS or LDAPS and a trusted server certificate.
- Save the settings and run the connection and login tests.
- Choose local recovery access on the Access tab. Keep your administrator session open, enable LDAP login, and test it in another browser.
A release ZIP includes its dependencies. Do not install an unbuilt source archive.
Changelog
Restores integration filters and documents their behavior. The metadata filter works in Free. Automatic LDAP mappings remain paid. Failed binds remain blocked.
2.0.1
- Restore the public metadata filter in Free without requiring a paid license.
- Keep automatic LDAP metadata mappings in the paid plans.
- Restore the user_nicename field for account creation filters.
- Run the LDAP authentication filter for server SSO and failed binds.
- Document filter arguments, actions, and compatibility limits.
2.0.0
- Update the plugin for WordPress 6.5 and PHP 8.1 or later.
- Redesign the settings screens for desktop and mobile.
- Add separate connection and login tests to check settings before enabling LDAP.
- Add selected local administrator recovery accounts and an option to turn recovery access off.
- Back up existing settings before upgrades and preserve site settings, network settings, and recovery access.
- Improve TLS validation and protect user account data during login.
- Keep other WordPress authentication checks active during LDAP login.
- Add translations for 23 additional locales.
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Simple LDAP Login alternatives
All active directory plugins →FAQ
Simple LDAP Login: quick answers
Straight answers, pulled from live WordPress.org data.
Source: WordPress.org
Is Simple LDAP Login free?
Yes. Simple LDAP Login is free to download and use from the official WordPress.org plugin directory.
Is Simple LDAP Login safe to use in 2026?
Simple LDAP Login is a solid plugin choice in 2026, with a few things worth checking first. It runs on 1K+ sites, is rated 4.3/5 and was last updated 1 day ago, and scores 79/100 on our health check.
How many websites use Simple LDAP Login?
Simple LDAP Login is active on 1K+ WordPress websites and has been downloaded 113,392 times since it launched in October 2008. It was downloaded 1,150 times in the last 30 days.
Does Simple LDAP Login work with WordPress 7.1?
Yes. The developer has tested Simple LDAP Login up to WordPress 7.1.5, the latest release. It requires WordPress 6.5 or newer.
What PHP version does Simple LDAP Login need?
Simple LDAP Login requires PHP 8.1 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Simple LDAP Login last updated?
The latest version, 2.0.1, was released on November 19, 2026 (1 day ago).
Who makes Simple LDAP Login?
Simple LDAP Login is developed and maintained by Clifton Griffin.
What are the best alternatives to Simple LDAP Login?
The most popular alternatives to Simple LDAP Login are authLdap (4K+ installs), Active Directory Integratio… (4K+ installs) and Next Active Directory Integ… (2K+ installs).
Powered by PageForge
One template and a spreadsheet. A real page for every search.
PageForge turns each row of a CSV into a WordPress page with its own title, URL, SEO fields and schema, built on the layout you already designed. Free on WordPress.org.
- CSV and XLSX, plus Google Sheets on Professional and Enterprise
- Its own title, URL, SEO fields and schema for every page
- Works with the block editor, Elementor, Divi and Avada
- Free on WordPress.org, no credit card




