Version 2.0.1 requirements

Check WordPress and PHP requirements, package installation, and supported directory configurations.

Changes in 2.0.1

sll_user_meta_data works in Free without a license. Integrations can return custom values through this filter. Automatic LDAP-to-user-meta mapping requires an active Pro or Enterprise license.

Version 2.0.1 restores user_nicename in the account creation filter and calls sll_ldap_auth for server SSO and failed binds. A filter cannot permit a failed bind. See developer hooks.

System requirements

  • WordPress 6.5 or later.
  • PHP 8.1 or later with the LDAP, OpenSSL, and iconv extensions.
  • Network access from the WordPress server to Active Directory or OpenLDAP.
  • A trusted directory certificate for StartTLS or LDAPS.

Free and Pro packages

Install one edition. Free and Pro use the same simple-ldap-login folder and settings. Pro replaces Free; it is not an add-on. An installable ZIP does not require Composer or Node on the WordPress server.

Free includes LDAP password authentication, required groups, account creation, standard profile attributes on new accounts, central network settings, and the public metadata filter. The Pro plan adds backup LDAP servers, server SSO, automatic LDAP-to-user-meta mapping, group role rules, and profile updates. The Enterprise plan adds scheduled account tasks, multisite membership rules, and audit history. Both plans use the same Pro ZIP.

Installation and updates

Use the ZIP for your selected edition. Open Plugins → Add New Plugin → Upload Plugin in WordPress. Keep a separate local administrator account and test the connection before you enable LDAP login.

Paid features require an active Pro or Enterprise license. Free receives updates from WordPress.org. The paid package receives updates through PaidCommunities with an active license. You can also install a new Pro ZIP through WordPress. See Pro and Enterprise licensing.

Directory and network scope

The plugin uses one configured directory. With Pro or Enterprise, a server list supplies failover for that directory. It does not combine independent directories. Network activation applies central settings in the current WordPress network. Network configuration templates are not included.

Server SSO requires a separately configured web server authentication service that sets REMOTE_USER. The plugin does not configure Kerberos, NTLM, Apache, Nginx, or a reverse proxy. See Server single sign-on.

Installation guides

Use Installation and setup for a new site. Use Upgrade from version 1.x for an existing installation. Test certificate trust, group rules, account creation, and administrator recovery on a site copy before you apply a change to a live site.