The Airlock web interface is a browser-based interface for accessing resources, viewing active sessions and recordings, managing access requests, users, and roles.
Joining an active session
The web interface lets you view and join active SSH sessions through a terminal in the browser.
Active SSH sessions you have access to are shown on the Active Sessions page in the left navigation panel. If the Active Sessions tab is missing, your role lacks the list permission for the ssh_session resource. Contact the administrator to update the role.
When you click Join, you must select a participant mode:
- observer — view-only, no input.
- moderator — view and forcibly terminate or pause the session, no input.
- peer — collaborative: view and input.
If the join button is absent, you have no permissions in any mode.
Idle timeout
After login, the web interface checks session activity every 30 seconds. If there has been no interaction with any browser tab (keyboard, mouse) for more than 10 minutes, the user is logged out.
To change the default timeout (10 minutes), the administrator sets the web_idle_timeout parameter in the Auth Service configuration.
Dynamic configuration
airctl edit cluster_networking_configChange the spec.web_idle_timeout value:
kind: cluster_networking_config
metadata:
...
spec:
...
web_idle_timeout: 10m0s
...
version: v2After saving, airctl updates the resource:
cluster networking configuration has been updatedStatic configuration
Update /etc/airlock.yaml in the auth_service section and restart the airlock daemon:
auth_service:
web_idle_timeout: 10m0sWeb interface sections
| Section | Purpose |
|---|---|
| Resources | List of available servers, databases, and Kubernetes clusters |
| Active Sessions | Active SSH sessions and the ability to join them |
| Session Recordings | Recorded SSH and Kubernetes sessions |
| Access Requests | Create and review access requests (see Access Requests) |
| Management | Manage users, roles, and settings (for administrators) |
Kubernetes via the web interface
The Kubernetes tab shows clusters you have access to. Click Connect — a window appears with commands for connecting via airsh kube login in the terminal.
Databases via the web interface
The web interface does not establish a direct connection to databases, but shows available databases on the Databases tab and provides airsh commands for connecting from the local terminal.