ViewStoreConfiguration

The view store's beans: its callers, its write rules, its derived ids, its access policies and the application its reads need, the board lookup, the system views and the handlers of its own routes.

Its access policies: a view, preferences or a wording is read by its owner, in its space, within the caller's application (ViewStateAccess.APP_ID and the others' appId), and changed by its owner in its space (the default rule, which a policy replaces, so each says so); its commands keep to the application in the domain, whose rejections (APP_REQUIRED, view-store.not-found) the view store's clients read. A dataset wording belongs to its tenant: no owner is compared. A read without an application is refused (ViewStoreApps).

Its callers: CoSec's, the user, its roles and the app of its scope, which the edge's resolver reads from the security context CoSec put on the request, which the cosec profile has CoSec's gateway mode read from the identity the CoSec gateway verified and forwarded (CoSec-Identity, the app the gateway decided the request in). In development without CoSec, the host's, from the Wow-* identity headers any client sets (DevelopmentCallerResolver; a user acts as an owner with Wow-Owner, in the application Wow-App names); a request without a user is the anonymous caller, which reads the reserved owners' views. Either is behind the view store's reserved owners (ReservedScopeCallers). A node outside development without CoSec does not start.