{"version":"2.1.284","anchor":"mcp-oauth-a-private-key-jwt-auth-method-is-registered-as-n","canonical_anchor":"mcp-oauth-a-private-key-jwt-auth-method-is-registered-as-n","heading":"OAuth registration sends \"none\" in place of private_key_jwt","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/mcp-oauth-a-private-key-jwt-auth-method-is-registered-as-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### OAuth registration sends \"none\" in place of private_key_jwt\n\nWhen Claude Code registers as an OAuth client, a configured private_key_jwt authentication method is now sent as \"none\"\n\n**Unclear.** Whether this applies to MCP server sign-in specifically is not confirmed.\n\n**What**\n\nWhen Claude Code registers itself with a server that uses OAuth, a common sign-in standard, it tells the server how it will prove its identity. If that method is configured as `private_key_jwt`, Claude Code now sends \"none\" instead of passing the value through. Other values work as before, using `client_secret_basic` or `client_secret_post` depending on what the server supports.\n\n**Why**\n\nServers that advertise `private_key_jwt` should now get a registration they accept, instead of one that Claude Code cannot then complete.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}