I am using LDAP to authenticate users in mixed mode (both Drupal accounts and LDAP accounts work). A user logs in via LDAP for the first time, the account is created in Drupal and a field "Full Name" (in the user profile) containing the user's full name is populated. The full name is than used by Real Name and assigned as the username.

The next time the user attempts to log in, they get an error that an account already exists with that email and they are not allowed the log in. Since Real Name replaced the username with the value from "Full Name", the username no longer matches the one coming from LDAP. The following error is recorded:

"LDAP user username (LDAP DN info listed) ... has email address (%mail) conflict with a Drupal user User Name"

'username' is the actual username and 'User Name' is the value from 'full name'...

Disabling Real Name fixes the conflict and the user is once again able to log in.

Comments

topazzz created an issue. See original summary.

topazzz’s picture

topazzz commented
Title: Real Name break LDAP authentication » Real Name breaks LDAP authentication
hass’s picture

hass commented
Category: Bug report » Support request
Priority: Major » Normal
Status: Active » Fixed

That is not a bug of realname.

I do not understand how this works what you describe, but it is clear that displayname is used somewhere where it must not used. The broken module need to use accountname and not display name for the username.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.