Skip to content

catalog entry: request the groups token claim - #9

Merged
reoring merged 1 commit into
mainfrom
fix/groups-token-claim
Nov 10, 2026
Merged

reoring merged 1 commit into
mainfrom
fix/groups-token-claim

Conversation

@reoring

@reoring reoring commented Nov 10, 2026

Copy link
Copy Markdown
Contributor

Observed on Craftsman: a user whose Project access comes only through a group (/appthrust/teams/craftsman/developers → Editor) was refused project.read (403, "No authorization policy grant for action") from this app, because the app's token carries no groups claim. Other first-party apps (directory, tracker, builder-console) already request it.

access.tokenClaims is not part of the immutable runtime contract; a server dry-run update of the live definition on Craftsman is admitted. The OIDC client is re-registered, so signed-in users may be asked to sign in again.

The app asks the Platform API with the viewer's own token. A Project role
granted through a group is matched on the token's groups claim, so without it
a member with group-only access is refused project.read.
@reoring
reoring merged commit 259c973 into main Nov 10, 2026
3 checks passed
@reoring
reoring deleted the fix/groups-token-claim branch November 10, 2026 06:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant