Download & Extend

LDAP User: Unable to set mapping fields between LDAP and drupal account.

Project:Lightweight Directory Access Protocol (LDAP)
Version:7.x-2.x-dev
Component:User interface
Category:bug report
Priority:normal
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

Hi, After setting an AD fully functional server I'm unable to mapp fields between LDAP and drupal accounts. If I select an LDAP attribute and a user field once I save this record is not commited to DB. Has anyone experienced this?

All other configuration works perfect. User roles/og groups login....

Thanks

Comments

#1

Title:Unable to set mapping fields between LDAP and drupal account.» LDAP User: Unable to set mapping fields between LDAP and drupal account.

The configuration might work in general, but the 7.x-2.x version is pretty unstable. It should be ready for another round of testing in 3 or 4 days.

#2

Status:active» postponed

7.x-2.x is unstable now. Keep an eye on #1115704: Version and Releases Status Updates for when its ready for testing and then please test this again.

#3

Hi guys, great work with last dev version ready for test. I finally found why this was not working, I think there is a bug on server name and user mappings.
if server name is: server.name
On the form rendered id for table fields are rendered without dots ie : %_server_name_% while we are expecting to have this values as %_server.name_%

in form_state you can see this difference. in form[input] the mappings are pressent while in form[values] are null. Sorry for lack of info, in some days I will have a test env to try to reproduce this.

Regards

#4

The current 7.x-2.x-dev version should have a functional ldap user admin form at admin/config/people/ldap/user. The form itself is ready for testing and feedback.

I'm working through the test coverage and missing features of LDAP User (binary fields, puid implementation, etc); after that the functionality of LDAP User will be ready for testing.

#5

Category:support request» bug report
Status:postponed» fixed

#6

Status:fixed» closed (fixed)

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