WWW-Authenticate headers should be passed through #168

Activity

1. localden

   added

   bugSomething isn't workingSomething isn't working

   on Mar 7, 2025
2. cliffhall commented on Mar 31, 2025

   

   cliffhall

   on Mar 31, 2025

   Last edited by cliffhall

   Member

   More actions

   @localden you're right, but can you provide an example with steps to repro? I'm not sure if this is a failing of the Inspector or the SDK.
3. cliffhall

   added

   waiting on submitterWaiting for the submitter to provide more infoWaiting for the submitter to provide more info

   on Mar 31, 2025
4. olaservo

   added

   authIssues and PRs related to authorizationIssues and PRs related to authorization

   on Apr 30, 2025
5. cliffhall commented on May 13, 2025

   

   cliffhall

   on May 13, 2025

   Member

   More actions

   Without this, you don't have the means to respond to specific HTTP 401 errors. Right now, on any token validation error that the server responds with 401 Unauthorized the client will just act as if it needs to re-authenticate with no context as to why.

   Are you saying that WWW-Authenticate response headers are not making it to the client from the MCP Inspector's backing server?
6. olaservo

   added

   v2Issues and PRs for v2Issues and PRs for v2

   on Nov 11, 2025
7. olaservo commented on Nov 11, 2025

   

   olaservo

   on Nov 11, 2025

   Member

   More actions

   Closing as not planned and labeling with v2 in case we want to review for next version.
8. olaservo

   closed this as not plannedon Nov 11, 2025