Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decoupling legacy and dynamic user profiles and exposing metadata from admin api #22532

Closed
2 tasks done
pedroigor opened this issue Aug 17, 2023 · 0 comments · Fixed by #22533
Closed
2 tasks done

Decoupling legacy and dynamic user profiles and exposing metadata from admin api #22532

pedroigor opened this issue Aug 17, 2023 · 0 comments · Fixed by #22533
Assignees
Milestone

Comments

@pedroigor
Copy link
Contributor

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:

  • 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

@pedroigor pedroigor added kind/bug Categorizes a PR related to a bug status/triage labels Aug 17, 2023
@pedroigor pedroigor self-assigned this Aug 17, 2023
@pedroigor pedroigor removed the kind/bug Categorizes a PR related to a bug label Aug 17, 2023
@pedroigor pedroigor added this to the 22.0.2 milestone Aug 17, 2023
pedroigor added a commit to pedroigor/keycloak that referenced this issue Aug 17, 2023
…m admin api

Closes keycloak#22532

Co-authored-by: Erik Jan de Wit <erikjan.dewit@gmail.com>
pedroigor added a commit that referenced this issue Aug 29, 2023
…m admin api

Closes #22532

Co-authored-by: Erik Jan de Wit <erikjan.dewit@gmail.com>
@ghost ghost removed the status/triage label Aug 29, 2023
stianst pushed a commit to pedroigor/keycloak that referenced this issue Sep 6, 2023
…m admin api

    Closes keycloak#22532

    Co-authored-by: Erik Jan de Wit <erikjan.dewit@gmail.com>
ahus1 pushed a commit that referenced this issue Sep 7, 2023
…m admin api

    Closes #22532

    Co-authored-by: Erik Jan de Wit <erikjan.dewit@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant