OIDC-Login schlägt fehl, wenn nur ID-Tokens zurückgegeben werden, nach dem Upgrade auf OAuth2 2.x

david · 15. September 2026 um 21:21

Dies hätte durch Folgendes behoben werden sollen:

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`.

Bitte lass uns wissen, ob du nach dem Deployment dieses Commits weiterhin Probleme hast.

Thema		Antworten	Aufrufe
JWT::InvalidIssuerError on Decode JWT (OpenID Connect) Support openid-connect	4	1472	28. Juni 2022
OAUTH2 basic - a nightmare :-( SSO oauth2	20	1010	3. Dezember 2024
OIDC Error for OpenAI Discourse forum Support openid-connect , hosted-support , fixed	7	381	11. April 2026
Authentication failure! invalid_credentials: OAuth2::Error SSO openid-connect	0	457	21. März 2024
OpenIdAuthenticator plugin fails Development	2	1335	27. Februar 2019

OIDC-Login schlägt fehl, wenn nur ID-Tokens zurückgegeben werden, nach dem Upgrade auf OAuth2 2.x

Verwandte Themen