Deprixa Plus — Technical Architecture · Authentication Architecture
Deprixa Plus supports four authentication methods:
| Method | Used By | Implementation |
|---|---|---|
| Email + Password | All users — primary login method | Laravel built-in auth with session cookies. Rate-limited to prevent brute force. |
| TOTP 2FA | Any user who enables it; enforced for admins if configured | Time-based One-Time Password (RFC 6238). Compatible with Google Authenticator, Authy, 1Password. |
| API Bearer Token | External integrations, mobile apps | Laravel Sanctum personal access tokens. Created via POST /api/tokens. Revocable. |
Inertia SPA vs. REST API
The Inertia frontend uses Laravel's session-based authentication (cookies) — not Bearer tokens. Bearer tokens are only for external API consumers. This means the Inertia app benefits from CSRF protection and traditional Laravel session security automatically.