Repository navigation
docs(protocol): scope the URL elicitation user check to authenticated users - #2641
Merged
Merged
Conversation
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 URL-mode rule that the Agent MUST verify the authenticated user who started an elicitation also completes it can't be met during
auth/login(which #2624 documents) or by Agents without user authentication.On v2 elicitation (stable and draft), the rule is scoped like the binding rule earlier on the page:
auth/login: the Agent MUST tie completion to the issued elicitation and its connection, for example with an unguessable single-usestatevalue, and MUST NOT apply the result to a different connection.This is what OAuth
statealready does, so it still closes login-link phishing. No wire changes, v2 only.