An OAuth/OIDC client secret is assigned from a hard-coded string literal (options.ClientSecret = "...").
Why AI tools produce this: AI coding tools generate this anti-pattern by default, it appears in a large share of AI-written auth code.
Why this matters
This secret authenticates the whole application to the identity provider: committed to source control it is one search away from letting an attacker impersonate the app, redeem codes, and obtain tokens (CWE-798). This is a common AI-generated mistake: the literal secret is inlined to make the sample "just work" and never externalized.
Read it from configuration or a secret store instead (e.g. options.ClientSecret = builder.Configuration["Authentication:ClientSecret"] or a value from Azure Key Vault / environment) and rotate the leaked secret out of source control.
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.hardcoded-client-secret -- <reason>