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 silently ignores partial defined user #51

Open
kostobog opened this issue Dec 8, 2023 · 3 comments
Open

Keycloak silently ignores partial defined user #51

kostobog opened this issue Dec 8, 2023 · 3 comments

Comments

@kostobog
Copy link
Collaborator

kostobog commented Dec 8, 2023

When we underspecify the user in keycloak administration ui, i.e. the user has not specified first name, last name and email address, the user is successfully saved in internal keycloak database. However, it is not saved in graphdb server.

Thus we are not able to login in record manager and we have no way to find out why.
There is no warning message in keycloak administration ui and no warning log in keycloak server.
And since the user is not saved in graphdb there is also not any unusual error in record manager server.

Note that within keycloak administration ui the first name, last name and email address are optional fields, see screenshot below.

Image

The best solution for this issue would be to show error message in keycloak administration ui when saving user without those fields.

@kostobog
Copy link
Collaborator Author

kostobog commented Dec 8, 2023

@ledsoft

@ledsoft
Copy link

ledsoft commented Dec 9, 2023

Currently, the user data replicator SPI is just an event listener, it has no influence on the user creation process. This would require either rewriting the SPI, changing Keycloak user profile theme to require first name and last name or modifying the target application to not require these fields. It depends on how critical this issue is and which solution would be the most efficient to implement.

@ledsoft
Copy link

ledsoft commented Dec 11, 2023

FYI, updated the user data replicator to handle missing first name and last name so that the user account metadata that are available (username) are replicated in the repository.
General handling of optional first name and last name should be iMHO done by the application (do not require them as well) or by Keycloak (require them).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants