-
Notifications
You must be signed in to change notification settings - Fork 2k
MultiAuth breaks EntraOBOToken dependency injection #3605
Copy link
Copy link
Closed
Labels
authRelated to authentication (Bearer, JWT, OAuth, WorkOS) for client or server.Related to authentication (Bearer, JWT, OAuth, WorkOS) for client or server.bugSomething isn't working. Reports of errors, unexpected behavior, or broken functionality.Something isn't working. Reports of errors, unexpected behavior, or broken functionality.serverRelated to FastMCP server implementation or server-side functionality.Related to FastMCP server implementation or server-side functionality.
Metadata
Metadata
Assignees
Labels
authRelated to authentication (Bearer, JWT, OAuth, WorkOS) for client or server.Related to authentication (Bearer, JWT, OAuth, WorkOS) for client or server.bugSomething isn't working. Reports of errors, unexpected behavior, or broken functionality.Something isn't working. Reports of errors, unexpected behavior, or broken functionality.serverRelated to FastMCP server implementation or server-side functionality.Related to FastMCP server implementation or server-side functionality.
What happened?
Follow-up to #3035 (closed). Using
EntraOBOTokenas a tool dependency fails at runtime when the server is configured withMultiAuth, even ifMultiAuthwraps anAzureProvider.MRE:
Actual:
Expected:
EntraOBOTokenresolves successfully whenMultiAuthwraps anAzureProvider.The failure is in
_EntraOBOToken(fastmcp/server/auth/providers/azure.py), which does a hardisinstance(server.auth, AzureProvider)check that doesn't look throughMultiAuth— not obvious from the public API.Version Information