Hi Stian,
so rather than do it "old school" as the manual says, I was told to use
<spi name="eventsListener">
<provider name="mqtt" enabled="true">
<properties>
<property name="serverUri"
value="tcp://127.0.0.1:1883"/>
<property name="username" value="mqtt_user"/>
<property name="password" value="mqtt_password"/>
<property name="topic" value="my_topic"/>
</properties>
</provider>
</spi>
with the jar copied to standalone/deployments.
This does not cause keycloak to crash on startup. It does cause errors but I think that is
a jar problem.
Regards,
John
------ Original Message ------
From: "Stian Thorgersen"
<sthorger@redhat.com<mailto:sthorger@redhat.com>>
Sent: 07/10/2019 08:46:26
Subject: Re: Re[2]: [keycloak-user] Custom SPI does not appear in list
module deployment like you've done is what I referred to by the old school deployment
approach. So what you're doing looks about right.
Do you only get the NPE below when you include your module? Is your standalone.xml in sync
with the latest release or perhaps it's missing something?