{"version":"2.1.232","anchor":"empty-oidc-claims-no-longer-count-as-values","canonical_anchor":"empty-oidc-claims-no-longer-count-as-values","heading":"Empty OIDC claims no longer count as values","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/empty-oidc-claims-no-longer-count-as-values","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Empty OIDC claims no longer count as values\n\nBlank OIDC claims no longer count, so identity falls through to the userinfo lookup.\n\n**What**\n\nReading identity claims from an OIDC token now rejects zero-length strings, so a blank claim falls through to the userinfo lookup instead of being accepted as a value. Affects OIDC-configured deployments only.\n\n**Details**\n\n- Scalar claims require `J.length > 0`; array claims filter on `typeof O === \"string\" && O.length > 0`.\n- Presence checks were split into their own helpers ahead of the userinfo fallback.\n\n**Evidence**\n\n`oidc id_token claim names request_id=`\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}