Hardened Storage Infrastructure.
Every project variable and system credential passing through Authepy maps to isolated encryption layers. Sensitive credentials are protected through layered hashing and encryption controls designed to reduce exposure if stored data is compromised.
One-Way Key Hashing
To safely isolate active application keys, the platform utilizes strict cryptographic hashing. When you generate an API key (e.g., ath_sec_live_...), the plaintext key is displayed to you exactly once.
Before the key is stored, the secret is processed through a one-way SHA-256 digest. Only the resulting hash is retained, so the original API key is not stored in plaintext.
Native Crypto Primitives
Stored passwords and core routing hashes use Node.js cryptographic primitives with per-record salts, providing protection against common offline password-guessing and precomputed-hash attacks.
Dynamic Key Revocation
Internal keys can undergo instant manual rolling via the developer dashboard. Rolling a key immediately writes a `revoked` status to the database, instantly locking out any external endpoints utilizing the deprecated credential.