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
Run `validateClaimsSubsetBytes` against the entry's stored claims
inside `GetEntryClaims` and surface `ErrClaimsInsufficient` as 403 in
the handler. Without this, a `manageEntries` caller scoped to one team
could read the claim metadata of an entry scoped to a different team
even though the matching `PUT` would deny them — that asymmetry
contradicts the default-deny visibility rule in `auth.md` §4.
`GetEntryClaimsOptions` gains a `JWTClaims` field and `setJWTClaims`
setter so the handler can plumb the caller's JWT through `WithJWTClaims`,
mirroring how `UpdateEntryClaims` already works. Super-admin still
bypasses uniformly via the existing helper.
Tests: handler-level case for `ErrClaimsInsufficient` → 403; db-layer
cases for cross-team denied / covering caller succeeds; integration
sub-test exercising a cross-team writer against a platform-scoped
entry. Swagger regenerated for the new 403 response.
0 commit comments