Ldap.config host requires 'ldap://...' indication

[tiagojulianoferreira]

Just reporting something that might help with LDAP settings in version 3.0.3.

When migrating from BookedSchedule version 2.8 to LibreBooking 3.0.3, we tried to faithfully replicate the LDAP settings from the old version to the new version.

However, the LDAP connection didn't work and prevented administrative access to the entire application.

The solution was to add the ldap:// suffix before host.

In BookedSchedule, where it was:

$conf['settings']['host'] = 'ldap.example.com';

In LibreBooking 3.0.3, we changed it to:

$conf['settings']['host'] = 'ldap://ldap.example.com';

Hope this helps!

[JohnVillalovos]

Thanks @tiagojulianoferreira I tried to show this in commit 03d6384 but very very easy to miss if doing an upgrade.

[soumik-com]

Thanks @tiagojulianoferreira I tried to show this in commit 03d6384 but very very easy to miss if doing an upgrade.

If we use the port 636, do we still use 'ldap://ldap.example.com' or 'ldaps://ldap.example.com'?