Security
How Clowk keeps authentication secure: HS256 JWT signing, token expiry, HTTPS only, bcrypt passwords, OAuth state, rate limits and data isolation.
JWT signing
All tokens are signed with HS256 using a secret key unique to your project. The key is generated when you create a project and can be rotated from the dashboard.
Token expiration
JWTs expire after 24 hours by default. You can configure the expiration time in your project settings.
HTTPS only
All communication between your app, Clowk, and OAuth providers happens over HTTPS. Tokens are never transmitted over unencrypted connections.
No plaintext passwords
Passwords are hashed with bcrypt (cost factor 12) before storage. Clowk never stores or logs plaintext passwords.
OAuth state parameter
Clowk uses the OAuth state parameter to prevent CSRF attacks during the authentication flow. Each request generates a unique state value that is validated on callback.
Rate limiting
Authentication endpoints are rate-limited to prevent brute-force attacks:
- Sign-in: 10 attempts per minute per IP
- Sign-up: 5 attempts per minute per IP
- Password reset: 3 attempts per minute per email
Data isolation
Each project has its own database partition. User data from one project is never accessible from another.
Reporting vulnerabilities
If you discover a security vulnerability, please email [email protected]. Do not open a public issue.
FAQ
Answers to common questions about Clowk: pricing, open source and hosting, Clowk vs Clerk, supported frameworks, password storage and what if it goes down.
Contributing
How to contribute to Clowk: open pull requests to the SDKs and docs, build a community SDK for a new framework, and report bugs or request features.