Hello Keycloakers,
We are currently running into an issue when upgrading Keycloak from 3.2.0
to 4.5.0 directly. The issue appears to be related to the database
migration specifically and from a change introduced in August 2018 which
references a previously dropped column.
Here is the Jira issue containing some more details with the error and some
more analysis:
https://issues.jboss.org/browse/KEYCLOAK-8702
Is there anything we can do to help expedite the resolution of this issue
aside from the details we have provided on the ticket?
Best regards,
Mandy
--
*Mandy Fung **|* Software Engineer 1 *| *Tasktop
*email: *mandy.fung(a)tasktop.com