Connect a container registry
Connect a registry and verify the credential. Strix encrypts the credential and never returns it. Session callers must hold the admin role. Container scanning requires the Enterprise plan.
Authorizations
API token obtained from the Tokens endpoint or CLI device login. Include as Authorization: Bearer <token>. Requests made with a managed CLI session also include X-Strix-Workspace: <organization_id> to pin a process to the workspace it started in; recovery endpoints report the current workspace after a concurrent switch.
Body
Registry provider. dockerhub for Docker Hub, ghcr for GitHub Container Registry, generic for any other OCI registry.
ghcr, dockerhub, ecr, generic How Strix authenticates. none for public registries, basic_token for a username and token. For GitHub Container Registry, use a personal access token with the read:packages scope.
basic_token, aws_assume_role, none Registry host for generic registries, for example registry.example.com. Optional for ghcr and dockerhub.
Display name for the connection. Defaults to the registry host.
Username for basic_token authentication.
Token or password for basic_token authentication. Strix encrypts the value and never returns it.
Response
The connected registry.
A connected container registry. The response never contains the stored credential.