You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My users are able to change their email address. However, since BWDC is using this field to compute new users, when a user is updating their address, a new BW user is created and an invitation is sent.
I see then that the old and the new account have both the same external identifier (which is the LDAP DN). I think that the DN should be used as unique identifier: if a user with the same DN already exists, then we change its email address.
We could also define a LDAP field (such as uid or cn) that defines the unique identifier instead of the mail address.
The text was updated successfully, but these errors were encountered:
Hi,
I am using LDAP as my organization users backend.
My users are able to change their email address. However, since BWDC is using this field to compute new users, when a user is updating their address, a new BW user is created and an invitation is sent.
I see then that the old and the new account have both the same external identifier (which is the LDAP DN). I think that the DN should be used as unique identifier: if a user with the same DN already exists, then we change its email address.
We could also define a LDAP field (such as uid or cn) that defines the unique identifier instead of the mail address.
The text was updated successfully, but these errors were encountered: