The TigerTrust Agent is the only thing you install on a host to bring it under CLM management. It never listens on any port; it dials out to the Collector on 443 and pulls work.
This page mirrors the Agent Setup wizard in the dashboard (/clm/agent-setup). Copy commands from either side — they’re identical.

Prerequisites

RequirementValue
Agent API KeyCreate one in Settings → API Keys → New key with type agent. Shown once.
Collector URLhttps://collector.tigertrust.io (or your self-hosted Collector)
Supported OSDebian/Ubuntu · RHEL/CentOS · Windows Server 2016+ · macOS 12+
Userroot or a service account that owns the paths you plan to manage

Quick install (one script, any Linux)

1

Run the installer

curl -fsSL https://releases.tigertrust.io/tigertrust-agent/scripts/install.sh | sudo bash -s -- \
  --collector-url https://collector.tigertrust.io \
  --api-key YOUR_API_KEY
The script detects your distro, adds the right package repo, installs tigertrust-agent, writes /etc/tigertrust/config.yaml, and enables the systemd service.
2

Verify

sudo systemctl status tigertrust-agent
The host appears in Infrastructure → Agents within 30 seconds of first heartbeat.

Installation methods

Choose the flow that matches your platform. All flows land on the same tigertrust-agent binary and /etc/tigertrust/config.yaml.
The install.sh script auto-detects apt (Debian/Ubuntu) vs dnf/yum (RHEL/Fedora/CentOS/Amazon Linux) and picks the right package source. It also detects amd64 vs arm64 and pulls the correct binary. Use this path for every Linux target — bare metal, VM, container-host, edge box.
1

Run the installer with your credentials

curl -fsSL https://releases.tigertrust.io/tigertrust-agent/scripts/install.sh | sudo bash -s -- \
  --collector-url https://collector.tigertrust.io \
  --api-key YOUR_API_KEY
Behind the scenes this adds the apt/yum repo, installs the tigertrust-agent package, writes /etc/tigertrust/config.yaml, and runs systemctl enable --now tigertrust-agent.
2

Verify

sudo systemctl status tigertrust-agent
The host appears under Infrastructure → Agents within 30 seconds.
Manual package-manager install (if you want to control the repo yourself):
# Debian / Ubuntu (amd64 or arm64 — package is multi-arch)
curl -fsSL https://releases.tigertrust.io/tigertrust-agent/latest/gpg.key \
  | sudo gpg --dearmor -o /usr/share/keyrings/tigertrust-archive-keyring.gpg
echo "deb [signed-by=/usr/share/keyrings/tigertrust-archive-keyring.gpg] https://releases.tigertrust.io/tigertrust-agent/latest/apt stable main" \
  | sudo tee /etc/apt/sources.list.d/tigertrust.list
sudo apt update && sudo apt install -y tigertrust-agent

# RHEL / Fedora / CentOS / Amazon Linux
sudo tee /etc/yum.repos.d/tigertrust.repo <<'EOF'
[tigertrust]
name=TigerTrust Repository
baseurl=https://releases.tigertrust.io/tigertrust-agent/latest/yum/stable/$basearch
enabled=1
gpgcheck=1
gpgkey=https://releases.tigertrust.io/tigertrust-agent/latest/gpg.key
EOF
sudo yum install -y tigertrust-agent   # or: sudo dnf install -y tigertrust-agent
Then create the directories, drop in a config file (there’s no configure subcommand — the agent reads YAML), and start the service:
sudo mkdir -p /etc/tigertrust /var/lib/tigertrust /var/log/tigertrust
sudo useradd --system --no-create-home --shell /usr/sbin/nologin tigertrust 2>/dev/null || true
sudo chown -R tigertrust:tigertrust /etc/tigertrust /var/lib/tigertrust /var/log/tigertrust

# Copy the example config the package ships and edit collector.base_url + collector.api_key
sudo cp /usr/share/tigertrust-agent/config.example.yaml /etc/tigertrust/config.yaml
sudo vi /etc/tigertrust/config.yaml

sudo systemctl enable --now tigertrust-agent

Verify the install

Check service status

sudo systemctl status tigertrust-agent

Tail agent logs

sudo journalctl -u tigertrust-agent -f
Once connected, the host appears in Infrastructure → Agents within a few seconds and starts discovering certificates automatically.

The install.sh script

