8000 Warnings when deploying my provider. DPKeycloakEventListenerProviderFactory is implementing the internal SPI eventsListener. · Issue #19118 · keycloak/keycloak · GitHub
[go: up one dir, main page]

Skip to content

Warnings when deploying my provider. DPKeycloakEventListenerProviderFactory is implementing the internal SPI eventsListener.  #19118

Closed

Description

@PavanKalyan-Gandhapudi

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

image

Activity

  1. changed the title [-]DPKeycloakEventListenerProviderFactory is implementing the internal SPI eventsListener. [/-] [+]Warnings when deploying my provider. DPKeycloakEventListenerProviderFactory is implementing the internal SPI eventsListener. [/+] on Mar 20, 2023
  2. PavanKalyan-Gandhapudi commented on Mar 21, 2023

    @PavanKalyan-Gandhapudi
    Author

    @dasniko Any comments on this ?

    We are using keycloak-server-spi-private, keycloak-server-spi dependencies.

  3. sschu commented on Mar 21, 2023

    @sschu
    Contributor

    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.

  4. PavanKalyan-Gandhapudi commented on Mar 21, 2023

    @PavanKalyan-Gandhapudi
    Author

    Hi @sschu Is there any alternate to using internal SPI event listeners ?

  5. sschu commented on Mar 21, 2023

    @sschu
    Contributor

    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.

  6. dasniko commented on Mar 21, 2023

    @dasniko
    Contributor

    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.

  7. locked and limited conversation to collaborators on Jul 30, 2025
  8. converted this issue into a discussion #41549 on Jul 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0