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
{{ message }}
Repository navigation
[Client] Support token_endpoint_auth_method: client_secret_basic, client_secret_post, none #321
Per RFC 6749 §2.3 (and AS metadata token_endpoint_auth_methods_supported), the client must send its credentials to the token endpoint using whichever method the AS advertises:
Cross-reference: this work covers SEP-837 for the MCP Spec 2026-07-28 release — the spec aligns MCP DCR with OIDC's application_type requirements, which in turn constrains the available token_endpoint_auth_method values (confidential web clients vs public native clients).
Coordinate with #320 (DCR) which also covers SEP-837. See umbrella #338.
Activity
chr-hertel commentedon May 26, 2026
Cross-reference: this work covers SEP-837 for the MCP Spec 2026-07-28 release — the spec aligns MCP DCR with OIDC's
application_typerequirements, which in turn constrains the availabletoken_endpoint_auth_methodvalues (confidentialwebclients vs publicnativeclients).Coordinate with #320 (DCR) which also covers SEP-837. See umbrella #338.
[Client] Add OAuth authorization to the HTTP transport
[Client] Add OAuth authorization to the HTTP transport