Portal User Management
Manage portal admin accounts and their permissions. Portal users are separate from proxy clients.
Using an AI assistant? Give it this file.
/llms.md is a single Markdown file covering installation, configuration, quickstart, clients, upstreams, permissions, TLS, and production deployment. Copy it and paste it into your AI chat, or tell the AI to fetch https://drevnix.tech/llms.md.
Portal User Management
Portal users are accounts that log into the Drevnix web portal at :8001. They are entirely separate from proxy clients. Clients authenticate against the proxy (:8000) for docker pull, while portal users log into the admin interface to manage the system.
Permission model
Access within the portal is governed by fine-grained permission strings. Super-admin accounts hold all permissions. Non-super-admin accounts can be granted individual permissions:
| Permission string | Controls access to |
|---|---|
users:view | View portal user list |
cache:view | View cache management page |
audit-logs:view | View and search audit logs |
stats:view | View stats dashboard |
settings:view | View settings page |
activity-log:view | View activity log |
api:access | Use the REST API (port 8002) |
A portal user with no extra permissions can still manage upstreams, clients, and permissions. Those are the core functions available to all authenticated portal users.
Creating a portal user
Go to Users → Add User in the portal (super-admin only):
- Username: used to log in
- Password: hashed on save, never recoverable
- Permissions: select which additional capabilities to grant
Resetting a password
Portal users can change their own password via My Profile → Change Password.
Super-admins can reset any user’s password from Users → Edit User → Set New Password.
If all super-admin accounts are locked out, see Troubleshooting.
Deleting a user
Go to Users → Delete. Deletion is immediate. The user’s past actions in the activity log are anonymised rather than removed. This preserves the integrity of the audit trail while complying with GDPR right-to-erasure requirements.
SSO login
If SSO is configured, portal users can also log in via your identity provider. See SSO Configuration for setup details. SSO availability is controlled by your license.
Security notes
- Portal sessions expire after inactivity
- Rate limiting applies to portal login: 5 failed attempts within 15 minutes triggers a 15-minute lockout
- Keep the portal port (
:8001) internal or behind a VPN