Critical Description
We currently call `Configuration.setConfiguration(null)` from a couple of places in our codebase (`Login` and `JaasUtils`) to force `Configuration` to be reloaded. If this code is removed, some tests can fail depending on the test execution order.
Ideally we would not need to call `setConfiguration(null)` outside of tests. Investigate if this is possible. If not, we should at least ensure that reloads are done in a safe way within our codebase (perhaps using a lock).