A requests call disables TLS certificate verification with verify=False.
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 silences the validation of the server's certificate, so an attacker who can intercept the connection can present any certificate and read or tamper with the traffic, a classic man-in-the-middle exposure. For OAuth/OIDC this leaks authorization codes, access tokens and client secrets.
Never set verify=False. Leave verification on (the default) so the system CA bundle is used. In development against a private CA, point verify at the CA bundle instead, e.g. requests.get(url, verify="/path/to/ca-bundle.pem") or set the REQUESTS_CA_BUNDLE env var (certifi).
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.py.flow.requests-verify-disabled -- <reason>