Configuration and security
System database
Section titled “System database”| Setting | Purpose |
|---|---|
SUPER_REDIS_MANAGER_DATABASE_PROVIDER |
SQLITE, POSTGRESQL, MYSQL, or MARIADB |
SUPER_REDIS_MANAGER_DATABASE_URL |
SQLite file or remote database URL |
DATABASE_URL |
PostgreSQL/MySQL/MariaDB-compatible URL |
SUPER_REDIS_MANAGER_SECRET_KEY |
Encryption key for Redis passwords and sensitive data |
The key must be stable and high entropy. Multiple instances must share it; losing the key makes existing encrypted credentials unreadable.
Session security
Section titled “Session security”- Authentication uses cookie sessions.
- Cookie-authenticated POST requests use CSRF protection.
- In-memory rate limits reduce abusive request volume.
- Administrators can revoke user sessions.
- Production requires HTTPS and restricted management ingress.
Authorization
Section titled “Authorization”Built-in roles, user management, and per-connection grants control team access. Users should see and operate only explicitly granted Redis connections. Combine least privilege, confirmations, and auditing for high-risk actions.
Connection security
Section titled “Connection security”- Redis passwords remain encrypted.
- TLS/SSL, SSH Tunnel, Sentinel, and Cluster are supported.
- Cluster-over-SSH uses
natMapfor node address mapping. - Sentinel-over-SSH establishes tunnels to discovered masters.
- Connection diagnostics and logs must never reveal passwords, keys, or tokens.
SQLite backup
Section titled “SQLite backup”File-backed SQLite deployments support encrypted backup and restore. Store backups separately, test restoration regularly, and tightly limit download and restore permissions.