An OpenID Connect handler turns PKCE off (UsePkce = false).
Why AI tools produce this: AI coding tools produce this regularly, typically when prompted for a shortcut or a quick fix.
Why this matters
Without Proof Key for Code Exchange, an authorization code intercepted on the redirect (a malicious app, a leaked URL, a network hop) can be redeemed by the attacker, defeating the code-flow protection that PKCE provides (CWE-287). This is a common AI-generated change made to work around a provider quirk and never reverted.
Leave PKCE enabled: it is the modern default (UsePkce = true) and is required for public clients. Fix the underlying provider configuration rather than disabling the proof key.
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.oauth.pkce-disabled -- <reason>