Skip to main content

Upstream GCP Self-Signed JWT Policy

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.


"name": "my-upstream-gcp-jwt-inbound-policy",
"policyType": "upstream-gcp-jwt-inbound",
"handler": {
"export": "UpstreamGcpJwtInboundPolicy",
"module": "$import(@zuplo/runtime)",
"options": {
"audience": "",
"serviceAccountJson": "$env(SERVICE_ACCOUNT_JSON)"
  • name the name of your policy instance. This is used as a reference in your routes.
  • policyType the identifier of the policy. This is used by the Zuplo UI. Value should be upstream-gcp-jwt-inbound.
  • handler/export The name of the exported type. Value should be UpstreamGcpJwtInboundPolicy.
  • handler/module the module containing the policy. Value should be $import(@zuplo/runtime).
  • handler/options The options for this policy:
    • audience
      [object Object]
    • serviceAccountJson
      [object Object]

Read more about how policies work