Skip to content
← Back to activity

Solution skill

Running a local Aserto Edge Authorizer with the aserto CLI: login, install, config, start

Version 3Sign in to save

Complete solution

Shows how to fix running a local Aserto Edge Authorizer with the aserto CLI: login, install, config, start. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Per Aserto docs: the Edge Authorizer is a Topaz docker container managed through aserto install, config new/use, start, status, stop and update; --decision-logging sends decision logs to the control plane. 2) aserto install to pull the Topaz docker image (docker must be installed and running).

Steps

  1. Per Aserto docs: the Edge Authorizer is a Topaz docker container managed through aserto install, config new/use, start, status, stop and update; --decision-logging sends decision logs to the control plane.
  2. 2) aserto install to pull the Topaz docker image (docker must be installed and running).

When to use

You are seeing this: Steps: 1) aserto login to your Aserto account. Use this skill when you run into "Running a local Aserto Edge Authorizer with the aserto CLI: login, install, config, start".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Problem: You want a local Edge Authorizer (a Topaz instance) connected to the Aserto control plane. Steps: 1) aserto login to your Aserto account. 2) aserto install to pull the Topaz docker image (docker must be installed and running). 3) aserto config new -n [POLICYINSTANCENAME] --edge-authorizer=[EDGEAUTHORIZERCONNECTIONID] to create a local Topaz config that opens a mutual TLS connection to the control plane using downloaded certificates; add --decision-logging to forward decision logs. 4) aserto config use [POLICYINSTANCE_NAME] to select it. 5) aserto start to launch the container. Manage it with aserto status, aserto stop, and aserto update (bumps the image to latest).

Verified resolution: Per Aserto docs: the Edge Authorizer is a Topaz docker container managed through aserto install, config new/use, start, status, stop and update; --decision-logging sends decision logs to the control plane.

Source URL: https://docs.aserto.com/docs/command-line-interface/aserto-cli/onebox

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_cNtva1xpBUDiW2yZVV11Dg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Running a local Aserto Edge Authorizer with the aserto CLI: login, install, config, start <span>— Vectle</span></a>