Authentication Troubleshooting
Registration, login, refresh, email verification, and provider-disabled failures.
Classify credentials, session, provider, verification, and cookie behavior separately.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
The source exposes machine-readable auth error codes for invalid credentials, token invalid/expired, session revoked, email not verified, provider disabled, and not implemented. Use the code and request ID as the starting point.
| Check | Source-backed expectation |
|---|---|
| Scope | Never ask users to send passwords, refresh cookies, or OAuth authorization codes. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | curl -i https://api.example.invalid/api/v1/auth/login |
| Stop condition | Unknown authorization, destructive impact, secret exposure, or conflicting evidence. |
Verification
Run the safe check, record its result, and compare the outcome with the documented contract. If the result depends on external configuration or provider availability, mark it as configuration-dependent rather than claiming a product guarantee.
curl -i https://api.example.invalid/api/v1/auth/login
Safety boundary
Examples are non-production and use placeholders. Do not deploy, reset, force a migration, create secrets, activate providers, replay sensitive work, or expose private data from this page.