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

Check for duplicated usernames and emails when Login with email option is enabled #27297

Closed
1 of 2 tasks
rmartinc opened this issue Feb 26, 2024 · 0 comments · Fixed by #27408
Closed
1 of 2 tasks

Check for duplicated usernames and emails when Login with email option is enabled #27297

rmartinc opened this issue Feb 26, 2024 · 0 comments · Fixed by #27408
Assignees
Labels
area/user-profile kind/bug Categorizes a PR related to a bug priority/important Must be worked on very soon release/24.0.0 team/core-iam

Comments

@rmartinc
Copy link
Contributor

Before reporting an issue

  • I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.

Area

user-profile

Describe the bug

Currently the user profile validators check for duplicated username and duplicated emails. But when the option Login with email is enabled (it's enabled by default) it can happen that the username (if it has an email format) collides with another user email. The duplicated username and duplicated email validators should also check for the other field when that option is enabled to avoid duplicates between them.

Version

23.0.7

Regression

  • The issue is a regression

Expected behavior

  • The validators should check the other field and throw an error because it's duplicated.

Actual behavior

  • The validators allow a user to have the same username than another email user and vice-versa.

How to Reproduce?

  • In a realm with login with email enabled.
  • Create a user with username username1@local.com and email username1@local.org.
  • Create a second user with username username2 and email username1@local.com (like the first username).

Anything else?

No response

@rmartinc rmartinc added kind/bug Categorizes a PR related to a bug team/core-iam labels Feb 26, 2024
@rmartinc rmartinc self-assigned this Feb 26, 2024
@pedroigor pedroigor added the priority/important Must be worked on very soon label Feb 26, 2024
rmartinc added a commit to rmartinc/keycloak that referenced this issue Feb 29, 2024
Closes keycloak#27297

Signed-off-by: rmartinc <rmartinc@redhat.com>
rmartinc added a commit to rmartinc/keycloak that referenced this issue Feb 29, 2024
Closes keycloak#27297

Signed-off-by: rmartinc <rmartinc@redhat.com>
rmartinc added a commit to rmartinc/keycloak that referenced this issue Feb 29, 2024
Closes keycloak#27297

Signed-off-by: rmartinc <rmartinc@redhat.com>
pedroigor pushed a commit that referenced this issue Mar 1, 2024
Closes #27297

Signed-off-by: rmartinc <rmartinc@redhat.com>
ahus1 pushed a commit to ahus1/keycloak that referenced this issue Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/user-profile kind/bug Categorizes a PR related to a bug priority/important Must be worked on very soon release/24.0.0 team/core-iam
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants