LDAP: Auth.info Bind successful but user was not found via search 'DN'

Description:

LDAP: Authentication error

Steps to reproduce:

Login with current AD credentials for any user.

Expected behavior:

Successful login.

Actual behavior:

It returns that message: User not found or incorrect password (only works with old cached passwords - Login Fallback).

Server Setup Information:

• Version of Rocket.Chat Server: 0.66.2
• Operating System: Ubuntu 16.04.3 LTS
• Deployment Method: Snap
• Number of Running Instances: 1
• DB Replicaset Oplog: Enabled
• NodeJS Version: 8.11.3
• MongoDB Version: 3.2.7

Additional context

Recent issue - Installed since spring 2017.

Relevant logs:

20180718-17:31:38.427(-3) LDAP Auth.info Authenticating CN=testuser,OU=Users,DC=domain,DC=local
20180718-17:31:38.661(-3) LDAP Search.info Search result count 0
20180718-17:31:38.664(-3) LDAP Auth.info Bind successful but user was not found via search CN=testuser,OU=Users,DC=domain,DC=local { scope: 'sub', filter: PresenceFilter { attribute: 'objectclass', type: [Getter], json: [Getter] } }
20180718-17:31:38.665(-3) LDAPHandler info Wrong password for testuser
20180718-17:31:38.667(-3) LDAPHandler info Fallback to default account system { username: 'testuser' }

Testing:

ldapsearch -H ldap://172.16.100.1 -x -s sub -b 'cn=testuser,ou=Users,dc=domain,dc=local'

extended LDIF

LDAPv3
base <cn=testuser,ou=Users,dc=domain,dc=local> with scope subtree
filter: (objectclass=*)
requesting: ALL

Testuser , Users, domain.local
dn: CN=testuser,OU=Users,DC=domain,DC=local

objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: user
cn: Testuser
[...]

No source file or test is named. Start by tracing the LDAP authentication and user-search flow that produces the reported log messages, then reproduce the Active Directory login with the supplied search parameters. Done means a successful bind finds the user and login no longer falls back to the cached-password account system.