redmine_ldap_sync: LDAP attributes "can't be blank" but exist in LDAP

Added by Lutz Horn over 3 years ago

I am having problems configuring the redmine_ldap_sync plugin groups are synched but users fail because the attributes "can't be blank". Example:

-- Could not create user 'a': "First name can't be blank", "Last name can't be blank", "Email can't be blank" 

The strange thing is that this user has all the normal attributes for inetOrgPerson (givenName, sn, and mail) in LDAP.

In addition, the screen to configure the "User/Group fields" doesn't allow me to set values for the LDAP attributes that belong the fields; the input elements are disabled.

The rest of the configuration:

Do I miss anything? How can I sync the users including the LDAP properties for First name, Last name, and Email?

Replies (3)

RE: redmine_ldap_sync: LDAP attributes "can't be blank" but exist in LDAP - Added by Lutz Horn over 3 years ago

I've found the solution: The LDAP attributes where not configured in the basic LDAP authentication settings. Adding them there made them available for the LDAP sync plugin.

RE: redmine_ldap_sync: LDAP attributes "can't be blank" but exist in LDAP - Added by trigal trigal about 3 years ago

but what if I want to insert a 'default value'?

RE: redmine_ldap_sync: LDAP attributes "can't be blank" but exist in LDAP - Added by Ricardo S almost 3 years ago

The firstname, lastname and email are required fields.
Without the plugin, the user would be requested to fill in those fields to proceed.

But, if you need that feature you can open a ticket at http://github.com/thorin/redmine_ldap_sync.

(1-3/3)