A ldap_authentified user can rename itself to one already existing in the ldap database. Like other drupal users, it should have been checked if a user with the other name already existed.
Probably, after having changed his user name to another one, he cannot login a next time, not knowing the other person's password.

Comments

pablobm’s picture

pablobm commented

???

Such thing isn't happenind here. And if it did, it would be really weird, as the module has nothing to say there: that check is done by Drupal itself, and ldap users exist always in the database (as stub users, even if they are not used at login).

Anybody else can cerify confirm this, please?.

pablobm’s picture

pablobm commented

Or, rather than "cerify", I would like somebody to "verify" this. :P

jpulles’s picture

jpulles commented

Maybe I need to clarify the problem. The error occurs when not all ldap users are present in the drupal database. My assumption was that drupal checks the drupal database, but that the ldap authentication module should check it's own == ldap database.

pablobm’s picture

pablobm commented
Status: Active » Closed (duplicate)

This is a different view of issue #37673, so I'm marking this as a duplicate and moving to discuss it there.