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

Keycloak username modification is not synced by sormas #13080

Closed
richardbartha opened this issue Apr 22, 2024 · 1 comment · Fixed by #13149
Closed

Keycloak username modification is not synced by sormas #13080

richardbartha opened this issue Apr 22, 2024 · 1 comment · Fixed by #13149
Assignees
Labels
bug An error or misbehavior of an existing feature (ticket type) qa-verified Issue has been tested and verified by QA

Comments

@richardbartha
Copy link
Contributor

Bug Description

For feature 13033 when we modify a username in keyclock and use sync in sormas the users is not modified but disabled and a new one gets created.

Reproduction Steps

1.Create a user in keycloak
2.Sync users from sormas
3.User from keycloak is transfered to sormas
4.Modify username in keycloak
5.Sync users again in sormas
6.User with old username is disabled and new user is created with the modified username
...

Expected Behavior

Username modification should be synced for sormas user

Affected Area(s)

Web app

SORMAS Version

1.96.0

Android version/Browser

Chrome

User Role(s)

Admin

Server URL

localhost

Additional Information

No response

@richardbartha richardbartha added the bug An error or misbehavior of an existing feature (ticket type) label Apr 22, 2024
@cazacmarin cazacmarin self-assigned this Sep 22, 2024
leventegal-she added a commit that referenced this issue Oct 7, 2024
…name-modification-is-not-synced-by-sormas

#13080 keycloak username modification is not synced by sormas
@richardbartha
Copy link
Contributor Author

@richardbartha richardbartha added the qa-verified Issue has been tested and verified by QA label Oct 9, 2024
@markusmann-vg markusmann-vg added this to the Sprint 2 - 1.99.0 milestone Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An error or misbehavior of an existing feature (ticket type) qa-verified Issue has been tested and verified by QA
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants