Modern Auth Lab

Modern Auth Lab is a progressive security project for exploring modern web authentication with PHP, vanilla JavaScript, TOTP, Passkeys/WebAuthn, controlled MFA fallback strategies, tests, coverage, mutation testing, and CI/CD.

The project is intentionally built step by step. It starts with a small framework-free foundation before adding authentication behavior.

Current Status

Implemented foundation:

• Agent development rules.
• Project roadmap and security documentation.
• PHP 8.5 backend tooling with Composer.
• PHPUnit, PHPStan, and PHP CS Fixer.
• Vite frontend tooling with vanilla JavaScript.
• Vitest, V8 coverage, ESLint, and Prettier.
• Minimal PHP HTTP foundation with public/ as the web root.
• GET /health diagnostic route.
• Server-side session primitives and explicit authentication session states.
• CSRF token primitives for future session-backed forms and unsafe requests.
• SQLite persistence foundation with migration tracking.
• User persistence schema, repository, password hashing, and password verification workflow.

Not implemented yet:

• HTTP password login.
• Login-backed authenticated sessions.
• CSRF middleware and protected forms.
• TOTP.
• Passkeys/WebAuthn.
• Trusted devices.
• Recovery flows.
• User-facing SQLite/libSQL persistence features.
• CI/CD.

Requirements

• PHP 8.5+
• Composer 2+
• Node.js 22+
• npm 10+
• SQLite PDO extension

Installation

Install backend dependencies:

composer install

Install frontend dependencies:

npm install

Backend Commands

Start the PHP development server:

composer serve

Health check:

curl http://127.0.0.1:8080/health

Run backend checks:

composer test
composer analyse
composer cs:check

Frontend Commands

Start the Vite development server:

npm run dev

Run frontend checks:

npm run build
npm test
npm run coverage
npm run lint
npm run format

Project Structure

assets/       Frontend JavaScript and CSS
docs/         Roadmap, security notes, architecture notes, and decisions
public/       Public web root
src/          PHP application source
tests/        Backend and frontend tests

Security Direction

Security-sensitive decisions must remain server-side. Frontend code may improve user experience, but it must not decide authentication, authorization, MFA fallback eligibility, recovery state, or trusted-device policy.

Authentication will be modeled as explicit states. Partial authentication must not be treated as a full authenticated session.

Documentation

Start with:

• Roadmap
• Architecture
• Security model
• Authentication flows
• Passkeys and WebAuthn
• Fallback strategy
• Decision records

Versioning

main represents the latest project version. Stable milestones are preserved with Git tags and GitHub releases.