Results
Verification results are available from the session details in the app and from the REST API.
Session statuses
Section titled “Session statuses”| Status | Meaning |
|---|---|
pending | The session is waiting for a successful verification or remains open for more connections. |
verified | The session verification rules were satisfied. |
failed | The session reached its maximum allowed attempts without verification. |
expired | The session expired before verification. |
The REST schema currently lists pending, verified, and failed; expiration is also represented by the backend and
app.
Connections
Section titled “Connections”Each SSH connection records:
- connection ID;
- IP address;
- SSH client version;
- keys matched during the connection;
- creation time.
Verified keys
Section titled “Verified keys”Each key includes a verified_at timestamp when it has been verified. For match_all_keys sessions, the session is only
successful after all configured keys have been verified according to the session rules.
Failed and multi-connection sessions
Section titled “Failed and multi-connection sessions”max_attempts controls how many connection attempts are allowed before the session fails. The default is 1.
When multi_connection is enabled, SSHVerify keeps accepting connections after a successful verification. Complete the
session manually when you no longer want to accept more connections:
curl -X POST https://sshverify.com/api/v1/ssh/verify/sessions/<session-id>/complete/ \ -H "x-api-key: <api-key>"