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.
Motivation and Context
Accessing the
ctx.request_context.request.user
is a simple way to retrieve the scopes available to a user (as well as access token and client ID, albeit client ID is already available as an attr to the Context class), which is useful for some request handling. E.g. in some MCP clients (OpenAI's DeepResearch MCP implementations), scopes cannot necessarily be handled at the middleware level because everything needs to hit a specificfetch
tool, so scopes need to be handled within the request callback. This means scopes need to be available within that callback. Adding auser
property to the ctx makes it easier for a developer to discern where they might get access to the user's scopes.How Has This Been Tested?
I have been able to access the
user
attribute viactx.request_context.request.user
in my own code.Breaking Changes
No
Types of changes
Checklist
Additional context