Thanks Stian. I tested running 2.5.4 with the 3.2.0 schema and keycloak runs and works in our environment. I assume as long as I don’t request an offline token… However in light of your comments and some other issues we discovered we’re going to have to perform the migration in downtime so using the newer schema with an older release won’t happen. Matt From: Stian Thorgersen [mailto:sthorger@redhat.com] Sent: Friday, 14 July 2017 3:30 PM To: Matt Evans <mevans(a)aconex.com&gt; Cc: keycloak-user <keycloak-user(a)lists.jboss.org&gt; Subject: Re: [keycloak-user] Upgrading from 2.5.4 to 3.2.0 Are you asking if you can upgrade the DB to 3.2 and still run 2.5.4? The answer to that question is no. It simply won't work. On 14 July 2017 at 01:11, Matt Evans <mevans@aconex.com<mailto:mevans@aconex.com>> wrote: Hi We're looking to upgrade keycloak from 2.5.4 to 3.2.0, but I noticed in the liquibase changesets that one of the changes in 3.2.0 jpa changelog the column OFFLINE_CLIENT_SESSION has been deleted in the OFFLINE_CLIENT_SESSION table. My question is how will 2.5.4 handle that column missing if we update the schema first? I've tested this scenario in our environment and it seems to work, but we don't request offline tokens. Will that be enough to ensure that we won't get failures because of the missing column? Thanks Matt _______________________________________________ keycloak-user mailing list keycloak-user@lists.jboss.org<mailto:keycloak-user@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/keycloak-user