Database auto-update for Basic Authentication does not work under some conditions about frost-server HOT 3 CLOSED

I've also noticed this, very irregularly, and hard to reproduce reliable. It's very bizarre.

Liquibase claims it updated the database successfully, and when you call the DatabaseUpdate script, it says there's nothing left to do. But when you access the database the tables are not there, and also the entries in the DatabaseChangeLog are not there.
Restarting the server causes Liquibase to re-run the updates, since obviously they did not happen.

It's like the updates happen in a transaction that only Liquibase can see that is never committed...

For now I did notice a workaround. If you disable persistence_autoUpdateDatabase but keep auth_autoUpdateDatabase enabled it works. The auth tables are initialised when they are needed the first time (and not on the start of FROST) and running Liquibase form the Database Update script works correctly. This also leads me to suspect the issue is in how Liquibase accesses the connection when it is triggered during service start...

By the way, it's quite brave of you to already experiment with the Fine Grained security implementation :) Would you mind telling some more about your use cases? If you can't post that here, feel free to drop me an email...

from frost-server.

I've implemented a work-around for the Liquibase bug.

from frost-server.

It's a bug in Liquibase:
https://forum.liquibase.org/t/bug-in-v4-21-changesets-are-not-run-because-abstractupdatecommandstep-isuptodatefastcheck-incorrectly-caches-value-across-schemas/8286

liquibase/liquibase#4304

from frost-server.