Configure access, transport, and audit for your site.
Authentication is off by default. With authentication on, the gateway checks project permissions using scoped sessions. Your reverse proxy provides browser HTTPS, pinned certificates secure the gateway mesh, and the audit log records runtime actions.
Local accounts with explicit project bindings.
Choose embedded local accounts or shared gateway accounts for each project. Bind usernames to project roles in the manifest and keep credentials outside Git.
Embedded users
AvailableLocal accounts use Argon2id password hashes and explicit project role bindings.
Gateway accounts
AvailableProjects can explicitly select shared gateway accounts as a trusted user source and bind usernames to roles.
Project sessions
AvailableProduction and draft logins have separate session scopes and cookie paths.
CSRF protection
AvailableHTTP writes require session cookies and a matching CSRF token; WebSockets use single-use tickets.
Each project has its own roles and tag namespace.
The gateway checks tag writes and alarm actions against the roles in your project session.
Project role capabilities
Role flags control project tag writes, alarm acknowledgment and shelving, and history reads.
Project scope
Projects have separate tag namespaces and session scopes. Explicit device and database scope lists restrict shared gateway resources.
Tag-write authorization
The gateway checks project tag-write permissions for browser and HTTP API requests.
Named queries
PostgreSQL named queries validate required parameters and value types. They use the gateway administrator session.
# projects/press-line-a/project.toml — role binding excerpt [[project.auth.bindings]] source = "local" username = "operator" roles = ["operator"] [project.auth.roles.operator] can_write_tags = true can_ack_alarms = true can_read_history = true # Configure the local embedded user source and credentials separately. # Enable gateway authentication to enforce these permissions.
# AuditEvent fields — project-scoped tag write
{
"timestamp": "<UTC timestamp>",
"gateway_id": "<gateway UUID>",
"project_id": "<project UUID>",
"actor": "operator",
"event_type": "tag.write",
"subject": "recipes/active_id",
"outcome": "success",
"details": { "value": "HX-204" }
}
Proxy HTTPS for browsers. Pinned mutual TLS between gateways.
Browser HTTPS
AvailableYour reverse proxy terminates HTTPS and forwards HTTP to the gateway. Use secure session cookies behind TLS.
Mesh mutual TLS
AvailableGateway peers use mutual TLS with pinned certificates. Configure trusted peer fingerprints for each connection.
Certificate rotation
AvailableMesh certificates are self-signed. Rotation requires restarting the gateway and updating peer certificate pins.
Secret references
AvailableReference database and notification secrets through environment variables. Keep device credentials in secured deployment configuration outside Git.
Runtime actions, recorded as structured data.
The audit log records authentication, configuration, tag-write, and alarm actions as JSON lines and, when configured, in PostgreSQL. Records include the actor, event type, subject, outcome, and event details, with project identity for project-scoped actions.
- • Authentication — enable sessions and bind users to project roles.
- • Network design — configure firewalls, proxy HTTPS, and mesh peer trust.
- • Recovery — secure credentials, keys, identity, and runtime backups.
Use these records in your OT/IT security and regulatory reviews.
- • Project permissions control alarm acknowledgment.
- • Shelve an individual alarm for a bounded duration.
- • Query recorded audit events by event type and subject.
- • Keep audit files and configured PostgreSQL records in your retention plan.
Bring your security review to the table early.
Walk through local authentication, project permissions, transport configuration, and audit records with your OT/IT security team.