Repository navigation
Say that the pairing token is a credential - #327
Merged
Merged
Conversation
11 of 12 tasks
arturpragacz
approved these changes
Oct 23, 2026
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
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.
The Lifecycle paragraph of the Pairing PSK Flow says the pairing PSK is long-lived and never consumed, but not what that means for whoever holds the token.
Anyone holding it can pair a new server with the client at any time, with no gesture on the device and nothing shown to the owner.
This adds one sentence saying so. The implementation guide already tells manufacturers to keep the token inside the owner's platform and never print it where a visitor can photograph it.