AutoCore Authentication Security Checklist
A release checklist for credentials, OAuth, cookies, sessions, and recovery flows.
Exercise both success and abuse-shaped paths in a disposable local environment. Record results without retaining credentials or token values.
Release candidate source
This article reflects the audited AutoCore source revision 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60 and immutable release-candidate tag v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f. Configuration and external provider behavior remain deployment-dependent.
Source boundary
| Control | Source-verified behavior |
|---|---|
| Secret | Production access JWT configuration is present, long enough, and not the development fallback. |
| Abuse | Login, refresh, reset, and verification throttles behave as expected. |
| Cookie | Refresh cookie flags and expiry match the intended deployment policy. |
| Recovery | Reset, password change, and revocation invalidate prior credentials as specified. |
| OAuth | State, nonce, PKCE, issuer, audience, and verified-email checks are verified when Google is enabled. |
High-risk operation
Use explicit authorization, a written reason, a confirmation gate, and post-action verification. Documentation does not grant permission to change a deployment.
Operational controls
Use the smallest verified control for the task. Keep provider, host, legal, and operator responsibilities separate from application behavior. When a control is not implemented or not verified, leave it disabled or mark it as a limitation.
Result format
For each item, record pass, fail, or not_applicable, the evidence reference, the reviewer, and the next action. Do not paste credentials or raw provider payloads into the record.
Verification
Verify the route, relevant API or configuration state, negative path, audit/evidence result, and public effect before closing the task. Record unknown or configuration-dependent behavior as a limitation.