Documentation
Web Auth
Understand the shared token/password login and the current cookie session model.
Auth inputs
The app accepts a single shared credential field on /login.
Either of these Worker environment values can satisfy that credential:
AUTH_PASSWORDAUTH_TOKEN
Cookie session
When login is enabled, the server issues a cookie named cloudflare_inbox_session.
Current behavior:
HttpOnlySameSite=LaxPath=/Max-Age=30 daysSecurewhen the request is HTTPS
Validation model
This alpha app does not store sessions in a database.
Instead, it computes the expected cookie value from:
- a fixed app prefix
AUTH_COOKIE_SECRETAUTH_PASSWORDAUTH_TOKEN
That means rotating any of those values invalidates all existing sessions immediately.
Protected surfaces
/app/send/thread-read
The /blob route remains public for now so emailed attachment fallback links still work outside the logged-in browser session.
When to harden it later
- per-user sessions
- session revocation without rotating the global secret
- attachment privacy on emailed
/bloblinks - audit trails tied to individual operators