Section Overview
Security
Typed session payloads, machine credentials, RBAC, and route protection without string-key auth chaos.
Support Semitexa
Built for developers who prefer control over magic.
Your support helps keep it fast, open, and evolving.
Route Map
Each feature page pairs live output with the source that produced it.
Identity
4Security
Session Auth
Google signs the user in, then the session stores the selected demo role and re-hydrates it on every request.
Security
Session Payloads
Semitexa forbids string-key session chaos: session state lives in typed Session Payloads or it does not exist.
Security
Google Authorization
Sign in with Google in Semitexa PHP: the OAuth flow, CSRF state, a typed session identity, and why long-lived SSE streams require an authenticated user.
Security
Machine Auth
Service-to-service authentication via Bearer tokens — issued from the CLI, scoped per route with #[RequiresScope], expiring, rotatable, revocable and audited.
Access Control
3Security
Protected Route
Add one access attribute and one optional permission attribute, and the framework enforces access: 401 for unauthenticated requests, 403 for unauthorized ones.
Security
Requires Permission
Declare one permission slug on the payload and let the framework enforce it before your handler runs.
Security
RBAC
Hybrid RBAC with coarse-grained capabilities, exact permission slugs, and module-owned permission catalogs.