The Linux flow above is what the single install.sh runs internally. It’s fetched from https://releases.tigertrust.io/tigertrust-agent/scripts/install.sh and:
  1. Detects the platform (/etc/os-release, uname -m) — supports amd64 (x86_64) and arm64 (aarch64).
  2. Detects the package manager: apt (Debian/Ubuntu) or dnf/yum (RHEL/Fedora/CentOS/Amazon Linux). Errors out on distros without either.
  3. Adds the correct repo (apt sources file or .repo file), imports the GPG key.
  4. Installs the tigertrust-agent package.
  5. Creates the tigertrust service user and chowns /etc/tigertrust, /var/lib/tigertrust (keys/, tpm/), and /var/log/tigertrust to it.
  6. Writes /etc/tigertrust/config.yaml from the flags you passed.
  7. Registers the systemd unit and starts it (only when --collector-url + --api-key were both supplied).
install.sh is Linux-only by design. Windows requires the MSI (different privilege model, different service manager) — use the Windows tab. macOS uses Homebrew (brew install tigertrust/tap/agent).
Supported flags:
--collector-url <url>     (required)
--api-key <key>           (required)
--agent-name <name>       optional; defaults to hostname
--config <path>           optional; use a pre-written config file
--channel <stable|beta>   optional; default: stable
--version <ver>           optional; pin to a specific tarball version

Non-root operation

The agent daemon runs as an unprivileged tigertrust user — never as root. The installer needs root once (to add the repo, install the package, and register the systemd unit), but the running process is dropped into a service account with:
PathOwnerMode
/etc/tigertrust/tigertrust:tigertrust750
/etc/tigertrust/config.yamltigertrust:tigertrust640
/var/lib/tigertrust/tigertrust:tigertrust750
/var/lib/tigertrust/agent-idtigertrust:tigertrust600
/var/lib/tigertrust/keys/tigertrust:tigertrust700
/var/lib/tigertrust/tpm/tigertrust:tigertrust700
/var/log/tigertrust/tigertrust:tigertrust750
The systemd unit hardens this further with NoNewPrivileges=true, ProtectSystem=strict, ProtectHome=true, PrivateTmp=true, and ReadWritePaths=/var/lib/tigertrust /var/log/tigertrust. Custom service user. If you want to bind the daemon to your own user (e.g. run as deploy who already owns the paths you’re deploying certs to), edit the systemd unit’s User= / Group=, chown the paths above to that user, and systemctl daemon-reload && systemctl restart tigertrust-agent. The daemon will honour whatever uid it inherits. Rootless container. For Docker/Kubernetes deployments, run the container as a non-root uid and mount /etc/tigertrust, /var/lib/tigertrust, /var/log/tigertrust volumes owned by that uid. The container image is built with a non-root tigertrust user (uid 1000) by default.

What the installer creates

install.sh creates every directory the agent needs before starting the service, so you don’t hit permission denied on first heartbeat:
  • /var/lib/tigertrust/ — the agent id (agent-id), key material (keys/), and TPM handle cache (tpm/) all land here. Created with mkdir -p and chowned to the service user.
  • /var/log/tigertrust/ — created and chowned.
  • /etc/tigertrust/config.yaml — templated from --collector-url / --api-key / --agent-name. Chmod 640.
  • /etc/systemd/system/tigertrust-agent.service — systemd unit with the non-root hardening flags above.
There is no tigertrust-agent configure command. The agent is configured purely via the YAML at /etc/tigertrust/config.yaml. install.sh writes it for you; if you skip the installer, drop a config.yaml from the example template yourself and restart the service.
If you’re deploying without install.sh (e.g. custom Ansible / Puppet), replicate those four items yourself. Otherwise the agent will fall back to inferring a home directory, and on read-only filesystems it will refuse to persist the agent id — you’ll see a fresh registration on every restart.

Capabilities

Agents advertise what they support. A discovery-only agent claims different capabilities than a data-center agent that also deploys certs. Edit /etc/tigertrust/config.yaml and restart:
agent:
  capabilities:
    - fs-scan
    - cert-renewal
    - csr-generation
    - cert-deploy
    - network-scan
    - ssh-scan
The control plane only schedules tasks the agent claims to support, so a stripped-down IoT agent (discovery + renewal only) can coexist with full-featured hosts in the same workspace.

Agents and Collector

The pull-based architecture, task types, and enrollment flow.

Discovery

What the filesystem, keystore, and network scans actually look at.

Certificate renewal

End-to-end CSR generation and deployment during renewal.

Troubleshooting

Common enrollment and connectivity issues.