A JWT setup sets RequireSignedTokens = false on TokenValidationParameters.
Why AI tools produce this: AI coding tools produce this regularly, typically when prompted for a shortcut or a quick fix.
Why this matters
With signed tokens no longer required, an unsigned token (alg: none, empty signature segment) is returned by the handler as valid, so an attacker can forge tokens with arbitrary claims and no key at all (CWE-347). This is a common AI-generated shortcut to get past a "token is not signed" error during local wiring.
Leave RequireSignedTokens at its secure default (true) so every accepted token must carry a signature that verifies against a trusted key (IssuerSigningKey / keys from OIDC metadata).
Suppressing this rule
If a finding is a genuine false positive, scope the suppression to the exact line and leave a reason, never disable the rule project-wide. Disable directives are line-scoped by design.
// oauthlint-disable-next-line auth.csharp.jwt.require-signed-tokens-disabled -- <reason>