Repository navigation
Replies: 1 comment
|
This has been now implemented by preferring |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Provider factories can register as
ProviderEventListeners with theKeycloakSessionFactory, which allows them to respond to events such asRoleRemovedEventorUserRemovedEvent.In the storage layer, the logic that is currently implemented in the legacy
JPAprovider factories can't be simply copied to the new map storage factories as the former factories make assumptions about the storage structure that may not be true in the new storage configuration.Ideally the map storage factories should "translate" the provider event, that contains references to model classes, into events that are appropriate for the
MapStorages, and propagate these events into the storages that are meant to be handling the event (instead of using model classes, the factory can relay, for example, aremove-roleevent with aModelCriteriathat the storage should use to locate the role to be removed).The context in which the event was generated is important, as we can have different storages at the
realmlevel, so an event generated in the context of a specificrealmshould be handled by the corresponding map storage.This thread aims to start a design discussion for event handling by the map storage factories.
All reactions