You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have checked that this question would not be more appropriate as an issue in a specific repository
I have searched existing discussions and documentation for answers
Question Category
Protocol Specification
SDK Usage
Server Implementation
General Implementation
Documentation
Other
Your Question
Let's say I have:
an ASP.NET Web API configured to authenticate a user via OpenID Connect
an ASP.NET host with an MCP server
When the WebAPI starts, I also connect to the MCP Server so that the tool calls are faster.
Now, when the user make a requests to the WebAPI, I want to use the "access token" (JWT) to call the MCP Server so that the tools calls authorize the user.
I have some ideas, but I wonder whether there is some "best practice" to follow, without reinventing the wheel.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Pre-submission Checklist
Question Category
Your Question
Let's say I have:
When the WebAPI starts, I also connect to the MCP Server so that the tool calls are faster.
Now, when the user make a requests to the WebAPI, I want to use the "access token" (JWT) to call the MCP Server so that the tools calls authorize the user.
I have some ideas, but I wonder whether there is some "best practice" to follow, without reinventing the wheel.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions