-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Private key jwt scopes #1443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Private key jwt scopes #1443
Conversation
🦋 Changeset detectedLatest commit: 368ec94 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@modelcontextprotocol/client
@modelcontextprotocol/server
@modelcontextprotocol/express
@modelcontextprotocol/hono
@modelcontextprotocol/node
commit: |
|
@pcarleton in this branch, should I add the changeset then? |
|
yep this one needs a changeset |
|
@pcarleton I think this is all set. Since this adds options to the API, I've made it a |
This adds support for a
scopeparameter in the client credentials OAuth providers as described in #1430.Motivation and Context
A client may now specify which scopes it requests to the Authorization Server.
How Has This Been Tested?
I have tested against an OAuth-compliant Authorization Server and an MCP Resource Server enforcing access control based on Access Token scopes.
Breaking Changes
No, the change is opt-in and the default behavior remains the same.
Types of changes
Checklist
Additional context
These changes have been backported to v1.x in #1442.