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
The legacy and dynamic user profile should be decoupled in order to avoid one impacting the other when managing user attributes.
In the 22 release, this coupling is causing:
Username and e-mail fields are not properly managed depending on how the registration as username and edit username settings are set to a realm (using the different combinations of both)
E-mail not properly managed and shown in UI when the update email feature is enabled
Admin UI not properly rendering attributes when the user profile is enabled
Admin API failing to update username/email depending on how the registration as username and edit username settings are set to a realm
Version
22
Expected behavior
Username and email are properly managed depending on how the registration as username and edit username settings are set to a realm.
Changes to legacy should not directly affect the dynamic user profile behavior, and vice-versa.
Actual behavior
Username and email are not properly managed depending on how the registration as username and edit username settings are set to a realm.
Changes to legacy is affected by the dynamic user profile behavior, and vice-versa.
How to Reproduce?
N/A
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Before reporting an issue
Area
user-profile
Describe the bug
The legacy and dynamic user profile should be decoupled in order to avoid one impacting the other when managing user attributes.
In the 22 release, this coupling is causing:
Version
22
Expected behavior
Username and email are properly managed depending on how the registration as username and edit username settings are set to a realm.
Changes to legacy should not directly affect the dynamic user profile behavior, and vice-versa.
Actual behavior
Username and email are not properly managed depending on how the registration as username and edit username settings are set to a realm.
Changes to legacy is affected by the dynamic user profile behavior, and vice-versa.
How to Reproduce?
N/A
Anything else?
No response
The text was updated successfully, but these errors were encountered: