Security
What we do with your credentials and tokens
Written for the person who has to approve this. Each statement below describes the shipped behaviour, not an aspiration.
Credentials
- Passwords are hashed with Argon2id. A 10,000-entry common-password list and a 12-character minimum are enforced; ten failed attempts lock the account for fifteen minutes.
- Client secrets are stored as keyed hashes and shown exactly once at creation. Each client may hold two secrets so rotation never causes downtime.
- Password reset, e-mail verification and invitation links are single-use and expire.
Tokens
- Authorization code flow requires PKCE with S256 for every client type; plain challenges are refused.
- Refresh tokens are single use. Replaying a consumed token revokes its whole family.
- Access tokens are signed JWTs (RS256) with explicit audience; keys are published at
https://iam-test.extremegym.com.mx/.well-known/jwks.jsonand rotated with an overlap window. - Redirect URIs match exactly. No wildcards, no fragments, HTTPS except loopback for development.
Sessions and MFA
- Browser sessions are cookies flagged
__Host-, HttpOnly, Secure, SameSite=Lax, validated against the server-side session on every request. Password change, disable and reset end every session at once. - Time-based one-time passwords (RFC 6238) with ten single-use recovery codes. Administrative roles must enrol before they can act.
- Tokens record the authentication methods used (
amr), so resource servers and policies can require MFA.
Authorization
- One evaluator decides everything: explicit deny beats allow, anything unmatched is denied.
- Organization administrators only ever see their own organization; the API enforces this, not the UI.
- Every use of the superuser bypass is written to the audit log.
Data
- PostgreSQL with separate roles for the application (no DDL, append-only audit) and maintenance.
- Deleted users are anonymised after 30 days; audit history is kept for the plan's retention window.
- Secrets never appear in logs or audit details; the audit writer refuses keys that look like secrets.
Operations
- Rate limits per IP and per account on sign-in, reset and MFA endpoints; per client on the token endpoint; per caller on the API.
- Health endpoints report database, signing-key expiry and Consola Central reachability.
- Security headers on every response: strict transport security, content security policy, frame denial, no referrer leakage.
Reporting an issue
If you believe you have found a vulnerability, contact ITFortal through the channel in your service agreement. We acknowledge reports and keep you informed until the issue is resolved.