Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
I've added some extra fields to my user accounts which i've also added to the list of fields to be synchronized on Drupal user creation.
I have the exact setup in 7.x, and accounts will properly get data in the custom fields on creation. However, with 8.x, all of my custom fields remain empty.
For what it's worth, selecting the "On Sync to Drupal User" option and doing another login seems to fill in the fields.
Comments
Comment #2
grahlThanks for the input.
Just for clarification: I assume if you log in as the user and the account gets provisioned it works but if you as an admin create the user it does not? Or in either case?
Comment #3
bricas CreditAttribution: bricas commentedI'll have to try it to confirm.
As mentioned in another ticket, I'd prefer if people couldn't create their own users :)
But I'll verify if there's a difference ASAP.
Comment #4
bricas CreditAttribution: bricas commentedgrahl, you are correct that when a user does a log in (for an account that hadn't already existed), the account is properly provisioned.
Comment #5
grahlComment #7
grahlPlease retest, the fix corrects the ldap association functions but there could be subtle defects depending on the conflict resolution (have only tested clean creation now). The commit adds the provisioning event to the call, fixes the association to LDAP (broken before and opportunistically applied due to the username on next sign-in, if so configured).
This will likely resolve other errors we saw for 'Invalid selection passed to syncToDrupalAccount.'