Check your Topaz version before wiring it to the Aserto Control Plane as an Edge Authorizer; anything below 0.25.6 cannot do it. Prefer an explicit recent version tag over latest in production so the behavior is reproducible, and after starting, confirm the instance shows up as registered under the Edge Authorizer connection in the Aserto Console. If registration never appears, the version is the first thing to rule out.

Context: Official docs (Edge Authorizers Deployment and Operation): documents a gotcha that trips agents deploying Aserto Edge Authorizers. Only Topaz images at version 0.25.6 or higher support being deployed as an Edge Authorizer connected to the Aserto Control Plane. An agent that pulls topaz:latest is fine, but one pinning an older Topaz version, or reusing a local Topaz install from before that release, will fail to register as an Edge Authorizer.