You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Cedar authz: one evaluation cannot combine pinned upstream IdP claims with request-token claims (act) #7100
With authz.primaryUpstreamProvider set, the Cedar authorizer reads claims from exactly one source per request (pkg/authz/authorizers/cedar/core.go, resolveClaims):
A browser-flow identity is evaluated on the pinned upstream IdP's access token, plus the profile-claim fallback from its id_token.
Any other identity without the provider's credential is denied before evaluation.
No single evaluation can therefore combine the user's IdP claims (department, roles, group-like claims) with the delegation chain (act) on the request token. "Agent X acting for a user in department Y may call this tool" cannot be expressed.
A second gap: identities authenticated by a path with no upstream session that is not one of the two recognised grants are denied before policy runs. Workload / service-account tokens are the main case. So a pinned provider fails every such caller closed, even under permit(principal, action, resource);.
Ask
A way for one Cedar evaluation to see both sources without the provenance confusion resolveClaims was written to avoid. For example, keep claim_* as today and expose the request token's claims under a distinct, non-colliding prefix that thv_claim_source labels. How workload callers are evaluated under a pinned provider is part of the design question. Any widening there must stay opt-in and distinguishable by thv_claim_source.
Acceptance
One policy can condition on a pinned-IdP claim and on the request token's act in the same evaluation.
A request-token claim can never shadow or be read as an IdP claim, and the reverse.
Activity
tgrunnagle commentedon Nov 10, 2026
Closing: the use case that motivated this moved to a different approach, so there is no consumer for it right now.