feat(playground): open device via grant request#79
Draft
marcus-pousette wants to merge 1 commit intomainfrom
Draft
feat(playground): open device via grant request#79marcus-pousette wants to merge 1 commit intomainfrom
marcus-pousette wants to merge 1 commit intomainfrom
Conversation
marcus-pousette
force-pushed
the
feat/invite-flows
branch
from
bb8496b to
03fed34
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
1 participant
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.
Stacked on #75 (base branch: feat/auth-cose-cwt).
This is the first slice of #77.
What changed
Open device no longer puts secrets in the URL hash. Instead, it opens a join only tab with an invite request id, waits for that tab to announce its replica pubkey, then sends a targeted grant (capability token plus doc payload key) over BroadcastChannel.
This keeps the demo flow one click, but avoids copying or leaking an invite link by default.
Notes
This is still a playground level flow. The payload key is sent as plaintext on the local BroadcastChannel. The protocol level upgrade for sealed key distribution and revocation lives in #77 and #78.