Authentication and Sessions
Bearer access tokens, refresh cookies, login, and session boundaries.
Authenticate before protected routes and keep refresh-cookie behavior separate from bearer-token behavior.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
The source registers a JWT guard, an autocore_rt cookie, access-token and session services, and explicit provider availability. Public routes must be marked public; the absence of a bearer decorator does not make a guarded route anonymous.
| Check | Source-backed expectation |
|---|---|
| Scope | Never place tokens, cookies, or provider credentials in documentation examples or incident evidence. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | curl -H 'Authorization: Bearer [access-token]' https://api.example.invalid/api/v1/me |
| 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 -H 'Authorization: Bearer [access-token]' https://api.example.invalid/api/v1/me
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.