The user to evaluate (e.g. provider.CurrentUser).
The MJ: Authorizations.Name to check (e.g.
REALTIME_ADVANCED_SESSION_CONTROLS).
The cached-metadata source — typically the component's
ProviderToUse (IMetadataProvider).
true only when an active authorization of that name grants the user via an
Allow role with no Deny veto; false in every other (including degraded) case.
PURE client-side check of whether
userholds the named MJ Authorization, resolved entirely from cached metadata: Authorizations ↔ Authorization Roles ↔ the user's roles.Semantics mirror
AuthorizationInfo.UserCanExecute(the canonical server/core evaluation): the authorization must exist and be ACTIVE; any matching Deny row on one of the user's roles vetoes globally; otherwise at least one matching Allow row is required. Name matching is trim + case-insensitive; UUID comparisons useUUIDsEqual(SQL Server vs PostgreSQL casing safe).Defensive by design: any missing piece — no user, no roles, no provider, missing metadata collections, unknown/inactive authorization, null
Type— resolves tofalse. This helper is a disclosure gate only; the server independently enforces the authorization on the protected mutation.