Back to overview

Advanced LDAP

Add it on-the-fly to your HumHub by activating it in the Modules menu! ("Administration -> Modules")

Advanced LDAP

This module provides advanced LDAP functions.

  • LDAP Mappings (User to group or space)
  • Synchronize attached LDAP profile images
  • Support for multiple LDAP servers/connections

User Mapping

You can assign user's group or space memberships automatically using LDAP configuration.

The mapping can be used by:

  • User LDAP group memberships (memberOf field, e.g. CN=xyz_space_access,OU=Groups,DC=example,DC=com)
  • The part of the users base DN (e.g. OU=People,DC=example,DC=com)
  • Attribute values (e.g. street==Some Street or street=~Street)

Note: The mapping is handled by the hourly cron job and may takes some time to affect.

Space Mapping

As administrative user, you can map a LDAP group directly to a space.

Configuration page: Open Space -> Members -> LDAP

Space LDAP Mapping

Group Mapping

As administrative user, you can map a LDAP group against HumHub groups which are mainly used for administrative tasks.

Configuration page: Administration -> Users -> Groups -> Select a group -> LDAP

Group LDAP Mapping

Profile Images

You can also synchronize profile image from LDAP.

Modify your local configuration protected/config/common.php and add following section:


return [
    'components' => [
        'authClientCollection' => [
            'clients' => [
                'ldap' => [
                    'class' => 'humhub\modules\advancedLdap\authclient\LdapAuth',
                    'profileImageAttribute' => 'thumbnailphoto'



Add following part into the components section of your configuration file.

'search' => [
    'class' => 'humhub\modules\solr\engine\SolrSearch',
    'host' => 'solr-host-name-here', // e.g. localhost
    'port' => 12345, // e.g. 8983
    'path' => 'solr-path', // e.g. /solr/example1
    'username' => 'optional-user-name',
    'password' => 'optional-password',

More information about the individual configuration can be found here:

Apache SOLR Configuration

Use the standard managed schema mode (schemaless).

Search core creation example:

cd bin
./solr create -c example1

Tweak default field type:

Edit the file server/solr/example1/conf/solrconfig.xml and change:

<str name="defaultFieldType">strings</str>


<str name="defaultFieldType">string</str>

Restart the SOLR search server:

cd bin
./solr restart

Active the SOLR search

Rebuild your search index and check your Apache SOLR status page.


Change following field types:

curl -X POST -H 'Content-type:application/json' --data-binary '{
     "stored":false }
}' http://localhost:8983/solr/example1/schema
curl -X POST -H 'Content-type:application/json' --data-binary '{
     "stored":false }
}' http://localhost:8983/solr/example1/schema

1.0.2 (July 31 2020)

  • Fix: Migration Path for older HumHub installations (1.2) broken
  • Fix: Remove 'count' value in 'memberOf' list provided by some LDAP servers

1.0.1 (July 30 2020)

  • Fix: Compatiblity issue with HumHub 1.6+

1.0.0 (November 11, 2019)

  • Enh: Initial release of standalone version
1.0.2 (released 8 months ago)

HumHub GmbH & Co. KG


HumHub 1.4 - Latest

Professional Edition

This module is part of the Professional Edition.