Skip to content

oauth with different oauth server #795

@matteo-rama

Description

@matteo-rama

Inspector Version

MCP Inspector v0.16.6

Describe the bug

using oauth2 with a different server (correctly reported in .wellknown host) i got redirected to the base host /authorize without using the correct oauth server.

details:

mcp server -> http://localhost:9090/sse

http://localhost:9090/.well-known/oauth-authorization-server

{
  "introspection_endpoint": "https://pippo.com/oauth2/introspect",
  "revocation_endpoint": "https://pippo.com/oauth2/revoke",
  "token_endpoint_auth_methods_supported": [
    "client_secret_basic"
  ],
  "jwks_uri": "https://pippo.com/oauth2/jwks",
  "grant_types_supported": [
    "client_credentials"
  ],
  "issuer": "https://pippo.com",
  "token_endpoint": "https://pippo.com/oauth2/token"
}

now, if i press "connect" i got redirect at

http://localhost:9090/authorize?response_type=code&client_id=152340&code_challenge=kapEdY6SCltWsInjXI0xjOzzHIE02Ua9LaOZ89ZfqcQ&code_challenge_method=S256&redirect_uri=http%3A%2F%2Flocalhost%3A6274%2Foauth%2Fcallback&state=b33899138b5247fd3f4d16c31ebd85697d6ebeb3a516a8408732470f4c065597&scope=read

that doesn't exist

what i am doing wrong?

Metadata

Metadata

Assignees

No one assigned

    Labels

    authIssues and PRs related to authorizationbugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions