5.0.0 LTS / Ldap Auth Problem

[eduwutzl]

Hi,

Today we upgraded from version 4.4 to 5.0.0 LTS and broke up with a problem with ldap authentication.

Before it was in perfect working order, the data was not changed and we have a production environment with the same data and we continue to work.

Someone with LDAP version 5.0.0 LTS integration problems?

[Gabbs]

It broke mine too. Previously the URI to my "LDAP host" entry was ldaps://1.2.3.4 and port 636. I'm using an OpenLDAP server and Secure LDAP. After the upgrade I had to fiddle with it and finally settled on changing the URI from sldap:// to ldap:// and left port on 636. That was the only way to get it to work, but don't understand why it broke in the first place.

[francesc.bassas]

Hi,

in my case, after upgrading, with ldaps://my.domain.com and port 636 works. Using docker distribution.

Regards.

[eduwutzl]

Well, mine has also returned to work, after I removed the various commas informing contingency servers and leaving only a single IP address, without informing the communication protocol and port.

Something has changed in the frontend and I don't think it was well documented.