[keycloak-user] ProviderFactory::postInit not called with hot deployment
Stian Thorgersen
sthorger at redhat.com
Wed Jun 28 01:15:44 EDT 2017
Yep, seems like a bug
On 28 June 2017 at 03:35, Dmitry Telegin <mitya at cargosoft.ru> wrote:
> Hi,
>
> Seems like o.k.provider.ProviderFactory::postInit() is called only upon
> server startup, no matter which way the provider has been deployed, as
> a module or via the deployments dir. However, if the provider is hot
> (re)deployed on the running server, the method is not called.
> (ProviderFactory::init() is called always, but it's insufficient for
> most init phase tasks since normally a KeycloakSessionFactory instance
> is required.)
>
> Indeed, o.k.services.DefaultKeycloakSessionFactory::deploy() doesn't
> contain mentions of postInit, contrary to
> DefaultKeycloakSessionFactory::init(). Seems like a bug to me, OK to
> file JIRA issue and PR?
>
> Regards,
> Dmitry
> _______________________________________________
> keycloak-user mailing list
> keycloak-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-user
>
More information about the keycloak-user
mailing list