Skip to content
Cyoda Documentation
Settings

KEYPAIR_NOT_FOUND — signing keypair not found

cyoda-go version 0.8.2

errors.KEYPAIR_NOT_FOUND

Section titled “errors.KEYPAIR_NOT_FOUND”

NAME

Section titled “NAME”

KEYPAIR_NOT_FOUND — the requested JWT signing keypair is not present.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 404 Not Found. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

Returned by:

  • DELETE /oauth/keys/keypair/{keyId} — keyId not present.
  • POST /oauth/keys/keypair/{keyId}/invalidate — keyId not present.
  • POST /oauth/keys/keypair/{keyId}/reactivate — keyId not present.
  • GET /oauth/keys/keypair/current?audience=X — no active key for audience X.

Verify the keyId, or check the bootstrap-key audience configuration via CYODA_JWT_BOOTSTRAP_AUDIENCE.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • errors.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 NOT_FOUND — Returned by administrative endpoints (key pair lifecycle, trusted-key lifecycle) when the supplied identifier does not match any registered resource. The submitted identifier is never echoed in the response body — only a generic descriptor — so attackers cannot use the response as a reflection oracle. The identifier is logged server-side at INFO for operator correlation.

Raw formats

Section titled “Raw formats”