-
Notifications
You must be signed in to change notification settings - Fork 135
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
KC UI fails if migration API isn't running (dev mode) #75
Comments
The error log
|
I honestly haven't given much thought to the probability of the migration API not being available, as I didn't think the plugin would be used at any other time than during logging in (the Keycloak docs for the interfaces aren't the best). Just to be sure, do I understand correctly that the issue is Keycloak calling the migration API when creating a user through the Keycloak UI? Off the top of my head, it should be fairly easy to modify On the other hand, the best solution would be to make Keycloak not use The problem definitely needs some investigating. If it's urgent, feel free to take a look at the code yourself, probably starting with LegacyProvider :) |
Hi Daniel,
I have a local docker-compose KC 19.0.1 with plugin loaded, and noticed when setting up users in the KC UI that create user fails if the migration API isn't available -
Error logged is
2023-02-25 02:47:47,382 ERROR [org.keycloak.services.error.KeycloakErrorHandler] (executor-thread-13) Uncaught server error: com.danielfrak.code.keycloak.providers.rest.exceptions.RestUserProviderException: com.danielfrak.code.keycloak.providers.rest.rest.http.HttpRequestException: An error occurred while making a HTTP request: GET http://host.docker.internal:5000/api/usermigration/[email protected] HTTP/1.1
With the API running, creating a new user works ok, even if the API returns a non-200 code.
Is this behaviour by design? The concern is KC availability will be impacted, e.g. whenever the API is being deployed.
What would you advise? Thanks v much for a fantastic utility!
Ken
The text was updated successfully, but these errors were encountered: