History

Thomas Darimont 586f6eeece KEYCLOAK-3142 - Capture ResourceType that triggers an AdminEvent Introduced new ResourceType enum for AdminEvents which lists the current supported ResourceTypes for which AdminEvents can be fired. Previously it was difficult for custom EventListeners to figure out which ResourceType triggered an AdminEvent in order to handle it appropriately, effectively forcing users to parse the representation. Having dedicated resource types as a marker on an AdminEvent helps to ease custom EventListener code. We now also allow filtering of admin events by ResourceType in the admin-console. Signed-off-by: Thomas Darimont <thomas.darimont@gmail.com>		2016-08-04 11:30:02 +02:00
..
src/main	KEYCLOAK-3142 - Capture ResourceType that triggers an AdminEvent	2016-08-04 11:30:02 +02:00
pom.xml	bump version	2016-06-30 17:17:53 -04:00
README.md	KEYCLOAK-2752	2016-04-06 13:18:23 +02:00

README.md

Example Event Store that stores events in memory

To deploy copy target/event-store-mem-example.jar to providers directory. Alternatively you can deploy as a module by running:

KEYCLOAK_HOME/bin/jboss-cli.sh --command="module add --name=org.keycloak.examples.event-inmem --resources=target/event-store-mem-example.jar --dependencies=org.keycloak.keycloak-core,org.keycloak.keycloak-server-spi"

Then registering the provider by editing keycloak-server.json and adding the module to the providers field:

"providers": [
    ....
    "module:org.keycloak.examples.event-inmem"
],

Then edit standalone/configuration/keycloak-server.json, change:

"eventsStore": { "provider": "jpa" }

to:

"eventsStore": { "provider": "in-mem" }

Then start (or restart)the server. Once started open the admin console, select your realm, then click on Events, followed by config. Set the toggle for Enabled to ON. After this try to logout and login again then open the Events tab again in the admin console to view events from the in-mem provider.