That is what I hoped. Thanks a lot, Dmitry.
On Tue, Jul 31, 2018 at 2:54 AM, Dmitry Telegin <dt(a)acutus.pro> wrote:
Normally you shouldn't do anything else, unless you manage Keycloak
configuration yourself, i.e. $KEYCLOAK/standalone/configuration is a
In this case you might need to migrate your configuration. There are
helpful scripts in $KEYCLOAK/bin/migrate*.cli to facilitate that.
If you deploy custom providers (extensions), especially if using
frequently changing private SPIs, you'll also make sure the code compiles
with the new version of Keycloak.
CTO, Acutus s.r.o.
Keycloak Consulting and Training
Pod lipami street 339/52, 130 00 Prague 3, Czech Republic
+42 (022) 888-30-71
On Mon, 2018-07-30 at 10:02 +0200, Erlend Hamnaberg wrote:
> Hello all.
> I was wondering if it required to run the upgrade steps (apart from the
> database migrations and themes ) when deploying keycloak in dockerized
> I am of course extending
> FROM jboss/keycloak:4.1.0.Final
> I started the server with just upgrading the database automatically, and
> seems to work fine.
> Am I missing something other important step?
> keycloak-user mailing list