How to Configure Make SSH Approval

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up a make ssh approval flow by routing server requests through an automated review step. After a peer approves the request, your automation issues an OpenSSH certificate or runs the remote task. Teams often build this flow using visual workflows that pause until a manager clicks approve. When teams skip this step and share static keys, one broad role can harm every server. How a make ssh approval workflow operates A make ssh approval setup connects a trigger, a human review step, and

Approval Chains & Escalation + SSH Access Management: the complete guide

Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.

Free white paper. No spam. Unsubscribe anytime.

You set up a make ssh approval flow by routing server requests through an automated review step. After a peer approves the request, your automation issues an OpenSSH certificate or runs the remote task. Teams often build this flow using visual workflows that pause until a manager clicks approve. When teams skip this step and share static keys, one broad role can harm every server.

How a make ssh approval workflow operates

A make ssh approval setup connects a trigger, a human review step, and a server action. First, an engineer submits a request through a form or a chat message. The workflow catches this event and sends a message to a team lead. The workflow then waits for a response before it moves to the next step.

If the lead denies the request, the automation stops and logs the refusal. If the lead approves it, the workflow moves to the server step. Many teams use OpenSSH certificates here instead of static public keys. In OpenSSH, a Certification Authority key signs a user public key to create a certificate.

This certificate holds a public key, identity info, user or host names, and specific options. OpenSSH certificates use a much simpler format than X.509 certificates. When you sign a key, you set a key identity and list allowed user names. You also set a time window so the signed certificate expires on schedule.

What native setup solves and what it misses

Putting a human approval step in front of SSH solves the problem of standing keys. Engineers do not keep permanent keys on their laptops that work at any hour. Every login or remote job leaves a record of who asked and who agreed. Using a signed user certificate also avoids copying public keys to every remote host.

Still, a basic workflow and a signed certificate only decide who can log in. Once the session starts, the native setup does not inspect individual commands in flight. A user with a valid certificate for a shared account can run any shell command. They can read private files, change system settings, or delete data without further checks.

Approval Chains & Escalation + SSH Access Management: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Also, if your automation tool holds a static private key to run tasks, risk remains high. Anyone who can edit the workflow can run arbitrary commands using that stored key. Also, standard shell logs do not mask sensitive data returned in command output. If a command prints emails, phone numbers, card numbers, or national IDs, raw text appears.

Closing the gap on command level control

To reduce risk inside the session, teams must look beyond initial login checks. You need controls that check each command before it runs on the target machine. Instead of approving a whole shell session, reviewers should approve specific actions or scripts. You also need a way to rewrite sensitive fields like card numbers in command results.

When you separate the approval logic from raw server keys, engineers do not hold secrets. The focus shifts from guarding the network door to governing what happens inside the session. This keeps production hosts safe while letting teams fix urgent bugs on time.

Inspect one-shot SSH commands and file tasks

SSH certificates and host rules decide who is allowed on a machine. Setup alone does not check single commands or block sftp reads on sensitive paths. By design, hoop.dev runs an open-source SSH listener on the host where people and agents keep their normal ssh, sftp, and scp tools.

First, hoop.dev guardrails check one-shot commands and file paths before they run. Next, hoop.dev data masking masks matched values in file downloads. The audit trail logs the certificate principal, requested action, and verdict without storing session content. Interactive shells carry no guardrails and can be turned off when every action must be checked. Explore the code on GitHub.

Frequently asked questions

What is the difference between an SSH key and an OpenSSH certificate?

A standard SSH key is a static pair of public and private files. An OpenSSH certificate is a public key signed by a Certification Authority key. It includes an identity, allowed user names, and a set time window.

Does an approval workflow stop bad commands after login?

No, a basic approval workflow only gates the start of a session or task. Once a user logs into a shell, the Linux user permissions control what runs. Without command level checks, the user can run any command that role allows.

Where should teams store keys used by automation workflows?

Teams should never paste raw private keys into plain text workflow fields. Store keys in a dedicated secret store and limit which workflows can use them. Better yet, remove static keys and issue short-lived user certificates for each approved task.

Save the open-source gateway.

hoop is MIT-licensed infrastructure for controlling how AI agents reach production data. Star hoophq/hoop so you can inspect it, deploy it, or share it when your team starts governing agent access.