docs(spec): Recommend principle of least privilege for in-task authorization - #2066
Open
mikeas1 wants to merge 3 commits into
Open
docs(spec): Recommend principle of least privilege for in-task authorization#2066mikeas1 wants to merge 3 commits into
mikeas1 wants to merge 3 commits into
Conversation
Add guidance for in-task authorization to scope credentials to the least privilege required for the requested action. SHOULD is used as there is no protocol defined way of specifying the representation of an action, other than via general guidance to use TaskStatus.message, nor a protocol requirement for using specific credential types that are capable of such tight scoping.
Contributor
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
|
|
||
| - Credentials SHOULD be bound to the agent which originated the request, such that only this agent is able to use the credentials. This ensures that credentials propagating through a chain of A2A requests are only usable by the requesting agent. | ||
| - Credentials containing sensitive information SHOULD be only readable by the agent which originated the request, such as by encrypting the credential. | ||
| - Credentials SHOULD grant the minimal permissions required to perform the desired action. |
Contributor
There was a problem hiding this comment.
Suggested change
| - Credentials SHOULD grant the minimal permissions required to perform the desired action. | |
| - Credentials SHOULD grant the minimal permissions required to process the message. |
Contributor
There was a problem hiding this comment.
which message? In a task with multiple turns / follow up messages I think this is ambiguous
Contributor
Author
There was a problem hiding this comment.
I guess I could just extend the wording:
... process the messages which elicited the TASK_STATE_AUTH_REQUIRED
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
5 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.
Add guidance for in-task authorization to scope credentials to the least privilege required for the requested action. SHOULD is used as there is no protocol defined way of specifying the representation of an action, other than via general guidance to use TaskStatus.message, nor a protocol requirement for using specific credential types that are capable of such tight scoping.