-
Notifications
You must be signed in to change notification settings - Fork 3.4k
auth specification in ClientSessionGroup #1723
Copy link
Copy link
Open
Labels
P2Moderate issues affecting some users, edge cases, potentially valuable featureModerate issues affecting some users, edge cases, potentially valuable featureauthIssues and PRs related to Authentication / OAuthIssues and PRs related to Authentication / OAuthenhancementRequest for a new feature that's not currently supportedRequest for a new feature that's not currently supportedhelp wantedContributions especially welcomeContributions especially welcomeneeds decisionIssue is actionable, needs maintainer decision on whether to implementIssue is actionable, needs maintainer decision on whether to implement
Description
Metadata
Metadata
Assignees
Labels
P2Moderate issues affecting some users, edge cases, potentially valuable featureModerate issues affecting some users, edge cases, potentially valuable featureauthIssues and PRs related to Authentication / OAuthIssues and PRs related to Authentication / OAuthenhancementRequest for a new feature that's not currently supportedRequest for a new feature that's not currently supportedhelp wantedContributions especially welcomeContributions especially welcomeneeds decisionIssue is actionable, needs maintainer decision on whether to implementIssue is actionable, needs maintainer decision on whether to implement
Description
It would be nice for the
ClientSessionGroupto be OAuth compatible by allowing us to specify the OAuthhttpx.Authprovider when passing in theServerParametersrather than passing the bearer tokens manually via theheadersfield. This will allow us to do the OAuth token exchange flow straight from theClientSessionGroup.References
Here is the singleton
ClientSessionexample of an OAuth flow: https://github.com/modelcontextprotocol/python-sdk/blob/main/examples/clients/simple-auth-client/mcp_simple_auth_client/main.pyIt would be nice to have an example of a
ClientSessionGroupusing that same flow.