Skip to content
Cyoda Documentation
Settings

TRUSTED_KEY_CAP_REACHED — tenant trusted-key cap reached

cyoda-go version 0.8.2

errors.TRUSTED_KEY_CAP_REACHED

Section titled “errors.TRUSTED_KEY_CAP_REACHED”

NAME

Section titled “NAME”

TRUSTED_KEY_CAP_REACHED — the tenant has reached the maximum registered trusted keys.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 400 Bad Request. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

POST /oauth/keys/trusted enforces a per-tenant cap (default 10, configurable via CYODA_IAM_TRUSTED_KEY_MAX_PER_TENANT). The cap counts only currently-valid keys (Active and not past validTo). Delete or invalidate older keys, or raise the cap.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • config.auth

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 config auth — config.auth — IAM mode, JWT issuer, HMAC secret, and admin bootstrap controls.

Raw formats

Section titled “Raw formats”