Why AI tools produce this: AI coding tools produce this regularly, typically when prompted for a shortcut or a quick fix.
Why this matters
The client secret authenticates your application to the authorization server's token endpoint; committed to source control it is one search away from compromise, letting an attacker impersonate your client to redeem authorization codes and mint access tokens (CWE-798). This is a common AI-generated mistake: a literal secret is inlined to make the OAuth sample "just work" and never externalized.
Load the secret from outside the source: a @Value("${...}")-injected property, System.getenv(...), Environment.getProperty(...), or a secret manager (Vault, AWS Secrets Manager). In Spring Boot, prefer spring.security.oauth2.client.registration.<id>.client-secret bound from an environment variable. Rotate any secret already checked in.
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.