Displayname missing from LDIF template placeholders

[awesome-manuel]

Would it be possible to also have a {displayname} placeholder that gets filled during user creation?

[blizzz]

Not without server/provisioning API changes, as backends do get the userid and a password only for the initial user generation. The user has to exist after this point.

The displayname is provided to the backends somewhat later, so it can be set only later. Delaying the creation is unreliable (would rely on memcache) and can lead ot undefined behaviour (when the LDAP record cannot be written).

[c-nv-s]

Not without server/provisioning API changes, as backends do get the userid and a password only for the initial user generation. The user has to exist after this point.

The displayname is provided to the backends somewhat later, so it can be set only later. Delaying the creation is unreliable (would rely on memcache) and can lead ot undefined behaviour (when the LDAP record cannot be written).

Would this also be the case if there was a {mail} placeholder for the LDIF template too? I've been searching the records created on openldap and it looks like emails aren't populated on user creation, even when the option 'an LDAP user must have an email set' is selected.

[blizzz]

Would this also be the case if there was a {mail} placeholder for the LDIF template too?

Yes, as said:

as backends do get the userid and a password only for the initial user generation.

[ThyMYthOS]

Could you point us to the hooks that get called on user creation and on update of displayname and mail?

[blizzz]

This is being triggered https://github.com/nextcloud/server/blob/master/apps/provisioning_api/lib/Controller/UsersController.php#L241

[Spacelord09]

Hey! I`m also missing a few placeholders like mail and first / last name. Any updates to this problem?