Falha no login OIDC com respostas apenas de ID-token após atualização para OAuth2 2.x

david · Setembro 15, 2026, 9:21pm

Isso deveria ter sido corrigido por:

FIX: Accept an OIDC token response that carries only an id_token (#43587)

committed 03:53PM - 11 Sep 26 UTC

Some providers return a token response with no access token at all, or with an e…mpty `access_token` alongside the `id_token`. `oauth2` 2.x treats `id_token` as one of the keys that can hold the token value, so `AccessToken.from_hash` either takes the `id_token` and removes it from the params, leaving `access_token["id_token"]` nil and the JWT decode failing, or it takes the empty `access_token` and raises "OAuth2::AccessToken has no token". When userinfo is disabled the strategy reads everything it needs from the `id_token`, so build the access token directly and keep the whole parsed response in the params. - The spec for the userinfo-disabled path goes back to an `id_token`-only token response, which is what a provider with no userinfo endpoint sends. - A new case covers a response with a blank `access_token`.

Por favor, nos avise se você ainda estiver vendo problemas após a implantação desse commit.

Tópico		Respostas	Visualizações
JWT::InvalidIssuerError on Decode JWT (OpenID Connect) Support openid-connect	4	1472	28 de Junho de 2022
OAUTH2 basic - a nightmare :-( SSO oauth2	20	1011	3 de Dezembro de 2024
OIDC Error for OpenAI Discourse forum Support openid-connect , hosted-support , fixed	7	381	11 de Abril de 2026
Authentication failure! invalid_credentials: OAuth2::Error SSO openid-connect	0	457	21 de Março de 2024
OpenIdAuthenticator plugin fails Development	2	1335	27 de Fevereiro de 2019

Falha no login OIDC com respostas apenas de ID-token após atualização para OAuth2 2.x

Tópicos relacionados