Details
-
Bug
-
Resolution: Unresolved
-
Neutral
-
None
-
6.2.27
-
None
-
Magnolia 6.2.28
Postgres DB
Description
Steps to reproduce
- Update a Magnolia Project from 6.2.24 to 6.2.28
- Try to loging with superuser
Expected results
The superuser account should work like before.
Actual results
There is an Exception (see attached screenshot)
javax.security.auth.login.LoginException: java.lang.IllegalArgumentException: Invalid salt version.
Workaround
Login with another user (If you have one) and reset the superuser password. If you don't have one, you can bootstrap the superuser on module update with the Version Handler.
Development notes
It did happen so all Projects we updated that run on Mironet Servers (shared hostings & Kubernetes). All use a postgres Database. It did not happen on our local instances thet use h2 Database.
I think the breaking change is in version 6.2.27 but did not find anything in the release notes that could cause this issue.
Checklists
Acceptance criteria