GeoServer does not load settings of a protected workspace when using Catalog Mode == Mixed
Steps to reproduce:
Add a role "testrole"
Add a workspace "testworkspace"
Add the following data access rules:
and assign these rules to the role "testrole"
Restart GeoServer and have a look at the log file. There is a stack trace caused by
As a consequence, GeoServer does not load the workspace settings for "testworkspace" and falls back to the default values. Unfortunately there is no indicator on the admin GUI that something went wrong.
A debug session shows that GeoServer uses the SecureCatalog implementation during bootstrapping. During this phase is the current user is null (treated as anonymous).
1) Is it possible to use the non secure implementation of the catalog during bootstrapping
2) If not, does it make sense to boostrap as "admin" or even better as "root" user.