Setu-TS
    Preparing search index...

    Type Alias AuthorizationDecisionReason

    AuthorizationDecisionReason:
        | "direct-role"
        | "inherited-role"
        | "direct-permission"
        | "direct-wildcard"
        | "role-permission"
        | "role-wildcard"
        | "not-held"
        | "compound-satisfied"
        | "compound-unsatisfied"

    Why the RBAC evaluator reached a decision's result (M98h).

    The vocabulary names the FIXED mechanism the evaluator used, not a policy name: direct-role/inherited-role for a role check, direct-permission / direct-wildcard / role-permission / role-wildcard for a permission check, not-held for a single check that found no grant, and the two compound outcomes compound-satisfied/compound-unsatisfied. Every step in a compound decision carries one of the single-check reasons; the compound reason describes the loop's overall stop.

    0.8.0