jenskl
commented
11 years ago I had the very same problem. Took me a day to find out why I could not map the LDAP "mail" to Plone's "email" property. The fix is on the above website:
##################### Fine Tuning
We're almost there now. If things went well we should be able to log into the Plone site using the login form using an Active Directory user's login name and password. However, I noticed that after I logged in and went to the user's personal preferences page, the user's Full Name and Email Address were missing. :-(
I got a tip from Stephen Altmueller (mond21) in the #plone chat room. He said that I needed to enable the ldap Properties Plugin in the ZMI. The place to find the list of Property Plugins is here: http://localhost:8080/Plone/acl_users/plugins/PropertiesPlugins. I found that it was enabled, but it was not the first Properties Plugin in the list of enabled plugins. I moved it to the top of the list and all was well. Thanks Stephen! ######################
That is, ldap-plugin is under mutable_properties by default. Movin it up fixes the issue.
Having otherwise successfully connected a Plone 4.1.5 site to an Active Directory server, I noticed there was no mapping from LDAP (AD) attributes to Plone member properties (in fact the AD server had no email data, but there were convenient attributes to be used as fullname).
I finally found http://www.catapultsolutions.net/resources/plone-cms-talks-w-ms-active-directory.html and followed the suggestion of visiting acl_users/plugins in the ZMI and reordering active Properties Plugins. With ldap-plugins at the top, fullname was finally correctly mapped from the AD attribute I had chosen..
Even if nothing else is changed, it would thus be nice to have that tip included in the brief plone.app.ldap doc text...