<div dir="ltr">We don't currently support live deploying of providers and the Keycloak server has to be restarted for updates as well as new providers to be picked up. <div><br></div><div>The 'reload' command only results in manual changes to standalone.xml to be reloaded and doesn't have any affect on modules or Keycloak itself. You can use 'shutdown(restart=true)' which will restart the server. I'm afraid you will use active sessions unless you have multiple nodes and increase owners for the userSession cache.<br></div><div><br></div><div>Feel free to create a JIRA to support deploying/repdeploying providers live, but it would most likely be a while until we can get around to it. Unless we get a community contribution around it that is.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 17 June 2016 at 16:41, Mitya <span dir="ltr"><<a href="mailto:mitya@cargosoft.ru" target="_blank">mitya@cargosoft.ru</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>Hi,</div><div><br></div><div>I'm developing a KeyCloak extension which is packaged as two JBoss modules:</div><div>- the extension proper (custom authenticator + custom realm resource + custom admin theme);</div><div>- modified org.keycloak.keycloak-model-jpa (since Entity SPI is not yet available).</div><div><br></div><div>Each time I make changes, I have to go through a roundabout of stopping KeyCloak, deploying modules and starting KeyCloak again. This can happen as many as several dozen times a day; as soon as I roll a CI infrastructure, the build server will have to do the same. Needless to say, the process is pretty time-consuming; additionally, I'll have to grant permissions to the build server to restart a system service (KeyCloak is deployed as systemd unit). I've tried the following in jboss-cli:</div><div><br></div><div>[disconnected /] connect</div><div>[<a href="mailto:standalone@localhost" target="_blank">standalone@localhost</a>:9990 /] module remove --name=foo.bar.main</div><div>[<a href="mailto:standalone@localhost" target="_blank">standalone@localhost</a>:9990 /] module add --name=foo.bar.main --resources=... --dependencies=...</div><div>[<a href="mailto:standalone@localhost" target="_blank">standalone@localhost</a>:9990 /] reload</div><div><br></div><div>This doesn't help, despite WildFly reports to have redeployed and restarted KeyCloak. The updated modules are simply not picked up.</div><div><br></div><div>Am I missing something? KeyCloak developers, what would you recommend to speed-up the workflow?</div><div><br></div><div>Cheers,</div><div>Mitya</div><div><br></div></div><br>_______________________________________________<br>
keycloak-dev mailing list<br>
<a href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br></blockquote></div><br></div>