Why the authorization inspector cannot explain enforcement (M98h).
rbac-not-configured — observation was opted into but the AuthPlugin
registered no authorization service (no rbac option), so there is no
first-party RBAC to observe.
provider-identity-unavailable — the registry lacks the optional
isCurrent identity predicate, so the source cannot verify it is still the
authoritative provider without resolving a replacement factory.
custom-provider — the current CAPABILITIES.AUTHORIZATION provider is not
the exact RbacService instance the plugin created, so a decision it
returns cannot be explained by the first-party evaluator.
unknown — the responder cannot name a reason: the connector answering
with no authorization source registered at all, or a client answering
locally before any server exchange. Availability is reported, never
improvised.
Why the authorization inspector cannot explain enforcement (M98h).
rbac-not-configured— observation was opted into but the AuthPlugin registered no authorization service (norbacoption), so there is no first-party RBAC to observe.provider-identity-unavailable— the registry lacks the optionalisCurrentidentity predicate, so the source cannot verify it is still the authoritative provider without resolving a replacement factory.custom-provider— the currentCAPABILITIES.AUTHORIZATIONprovider is not the exactRbacServiceinstance the plugin created, so a decision it returns cannot be explained by the first-party evaluator.unknown— the responder cannot name a reason: the connector answering with no authorization source registered at all, or a client answering locally before any server exchange. Availability is reported, never improvised.