Choose authentication for the client
A same-site browser application may use secure session cookies with CSRF protection. Mobile apps and third-party integrations may need scoped API tokens or an established OAuth flow.
Treat bearer tokens as secrets
Send tokens in the Authorization header over HTTPS. Never put them in query strings, URLs, analytics events, or ordinary logs.
Store hashes of opaque random tokens where practical. Support expiration, revocation, scopes, and rotation.
Enforce authorization per resource
A valid token proves that a credential was presented; it does not grant unrestricted access. Check token scopes and the user's permission for every requested resource.
Validate and monitor
Check HTTP method, content type, payload size, required fields, and data types. Use prepared statements, rate limits, and audit logs for sensitive operations. Keep secrets in private configuration.