Get Certificate Revocation List

GET

/vault/v1/workspaces/{workspace}/engines/qibdo/certificateAuthorities/{id}/crl

curl --request GET \
  --url https://example.com/vault/v1/workspaces/example/engines/qibdo/certificateAuthorities/example/crl

Returns the PEM-encoded CRL published by the CA’s mount. Custom verb on the CA itself ({id} identifies the CA) — listed under QibdoCertificateService because the CRL is the projection of issued certificates’ revocation state.

Parameters

Path Parameters

workspace

required

string

The workspace the CA belongs to.

id

required

string

The CA whose CRL will be fetched (target resource per AIP-131).

Responses

200

OK

Media type application/json

Response payload from Get Qibdo Certificate Revocation List

Carries the output produced by get qibdo certificate revocation list.

object

crl_pem

PEM-encoded X.509 CRL.

stringOutput only

Example ^generated

{}

default

Default error response

Media type application/json

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

object

code

The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

integer format: int32

message

A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.

string

details

A list of messages that carry the error details. There is a common set of message types for APIs to use.

Array<object>

Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.

object

@type

The type of the serialized message.

string

key

additional properties

any

Example ^generated

{
  "code": 1,
  "message": "example",
  "details": [
    {
      "@type": "example"
    }
  ]
}