Gateways
A gateway is AuthNull's SSH jump server. It runs on a Linux machine in your network. Every SSH session to an endpoint goes through it. Older versions of the console called it a "Jump Server" or an "SSH Proxy".
To open gateways, choose Switch product → PAM and select Gateways in the sidebar.
The Gateways List
| Column | Shows |
|---|---|
| Gateway | The gateway name. Click it to open the gateway |
| Status | Online, Offline, In progress or Disabled |
| Public IP | The address operators connect to |
| Listening on | The address and port the gateway listens on (port 2222) |
Search by name, or filter by Status.
| Status | Meaning |
|---|---|
| In progress | Registered, but it has not checked in yet |
| Online | It is sending heartbeats |
| Offline | It has missed its heartbeats |
| Disabled | An administrator disabled it. Sessions through it are refused |
A gateway sends a heartbeat every 60 seconds. It shows as Offline after about 3 minutes (three missed heartbeats). The list refreshes every 60 seconds.
Row Menu
| Action | What it does |
|---|---|
| Open | Opens the gateway's overview |
| Enrol machines | Adds endpoints behind this gateway (administrators only) |
| Disable / Enable | Stops or restarts sessions through the gateway (administrators only) |
| Delete | Removes the gateway |
The gateway page has one tab, Overview. It shows what the gateway reports about itself and its host-key fingerprint.
How a Session Works
A session opens only when both are true:
- A policy grants the person that account on that endpoint, through that gateway.
- The person approves the push from your organisation's MFA provider (Duo Security or Okta Verify).
The gateway then reaches the endpoint with the account's vaulted password or a key. The person never sees it. The session is recorded and logged in Access Logs.
If either condition fails, the connection is refused. Every refusal looks the same. See Connecting by Name: Security.