LDAP authentication flexibility

[aaroncalderon]

Say, if you use the default behavior of the of ldap for authentication, if your AD implementation does not assign a uid you will get a failed authentication even if there is a valid user on the AD records.

[The module ldap makes] the assumption that result.uid will match the login on ldap.js#L39. That is not the case in all Active Directory deployments (like in my case). So I'm trying to figure out how to address this.

Find a way to let the developer override the everyauth.ldap.authenticate step while providing a reference to ldapauth.

Wait for PR...