Upstream GCP Self-Signed JWT
CAUTION: This policy only works with certain Google APIs. In most cases, the Upstream GCP Service Auth should be used.
This policy adds a JWT token to the headers, ready for us in an outgoing request
when calling a GCP service (e.g. Cloud Endpoints / ESPv2). We recommend reading
the serviceAccountJson from environment variables (so it is not checked in to
source control) using the $env(ENV_VAR) syntax.
Configuration#
{
"name": "my-upstream-gcp-jwt-inbound-policy",
"policyType": "upstream-gcp-jwt-inbound",
"handler": {
"export": "UpstreamGcpJwtInboundPolicy",
"module": "$import(@zuplo/runtime)",
"options": {
"audience": "your_gcp_service.endpoint.com",
"serviceAccountJson": "$env(SERVICE_ACCOUNT_JSON)"
}
}
}Options#
namethe name of your policy instance. This is used as a reference in your routes.policyTypethe identifier of the policy. This is used by the Zuplo UI. Value should beupstream-gcp-jwt-inbound.handler/exportThe name of the exported type. Value should beUpstreamGcpJwtInboundPolicy.handler/modulethe module containing the policy. Value should be$import(@zuplo/runtime).handler/optionsThe options for this policy:audienceThe audience for the minted JWT. Refer to https://cloud.google.com/endpoints/docs/grpc-service-config/reference/rpc/google.api#google.api.AuthRequirement.
serviceAccountJsonThe Google Service Account key in JSON format. Note you can load this from environment variables using the $env(ENV_VAR) syntax.