[keycloak-dev] Publishing events to JMS topic

[Thomas Raehalme]

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 at redhat.com>
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 at aitiofinland.com> wrote:
>
>> Hi,
>>
>> On Thu, Mar 31, 2016 at 4:38 PM, Thomas Darimont <
>> thomas.darimont at googlemail.com> 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 at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/keycloak-dev/attachments/20160404/6f6057e8/attachment-0001.html