feat(relayauth): add optional product_id to JWT claims#15
Merged
khaliqgant merged 1 commit intomainfrom Apr 20, 2026
Merged
Conversation
Additive, MINOR bump. mint() accepts an optional productId, verify() surfaces it on the result without enforcing anything. Legacy tokens (no product_id) continue to validate exactly as before. Enforcement happens in downstream consumers behind a per-workspace policy flag (see cloud/specs/platform-architecture-v1.md, wave 2). No breaking change.
kjgbot
force-pushed
the
khaliq/platform-v1-relayauth-workspace-scope
branch
from
1f46adb to
f33bb02
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Additive, MINOR bump. mint() accepts an optional productId, verify() surfaces it on the result without enforcing anything. Legacy tokens (no product_id) continue to validate exactly as before. Enforcement happens in downstream consumers behind a per-workspace policy flag (cloud/specs/platform-architecture-v1.md, wave 2).
Part of platform-v1 migration (issue #84).