You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was attempting to import a realm over the top of an existing realm to apply changes that had been made.
Someone had manually created a client role of "Admin" under a client using the keycloak admin UI.
It was subsequently added to the realm file applied by config cli as "admin".
When attempting to apply the change the only error was the following in the logs: 2023-11-06 02:18:06.823 ERROR 1 --- [ main] d.a.k.config.KeycloakConfigRunner : HTTP 409 Conflict
After updating the logging level to trace I found it was because Keycloak was saying that the client role already existed.
Expected Behavior
If keycloak treats client roles as case insensitive, then the config cli should try to match case insensitive too.
The error message reported should be more useful to someone looking in the logs without having to increase the logging level.
Note that the message reported by the server wouldn't be helpful on it's own as it doesn't indicate what resource had the issue.
Steps To Reproduce
Create a realm config file that includes at least 1 client role that begins with an upper case character.
Apply the config file using the config cli.
Update the client role in the realm config file to have a lower case first character.
Apply the updated config file using the config cli.
Environment
Keycloak Version: 20.0.3
keycloak-config-cli Version: 5.6.1-20.0.5
Java Version: Whatever version is in the docker image
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Current Behavior
I was attempting to import a realm over the top of an existing realm to apply changes that had been made.
Someone had manually created a client role of "Admin" under a client using the keycloak admin UI.
It was subsequently added to the realm file applied by config cli as "admin".
When attempting to apply the change the only error was the following in the logs:
2023-11-06 02:18:06.823 ERROR 1 --- [ main] d.a.k.config.KeycloakConfigRunner : HTTP 409 Conflict
After updating the logging level to trace I found it was because Keycloak was saying that the client role already existed.
Expected Behavior
If keycloak treats client roles as case insensitive, then the config cli should try to match case insensitive too.
The error message reported should be more useful to someone looking in the logs without having to increase the logging level.
Note that the message reported by the server wouldn't be helpful on it's own as it doesn't indicate what resource had the issue.
Steps To Reproduce
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: