Nexus Repository 2 makes two LDAP user search queries per configured LDAP server when the inbound request userid is not found

Configure Nexus for LDAP using standard settings in the LDAP connection, then try to access a resource with a user ID that doesn't exist in the LDAP server

curl -u fubar:fubar http://localhost:8081/nexus/service/local/status

You will see that the exact same query is made twice to the LDAP server.

For successful authentication the query is only made once.

Expected

A single LDAP search query per configured LDAP server should be all that is needed per inbound request, to attempt to authenticate the provided user name.