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
When programmatically creating a user via IUserManager.AddUser, the EmailConfirmed property can be set to True on the User object, and this is transferred to the identity user object (such that the user can log in without going through a manual email verification).
Given this, the expectation is that updating a user programmatically via IUserManager.UpdateUser, the EmailConfirmed property on the User object can be set to True/False, and again this will be transferred to the identity user object.
Having this ability (to set/clear the EmailConfirmed property) is useful for when creating a custom login module (see 4220) where the external authentication provider controls most of the auth checks on the user.
Expected Behavior
As with IUserManager.AddUser, IUserManager.UpdateUser should transfer EmailConfirmed property changes to the identity user.
Anything else?
I know there are ways to accomplish the same result using other methods. This is just a question of expectations and consistency - if AddUser allows control over the EmailConfirmed property, then why doesn't UpdateUser ?
The text was updated successfully, but these errors were encountered:
lanthonyneville
changed the title
[BUG] IUserManager.UpdateUser method does not set EmailConfirmed (and other properties) on identity user from same on User object (but IUserManager.AddUser method does)
[BUG] IUserManager.UpdateUser method does not set Email & EmailConfirmed on identity user from same on User object (but IUserManager.AddUser method does)
May 11, 2024
lanthonyneville
changed the title
[BUG] IUserManager.UpdateUser method does not set Email & EmailConfirmed on identity user from same on User object (but IUserManager.AddUser method does)
[BUG] IUserManager.UpdateUser method does not set EmailConfirmed on identity user from same on User object (but IUserManager.AddUser method does)
May 11, 2024
lanthonyneville
changed the title
[BUG] IUserManager.UpdateUser method does not set EmailConfirmed on identity user from same on User object (but IUserManager.AddUser method does)
[ENH] Allow IUserManager.UpdateUser method to set EmailConfirmed on identity user from same on User object (as IUserManager.AddUser method does)
May 11, 2024
Oqtane Info
Version - 5.1.1
Render Mode - N/A
Interactivity - N/A
Database - N/A
Describe the bug
When programmatically creating a user via IUserManager.AddUser, the EmailConfirmed property can be set to True on the User object, and this is transferred to the identity user object (such that the user can log in without going through a manual email verification).
Given this, the expectation is that updating a user programmatically via IUserManager.UpdateUser, the EmailConfirmed property on the User object can be set to True/False, and again this will be transferred to the identity user object.
Having this ability (to set/clear the EmailConfirmed property) is useful for when creating a custom login module (see 4220) where the external authentication provider controls most of the auth checks on the user.
Expected Behavior
As with IUserManager.AddUser, IUserManager.UpdateUser should transfer EmailConfirmed property changes to the identity user.
Anything else?
I know there are ways to accomplish the same result using other methods. This is just a question of expectations and consistency - if AddUser allows control over the EmailConfirmed property, then why doesn't UpdateUser ?
The text was updated successfully, but these errors were encountered: