You could do something like the following before deleting the adapter files
to uninstall all the components from Wildfly so that you can run
adapter-install-offline.cli script after installing the new version:
embed-server --server-config=standalone.xml
/subsystem=keycloak:remove
/extension=org.keycloak.keycloak-adapter-subsystem/:remove
/subsystem=security/security-domain=keycloak/authentication=classic/:remove
/subsystem=security/security-domain=keycloak/:remove
On Mon, Mar 13, 2017 at 4:34 PM, Marko Strukelj <mstrukel(a)redhat.com> wrote:
That's a good point. Our install mechanism for adapters is to
simply unzip
an archive.
If you want to upgrade the cleanest way would be to completely delete the
old adapter, and install the new one.
We don't have a mechanism to delete files so you're on your own here.
On Linux and MacOS you could do:
cd WILDFLY_HOME
jar tf ~/Downloads/keycloak-wildfly-adapter-dist-PREVIOUS_VERSION.zip |
xargs -I {} rm {}
unzip ~/Downloads/keycloak-wildfly-adapter-dist-NEW_VERSION.zip
Neither do we have a script for uninstalling the components from Wildfly.
You could do something
On Mon, Mar 13, 2017 at 2:18 PM, ko lo <sanchoponchos(a)gmail.com> wrote:
> I have applications including those not deployed directly to the Keycloak
> server. I want to upgrade the adapter.
> I have to do similar steps to the standalone server? New WF installation
> add new KC adapter, copy standalone.xml, themes, etc. over., etc..
> _______________________________________________
> keycloak-user mailing list
> keycloak-user(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-user
>