PKCE S256 Enforcement coming in March 2027
Action required: PKCE with S256 will be mandatory on March 1, 2027
S256 will be mandatory on March 1, 2027To strengthen the security of Vibe integrations and align with the highest industry standards (RFC 9700 and the upcoming OAuth 2.1), every request in the OAuth Authorization Code flow must use PKCE with the S256 method starting March 1, 2027.
PKCE ensures that an intercepted authorization code cannot be exchanged for tokens by anyone else. If your app doesn't send PKCE parameters, new authorizations will fail with invalid_request, and your users won't be able to connect their Vibe accounts.
To get ready, generate a code_verifier for each authorization request, send its S256 code_challenge to /oauth2/auth, and include the code_verifier when you exchange the code at /oauth2/token. You still need your client secret and the state parameter, so keep sending them. The plain method is not supported. See the updated OAuth guide for the step-by-step flow and code samples in JavaScript and Python.
Refresh tokens your users already have will keep working, and the Client Credentials flow is not affected.