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
Warning about global state on start #27718
Comments
@tristantarrant can you weigh in on if there is any benefit for keycloak to configure a global state, or if we should look to omit this warning in some way? |
Are you enabling authorization ? |
@tristantarrant No. We by default provide configuration for infinispan in local and clustered mode https://github.com/keycloak/keycloak/tree/main/quarkus/runtime/src/main/resources - neither have explicit configuration for authorization. |
@tristantarrant can you confirm that if we aren't using authorization, then this warning isn't meaningful? If that's the case, should there be an upstream change to detect this and lessen the warning, or should we look to do log filtering on the keycloak side? |
Thank you @tristantarrant We'll close this issue when we pick up that fix. |
Resolved by #29069 |
On a simple start or start-dev the logs will show:
Neither of our built-in cache configs have global-state defined, but the ClusterPermissionMapper and the ClusterRoleMapper create internal caches that expect persistence. For dev mode there doesn't seem to be a great way to ignore this, and it doesn't like we should be configuing a global-store in that case. @mhajas @mabartos @vmuzikar is there any benefit to users configuring a global-state when not in dev mode? If not, then it seems like we'd want the upstream to switch this to a debug message instead.
Originally posted by @shawkins in #27308 (comment)
The text was updated successfully, but these errors were encountered: