Skip to content
Cyoda Documentation
Settings

KEY_OWNED_BY_DIFFERENT_TENANT — trusted-key collision with another tenant

cyoda-go version 0.8.2

errors.KEY_OWNED_BY_DIFFERENT_TENANT

Section titled “errors.KEY_OWNED_BY_DIFFERENT_TENANT”

NAME

Section titled “NAME”

KEY_OWNED_BY_DIFFERENT_TENANT — the requested keyId is already registered by another tenant.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 409 Conflict. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

Trusted keys are tenant-scoped. When POST /oauth/keys/trusted is called with a keyId that already belongs to a different tenant, the request is rejected with 409. Pick a fresh keyId (the caller cannot see or affect the other tenant’s keys).

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • errors.TRUSTED_KEY_NOT_FOUND

See also

Section titled “See also”
  • cyoda help errors — Every error response from the Cyoda REST API carries a structured errorCode in the properties object. Multiple codes may share the same HTTP status. Programmatic handling keys on errorCode, not HTTP status.
  • cyoda help errors TRUSTED_KEY_NOT_FOUND — Returned by trusted-key admin endpoints when the supplied KID does not match any registered key:

Raw formats

Section titled “Raw formats”