Method: projects.locations.certificateAuthorities.activate

Activate a CertificateAuthority that is in state PENDING_ACTIVATION and is of type SUBORDINATE. After the parent Certificate Authority signs a certificate signing request from certificateAuthorities.fetch, this method can complete the activation process.

HTTP request


The URL uses gRPC Transcoding syntax.

Path parameters



Required. The resource name for this CertificateAuthority in the format projects/*/locations/*/certificateAuthorities/*.

Authorization requires the following IAM permission on the specified resource name:

  • privateca.certificateAuthorities.update

Request body

The request body contains data with the following structure:

JSON representation
  "pemCaCertificate": string,
  "subordinateConfig": {
    object (SubordinateConfig)
  "requestId": string


Required. The signed CA certificate issued from FetchCertificateAuthorityCsrResponse.pem_csr.


object (SubordinateConfig)

Required. Must include information about the issuer of 'pemCaCertificate', and any further issuers until the self-signed CA.



Optional. An ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes since the first request.

For example, consider a situation where you make an initial request and t he request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.

The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).

Response body

If successful, the response body contains an instance of Operation.

Authorization Scopes

Requires the following OAuth scope:


For more information, see the Authentication Overview.