Adds LDAP support to SilverStripe including user synchronisation and authentication
This package is auto-updated.
Last update: 2023-01-25 21:15:00 UTC
This Silverstripe module provides integration with LDAP (Lightweight Directory Access Protocol) servers. It comes with two major components:
- Synchronisation of Active Directory users and group memberships via LDAP(S)
- Active Directory authentication via LDAP binding
These components may be used in any combination, also alongside the default Silverstripe authentication scheme.
Install using Composer:
composer require silverstripe/ldap ^1.0
- PHP 5.6+ with extensions: ldap, openssl, dom, and mcrypt
- Silverstripe 4.0+
- An Active Directory server:
- Active Directory on Windows Server 2008 R2 or greater (AD)
- HTTPS endpoint on Silverstripe site
- SSL/StartTLS encrypted LDAP endpoint on Active Directory
This module has been tested using Samba 4. It has also been tested in previous major releases against:
- Windows Server 2008 R2 with ADFS 2.0
- Windows Server 2012 R2 with ADFS 3.0
This module has not been tested on OpenLDAP.
Note: For Silverstripe 3, please see the silverstripe-activedirectory module.
This module will provide an LDAP authenticator for SilverStripe, which will authenticate via LDAPS against members in your AD server. The module comes with tasks to synchronise data between Silverstripe and AD, which can be run on a cron.
To synchronise further personal details, LDAP synchronisation feature can be used, also included in this module. This allows arbitrary fields to be synchronised - including binary fields such as photos. If relevant mappings have been configured in the CMS the module will also automatically maintain Silverstripe group memberships, which opens the way for an AD-centric authorisation.
Note: If you are looking for SSO with SAML, please see the silverstripe-saml module.
With appropriate configuration, this module provides a secure means of authentication and authorisation.
AD user synchronisation and authentication is hidden behind the backend (server to server communication), but must still use encrypted LDAP communication to prevent eavesdropping (either StartTLS or SSL - this is configurable). If the webserver and the AD server are hosted in different locations, a VPN could also be used to further encapsulate the traffic going over the public internet.
Note that the LDAP protocol does not communicate over HTTP. If this is what you're looking for, you may be interested in SAML instead.
- Developer guide - configure your Silverstripe site
- CMS usage guide - manage LDAP group mappings
- Troubleshooting - common problems
Please see the GitHub releases for changes.