Repository navigation
Warnings when deploying my provider. DPKeycloakEventListenerProviderFactory is implementing the internal SPI eventsListener. #41549
Replies: 5 comments
|
@dasniko Any comments on this ? We are using keycloak-server-spi-private, keycloak-server-spi dependencies. |
|
This is just a warning and it means exactly what it says. The interface you are implementing is not public so not guaranteed to be stable. Your SPI might not work with future Keycloak versions and you will have to adapt it. |
|
Hi @sschu Is there any alternate to using internal SPI event listeners ? |
|
You can store all events in the database and then poll for events via API. But that might be a lot of event and needs an extra component outside of Keycloak. So implementing a custom listener is probably the natural way to go. |
|
Like @sschu wrote, it's just a warning that you are aware of this. It's not forbidden to use these private interfaces. They are here to be used and implemented. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Description
Currently we are using wildfly keycloak, as a part of this we have SPI Events listener is there. But now we are moving wildfly keycloak to quarkus keycloak. Here when i deploy keycloak-event-listener jar file and build it (using kc.bat build command). I was getting this error - 2023-03-09 04:02:37,148 WARN [org.keycloak.services] (build-37) KC-SERVICES0047: dp-keycloak-event-listener (com.mf.dp.cell.event.DPKeycloakEventListenerProviderFactory) is implementing the internal SPI eventsListener. This SPI is internal and may change without notice
After execute kc.bat build command
All reactions