Closed (won't fix)
Project:
LDAP integration
Version:
5.x-1.3
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Jun 2007 at 22:29 UTC
Updated:
6 Aug 2011 at 18:27 UTC
Jump to comment: Most recent file
Comments
Comment #1
pcorbett commentedGood idea, I'll fix it myself and send you the code.
Comment #2
kreaper commentedpcorbett
Were you able to make a patch ? We can roll that into the 5.x-1.4/HEAD
kreaper
Comment #3
kreaper commentedldapauth module now has the code to retrieve the email address and set it accordingly, if available.
This is available in 5.x.1.3 and in HEAD
Comment #4
pcorbett commentedHmm... I upgraded but the email field is still not being filled automatically. I'm quite sure the fieldname is set properly. Any suggestions? I'm using ActiveDirectory not LDAP, fyi.
Another thing - using the garland default theme, the ldap menu looks a bit odd in IE and Firefox. In IE there is a bolding issue as you can see by the attached photo. You can see it extends to my admin menu as well (the bolding). In Firefox, the LDAP menu pulldowns that were bold in IE are invisible/gone in Firefox - the titles and arrow are, the rest (blue lines) appear, but nothing can be clicked to show what is in each of those areas (like "Security Options").
Comment #5
emdalton commentedI'm at 5.x-1.3 and I still don't get email information when a new account is created through LDAP/Active Directory. I've tried "mail", "smtp", and "SMTP" as values for the "email attribute" setting. The rest of my LDAP authentication is working just fine. So if the patch is in 5.x-1.3, I don't think the problem is solved yet... or possibly I have the wrong email attribute setting. Any suggestions about values for this field would be very welcome.
Comment #6
emdalton commentedI've discovered that the LDAP integration module is actually erasing email addresses stored in the user account if it can't get a value from the LDAP/AD server. I think this is a pretty bad failure mode. The old version at least left existing values alone. Now my users suddenly don't get notices from the system any more, because their address has been replaced by null.
I'd like to suggest that the system check for a null return from the email address call and if null, don't change the current email value for the user.
Comment #7
scafmac commentedpcorbett - Did you figure out the problem? What type of server are you authenticating against? What is currently in the mail attribute field? What is the attribute name on your ldap server? BTW none of the ldap_integration settings are supposed to defeat core's email requirement, only make it easier to populate it from LDAP and hide it from the drupal user.
emdalton, can you provide a bit more information? I have been unable to reproduce the email address getting overwritten. Are you using AD or LDAP? What is the mail attribute name on your ldap server? You need to know that - neither we nor the module can figure that out for you:
Comment #8
pcorbett commentedI'm authenticating against a Windows 2000 Active Directory server. My code base has been modified to run on SQL Server 2000 on IIS, however, I don't believe that should have much to do with anything in this particular instance. The e-mail field that my AD server uses is called UserPrincipalName. When I go to edit a user who has been added via ldap integration, the email field is blank.
I looked at how mine was working, and it doesn't appear to overwrite any thing (in my case with a blank) on the AD server - my ldap integration email field simply isn't being populated and thus requires me to fill it in when I go to save a user who was added automatically via ldap integration.
Comment #9
scafmac commentedOn the ldap auth configuration page in drupal, set the mail attribute to: userprincipalname
I just found a bug where, at least with an Open LDAP server, the attribute names from the server are all lowercased. The ldapauth module checks for the existence of the attribute in the ldap record before reading it - UserPrincipalName <> userprincipalname so it doesn't even try to read the mail attribute... It shouldn't matter that the cases don't match from the LDAP server's perspective - I'm 99% sure AD doesn't care about case and have found OpenLDAP doesn't appear to care either.
I'm not sure how extensive of a problem it is, but it's on my list. Let me know if changing the case helps.
Comment #10
pcorbett commentedBingo!!! Changing everything to lower case allows the email address to be read into Drupal perfectly. Now, THAT is annoying. Are you saying that because Open LDAP uses lower case that LDAP Integration looks for that and ignores anything else that isn't all lower case? Thanks for the suggestion, works like a charm.
Comment #11
pcorbett commentedHave you looked into #4 with respect to Firefox and the Garland theme for D 5.x ? See the attachment I posted to see a screen shot. Works in IE 6.x, but the right menu is still bolded.
Comment #12
emdalton commentedscafmac, we're using AD and we don't have email addresses stored in the authentication system at all, so the module can't retrieve them. I just need to make sure it doesn't wipe out addresses that get added manually to Drupal.
Comment #13
scafmac commentedpcorbet - I've noticed #4 and have assumed it is a garland bug since in every other theme I've tried, it works fine. But I'm happy to take a closer look at it, but it would be best if you open it as its own bug.
I have a fix for the case problem, I just hadn't had a chance to confirm it was a problem with AD as well - you've done that so I'll work on the fix for the next version.
emdalton - let me see if I've got it:
Does that cover it?
Comment #14
emdalton commentedYes, that covers what we experienced with 5.x-1.3. We backported to 5.x-1.2 until this can be resolved.
Comment #15
emdalton commentedI'm not sure why the issue title was changed. I still hope "Disable requiring e-mail on edit User" gets addressed someday.
Comment #16
johnbarclay commentedClosing 5.x issues to clean out issue queue.