After upgrading from 5.2 to 6.0 LDAP authentication against an AD Ldap server is no longer working.
After the upgrade the Ring Auth module was present, but the config had changed. I have now reconfigured it as follows, but I am unable to authenticate.
Server URL: ldap://ldapserver.a.b.c.d:389/DC=a,DC=b,DC=c,DC=d
DN Transform: (sAMAccountName=%u)
Select SSL Key: No Key
Here "a.b.c.d" is our internal domain name, and ldapserver is FQDN to ldap server.
In 5.2 we would have configured "Query" to (sAMACccountName=%u).
When testing this (and several different combinations of Filters and DN Transforms), I only get "User not found", and the youtrack-std-logs has this to say about the autentication :
00:06:13,534 INFO [TrustStoreImpl ] TrustStore is empty -> return default TrustStore
00:06:13,534 INFO [LdapUserDirectory ] a\x12345: auth in LDAP
00:06:13,534 INFO [LdapClient ] Constructed DN: sAMAccountName=x12345
00:06:13,565 ERROR [LdapUserDirectory ] LDAP failure
00:06:13,565 WARN [BaseExceptionMapper ] REST exception for URL: /hub/api/rest/authmodules/0b105f9a-51e7-4d08-be7f-773dfb6a9b37/resolve