Stay organized with collections
Save and categorize content based on your preferences.
Using gRPC with Certificate Authority Service
If you are using manually created gRPC
libraries to make API calls to Certificate Authority Service, you must add x-goog-request-params: '<request-field>:<resource-name>'
as a header. The proper use of x-goog-request-params
ensures that the request is routed to the appropriate region for your CA Service resources.
Given below are a few examples of methods with their respective request field and sample header.
For the complete list of RPC methods and their respective request fields, see Package google.cloud.security.privateca.v1beta1
.
What's next
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License
, and code samples are licensed under the Apache 2.0 License
. For details, see the Google Developers Site Policies
. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-09-04 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[[["\u003cp\u003eWhen using manually created gRPC libraries to call the Certificate Authority Service API, you must include the \u003ccode\u003ex-goog-request-params\u003c/code\u003e header.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ex-goog-request-params\u003c/code\u003e header, in the format of \u003ccode\u003e<request-field>:<resource-name>\u003c/code\u003e, is necessary to ensure requests are routed to the correct region for your CA Service resources.\u003c/p\u003e\n"],["\u003cp\u003eSpecific request fields vary by method, for example, \u003ccode\u003eCreateCertificateAuthority\u003c/code\u003e uses the 'parent' field, while \u003ccode\u003eGetCertificateAuthority\u003c/code\u003e uses the 'name' field.\u003c/p\u003e\n"],["\u003cp\u003eFor the full list of RPC methods and their corresponding request fields, consult the \u003ccode\u003egoogle.cloud.security.privateca.v1beta1\u003c/code\u003e package documentation.\u003c/p\u003e\n"]]],[],null,["# Using gRPC with Certificate Authority Service\n=============================================\n\nIf you are using manually created [gRPC](https://grpc.io/) libraries to make API calls to Certificate Authority Service, you must add `x-goog-request-params: '\u003crequest-field\u003e:\u003cresource-name\u003e'` as a header. The proper use of `x-goog-request-params` ensures that the request is routed to the appropriate region for your CA Service resources.\n\nGiven below are a few examples of methods with their respective request field and sample header.\n\n\u003cbr /\u003e\n\nFor the complete list of RPC methods and their respective request fields, see [Package google.cloud.security.privateca.v1beta1](/certificate-authority-service/docs/reference/rpc/google.cloud.security.privateca.v1beta1).\n\nWhat's next\n-----------\n\n- [Cloud APIs: gRPC APIs](/apis/docs/client-libraries-explained#grpc_apis)\n- [RPC Reference](/certificate-authority-service/docs/reference/rpc)"]]
