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

Replace event processing with invalidation handling #11842

Open
vramik opened this issue May 5, 2022 · 2 comments
Open

Replace event processing with invalidation handling #11842

vramik opened this issue May 5, 2022 · 2 comments
Labels
area/storage Indicates an issue that touches storage (change in data layout or data manipulation) kind/enhancement Categorizes a PR related to an enhancement team/core-shared

Comments

@vramik
Copy link
Contributor

vramik commented May 5, 2022

After #11076 and #11213 are done, we might be able to get rid of publishing events like here https://github.com/keycloak/keycloak/pull/11077/files#diff-ef696ace083c81d5951f520c68ef20a4ab428357e54b1139d863da2e78af6c9fR63-R66.

The remaining places what uses events seems to be Synchronizers: https://github.com/keycloak/keycloak/tree/main/server-spi-private/src/main/java/org/keycloak/authorization/store/syncronization

@vramik vramik added kind/enhancement Categorizes a PR related to an enhancement area/storage Indicates an issue that touches storage (change in data layout or data manipulation) team/storage-sig labels May 5, 2022
@vramik
Copy link
Contributor Author

vramik commented May 8, 2022

another place where events are used is ClientScopePolicyProviderFactory

@ahus1
Copy link
Contributor

ahus1 commented Nov 9, 2023

Re-evaluate if this is relevant for the legacy store as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/storage Indicates an issue that touches storage (change in data layout or data manipulation) kind/enhancement Categorizes a PR related to an enhancement team/core-shared
Projects
Status: 📤 Todo
Development

No branches or pull requests

3 participants