Hi! We have a need to publish Keycloak events to external systems, for example when user updates her profile. I was thinking of publishing messages to a JMS topic by implementing an event listener. What do you think, would you be interested in such a pull request? I think the topic should be preconfigured in Keycloak/Wildfly, but the admin would enable the functionality by adding "jms" to event listeners in the admin console. Best regards, Thomas _______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-dev

Hi Thomas, would be great to have that! Cheers, Thomas 2016-01-12 18:37 GMT+01:00 Thomas Raehalme < thomas.raehalme(a)aitiofinland.com&gt;: > Hi! > > We have a need to publish Keycloak events to external systems, for > example when user updates her profile. I was thinking of publishing > messages to a JMS topic by implementing an event listener. > > What do you think, would you be interested in such a pull request? I > think the topic should be preconfigured in Keycloak/Wildfly, but the admin > would enable the functionality by adding "jms" to event listeners in the > admin console. > > Best regards, > Thomas > > _______________________________________________ > keycloak-dev mailing list > keycloak-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/keycloak-dev >

wrote:

I have something like this implemented already. It listens to KC events and publishes those to a REST endpoint (if the target server is remote), or to a JMS topic.

Hello Thomas, would you mind sharing your keycloak configuration with a JMS resource-adapter? Did you manage to configure a new resource-adapter via jboss-cli? Cheers, Thomas 2016-01-13 14:31 GMT+01:00 Thomas Raehalme < thomas.raehalme(a)aitiofinland.com&gt;: > > On Wed, Jan 13, 2016 at 3:25 PM, Juraci Paixão Kröhling < > juraci(a)kroehling.de&gt; wrote: > >> I have something like this implemented already. It listens to KC events >> and publishes those to a REST endpoint (if the target server is remote), >> or to a JMS topic. >> > > That's great, thanks for the info! I also have the JMS implementation > ready, but the necessary Wildfly configuration still needs to be thought > through... > > Best regards, > Thomas > > _______________________________________________ > keycloak-dev mailing list > keycloak-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/keycloak-dev >

wrote:

wrote:

It would probably be a good idea although I think this JMS publishing is such a basic feature that it should be part of the core package. If you have a chance to help me get started with the Arquillian part, I'm happy to send the PR. I should have time to work on this again within the next week or so. Best regards, Thomas On Mon, Apr 4, 2016 at 12:26 PM, Stian Thorgersen <sthorger(a)redhat.com&gt; wrote: > I wonder if we should have a Keycloak extensions repository where we > could place things like this rather than adding directly to master. > > On 31 March 2016 at 20:18, Thomas Raehalme < > thomas.raehalme(a)aitiofinland.com&gt; wrote: > >> Hi, >> >> On Thu, Mar 31, 2016 at 4:38 PM, Thomas Darimont < >> thomas.darimont(a)googlemail.com&gt; wrote: >> >>> would you mind sharing your keycloak configuration with a JMS >>> resource-adapter? >>> >> >> Here are the changes I made to standalone/configuration/standalone.xml: >> >> 1. Added the following extension under /server/extensions: >> >> <extension module="org.wildfly.extension.messaging-activemq"/> >> >> 2. Added the following subsystem under /server/profile: >> >> <subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0"> >> <server name="default"> >> <security enabled="false" /> <!-- I didn't need to use security >> as everything was localhost --> >> <remote-acceptor name="netty" socket-binding="messaging"/> >> <remote-connector name="netty" socket-binding="messaging"/> >> <in-vm-acceptor name="in-vm" server-id="0"/> >> <in-vm-connector name="in-vm" server-id="0"/> >> <pooled-connection-factory name="activemq-ra" >> transaction="xa" connectors="in-vm" >> entries="java:/ConnectionFactory java:/JmsXA >> java:jboss/DefaultJMSConnectionFactory"/> >> <jms-topic name="KeycloakEvents" entries="jms/KeycloakEvents >> java:jboss/exported/jms/KeycloakEvents" /> >> </server> >> </subsystem> >> >> 3. Added the following socket-binding under /server/socket-binding-group: >> >> <socket-binding name="messaging" port="61616"/> >> >> This enabled my external process to listen to the JMS topic. >> >> I attached a full example to this message. The changes have been marked >> with <!-- keycloak-events-jms -->. >> >> Did you manage to configure a new resource-adapter via jboss-cli? >>> >> >> No, I haven't used jboss-cli but modified the configuration file >> directly. >> >> My implementation of KEYCLOAK-2302 can be found at Github: >> https://github.com/raehalme/keycloak/tree/KEYCLOAK-2302. >> >> I have not sent a PR as I have yet to complete the Arquillian >> integration tests requested by Stian. Other work has kept me busy and I >> haven't had a chance to even rebase against 1.9.x. >> >> Best regards, >> Thomas >> >> >> _______________________________________________ >> keycloak-dev mailing list >> keycloak-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/keycloak-dev >> > >

On Wed, Apr 6, 2016 at 12:47 PM, Stian Thorgersen <sthorger(a)redhat.com&gt; wrote: > Problem with a built-in JMS event listener provider is that it should > send messages to an external JMS server. Keycloak itself should not act as > a JMS server. Further, there's no standard way to connect to JMS providers, > so best we could do is one that connects to WildFly/EAP and make it easy > for users to extend it to connect to different providers (maybe an > getDestination() method). > I understand that the configuration cannot (and should not) be enabled by default, but it would be great if it was enough for the user to just modify the Wildfly/Keycloak configuration instead of having to add modules, jars and whatever to the installation. Examples of the configuration can be provided separately.

At the moment I've got no spare time to help out in detail with Arquillian > part, although I can answer questions over email if that's enough. For the > Arquillian part I'd suggest starting an embedded Archimedes server in the > test. > That'll do just fine, thanks! I'll get in touch as soon as I have time to work on this (and encounter a problem). Best regards, Thomas