@@PRODUCT@@

Opening and closing support access

Support access is time-boxed SSH access for the support agent on one or more servers. You open it from the panel, confirm with your passkey, and the access closes by itself on every server at its end time, even when the panel or the network

Written for: Administrator

Support access is time-boxed SSH access for the support agent on one or more servers. You open it from the panel, confirm with your passkey, and the access closes by itself on every server at its end time, even when the panel or the network is gone at that moment. Every platform administrator is told when it opens, is extended, closes or expires.

Only platform administrators see the actions, the overview and the settings.

Where you start

One dialog, from five places:

  • One server: the Server ▾ menu on the server page, Open support access.
  • A server with its related servers: the same menu, Support access with related servers. The list then also holds the servers that share customers with this one (the database server of a website here, the web server of a database here).
  • Several servers: tick them in the server list and choose Open support access in the bar that appears.
  • A customer account or a domain: the Account ▾ menu on the account page, or the button in the domain panel. The list holds every server the services of that account or domain point at (web, database, mail, DNS).
  • A group: the row actions in Groups.

The dialog shows the resolved server list before you confirm, with address, SSH port and roles. Above five servers the mass-operation guard reports it to every administrator; it does not block.

What you choose

  • Level: Investigate is read-only (logs, status, versions, settings without secrets) as its own user without root. Full is root. Full on the panel host or the build server is refused on that server with the reason; choose Investigate there.
  • Duration: 30 minutes, 2 hours (default), 4 hours or 8 hours. Extending adds at most 8 hours each time.
  • Reason (required) and a ticket reference. Both go into the audit log and into the alert the administrators get.
  • Agent: which of the configured agents may come in (see below).

Confirming with your passkey

Opening, extending and the agent settings each ask for a fresh passkey confirmation that belongs to exactly that request: the servers, the level and the duration are part of the challenge your passkey signs. An earlier confirmation from the last ten minutes does not count, and a code from an app or a password opens nothing. Without a passkey on this panel the action is disabled with an explanation; register one under My account first.

Revoking asks for no confirmation: making things safer must be easy.

After opening

Per server you see open, failed (with the reason) or closed. Access that failed on one server stays open where it succeeded; Retry failed servers tries again, Revoke all closes everything.

The hand-over block is shown once: the grant number, the level, the servers (name, address, SSH port, roles) and the end time. Copy it and paste it into the conversation with the agent. It carries no key or password: the agent has its own key.

The panel also writes a manifest of the grant and a panel view (alerts, customer bindings, recent audit rows, related servers) onto every server and refreshes it every few minutes; corectl support brief on the server shows it to the agent.

The Support access overview

Under Fleet › Support access: the active grants with the time left, Extend (passkey), Revoke of the whole grant or of one server, and the history. Anybody signed in with scope on an affected server sees Support access active until … at the top; customers see nothing.

After every revoke and every expiry the panel verifies per server that everything is gone: the key file, the firewall opening, the timer, live sessions, and whether root's keys, the users and the sshd settings are still what they were before the grant. When something is off, the server shows not closed cleanly and every administrator gets an alert.

A server that cannot be reached at revoke shows close not confirmed; the panel retries and reports it, and the server closes itself at the end time regardless.

Reviewing afterwards

Every grant has Recordings and changes. Per server you see the agent's sessions, the command list and the change report:

  • Play shows an interactive session as it was on the screen, or for a single command its input, output and exit code. Because a recording may show passwords or customer data, the panel first asks for a fresh confirmation.
  • The change report (with full rights) shows in red files edited by hand that CoreCP manages — the next reconcile puts them back —, in amber changes outside CoreCP that stay, what went through corectl, and the packages and services. A report that does not match the snapshot the panel keeps itself is marked Forged.
  • Put back restores one file to how it was when the access began. If that fails, the file stays as it is and you see why.
  • A session marked Recording missing did not (fully) reach the panel; every administrator is alerted.

After 90 days the recordings, command list, reports and snapshot are deleted, in the panel and on the servers. The grant stays in the history, marked Deleted after 90 days.

Looking on the server itself

What the panel shows can be read on the server as root:

corectl support status        # the grant, its end time and the three closers
corectl support verify        # what is left after a close, and the digests

Access opened on the server itself

Whoever has root on a server can run corectl support enable there. That grant appears in this overview within a minute, marked on the server itself, and every administrator gets an alert.

Support agents

At the bottom of the overview are the agents: per agent a name, the public key(s) (ed25519, or RSA of at least 3072 bits) and the address or addresses it connects from. Saving asks for your passkey and distributes the settings to every server; a weak key is refused by the servers and nothing is saved then.