Misleading user tokens column in sync to Drupal

experiencing the same problem here..!!

Temp solution..

edit file LdapUserConfAdmin.class.php in ldap_user Directory

search line "$id = $id_prefix . 'sm__user_tokens__' . $row;"

and disable the if loop which is just above the searched line..

don't know why its been made one side!?.

subscribe, where is the token key column?

Please help me with this, is there a manual or something?

I use the profile2 module and want to fill my fields with ldap data but my fields are not in the list. Creating a token is not possible because of the missing column. Am i missing something?

Thanks
Nielsvoo

Still need some help here, someone?

Thanks

Sometimes this forum is really fast with answering questions, but this question although it is for me an important one simply won't get any answer. :-(

Does anyone have an answer to this issue?

Same problem here. Anyone?

Thanks in advance

Still need an answer!, please

I'm trying to get this working, but don't have any luck with #3. Am I missing something?

To clarify my previous comment. When remove the if statement I get the box to appear where I can enter a user token. However, I have no luck with any data being imported. Also, I'm limited to adding one user token field, new ones are simply overwritten.

Example
[givenName] ---> [field.field_first_name]

Is that the correct format? I have field_first_name in my Profiles2 form, but nothing appears when I login even with both sync boxes checked in the ldap user page.

All I want to do is to sync First and Last Name to Drupal from ldap, I was hoping this wasn't going to be this complicated.

Can anyone help with this issue please ?

Having the same issue here

need help on this issue please

Still a problem -- is there a trick to enable the non-existent tokens column?

#3 does expose the "Convert From Binary" column when -- user tokens -- is selected under Target Drupal Attribute and saving changes does indeed save the token (I used [field.field_phone_number] as an example) but doing so accomplishes nothing in that when a user signs on the field doesn't get populated with LDAP data.

I'm still seeing this issue on the latest dev version.

Is there something we're missing here, as I can't imagine this has been broken for 30+months now since first being reported?

Or is it as simple as the module isn't even attempting to perform LDAP > Drupal functionality, and the fact that there is the "- user tokens -" entry is the actual bug?

Needs review is for patches, this issue is still active as far as I can see.

This issue still exists!, why cannot someone commit this.?

#20 a patch to review might eventually get committed. So far nobody has provided one.

I believe Yerwol is correct in speculating that the "- user tokens -" entry is a bug and I had removed it in 8.x. Since the defect is the current state of the 7.x-2.x branch without an indication for a proper fix, and it's confusing users, I've removed that line.

See https://www.drupal.org/node/2211079 if you are interested in full Token support.