We don't support downgrade.
In other words, when you do this:
- Run keycloak on 3.1.0
- Stop keycloak 3.1.0 and run keycloak 3.2.0 against same database. At
this point, your DB (both schema and data) are migrated to version 3.2.0
- At this point, it's not supported to run Keycloak 3.1.0 (or any other
older version) against same DB, which was already migrated to 3.2.0. If
you do this, the behaviour is completely unexpected.
See our migration guide for more details.
Marek
On 19/07/17 08:39, Sarp Kaya wrote:
Hello,
If we left the password encryptor default, upon upgrading from 3.1.0 to 3.2.0 and then
followed by a downgrade to 3.1.0 causes login screen to give “Invalid username or
password” issue.
I am guessing this is due to default encryptor being changed in V3.2.0. My question is
after downgrade, is there a way to fix this issue? Especially if it is done on the master
realm, then you simply cannot login anymore.
Thank you,
Sarp
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user