Configure the Passport Proxy
The Passport Proxy runs in your environment, so you tell it which organization it serves, give it the keys it uses to issue certificates and find credentials, and point it at your secret store and audit destination. This page walks you through finding your organization ID, generating the proxy’s keys, and setting those values in values.yaml. It assumes you’ve completed Get registry access, including exporting the chart’s default values to values.yaml.
Find your organization ID
Your organization ID ties this proxy deployment to your Passport organization. The proxy only issues certificates for the organization you list, and it won’t issue any without one.
To copy your organization ID from the Passport app, do the following:
- In the Passport app, click Org Settings in the header.
- Select Overview.
- Copy the Organization ID.
You’ll use this value as bundle.allowedTeamIds. If you leave it set to the CHANGE-ME placeholder, helm install fails with the error bundle.allowedTeamIds is still set to the placeholder 'CHANGE-ME'.
Generate the proxy keys
The proxy won’t start without the following two private keys, which you generate in your own environment:
- CA key — The proxy uses it to issue certificates to your members’ machines. Members authenticate to the proxy with those certificates.
- Reference key — The proxy uses it to decrypt the information it needs to find the right credential in your secret store when a request uses a secret reference. You register the matching public key in Passport, which uses it to encrypt that information so that only your proxy can read it.
Both must be RSA keys in PEM format. The following commands generate 2048-bit keys. The proxy creates its own CA certificate from the CA key, so you don’t need to create one.
You store the keys in a Kubernetes Secret, and the chart mounts them as files in the proxy. This keeps key material out of values.yaml, so don’t put it there.
-
Generate the two keys, and the public key for the reference key:
The last command writes the reference key’s public half to
reference-public-key.pem. Keep this file, because you enter it when you register the proxy. -
Create a Kubernetes namespace for the proxy, then store the two private keys in a Secret named
passport-keys. A Kubernetes namespace groups resources in your cluster, and it’s separate from a Passport namespace. The Secret must be in the namespace that the proxy is installed into, so create the namespace first. Then return to the directory that contains yourvalues.yaml:
Keep your reference key. If you generate a new one, every secret reference created for the old key stops working, and you must register the proxy again with the new public key.
Set up the management URL
The management URL is the HTTPS address of the proxy’s management endpoint. Your members’ machines call it to get certificates from the proxy when they run passport setup, where they pass it with the --management-url option. You also enter it when you register the proxy. It’s separate from the proxy URL, which is where members send API traffic.
By default, the management endpoint is reachable only inside your cluster, so you expose it at a hostname that your members can reach. The chart does this with a Kubernetes Ingress that exposes only the two routes members need for setup. The rest of the management endpoint stays internal.
To set up the management URL, do the following:
- Choose a hostname for the management endpoint, such as
proxy-mgmt.example.com, and point it at your cluster’s ingress controller. - Store a TLS certificate for that hostname in a Kubernetes TLS Secret. The ingress controller handles TLS, because the management endpoint itself uses plain HTTP.
- Set the
ingressandproxy.managementHostvalues invalues.yaml, as shown in the next section.
Your management URL is then the HTTPS address of that hostname, such as https://proxy-mgmt.example.com.
Configure values.yaml
A values.yaml file holds the settings for a Helm chart. The file you exported earlier contains the chart’s defaults. When you install the proxy, Helm uses your edited copy and falls back to the chart’s defaults for anything you didn’t change. Most of the file is optional tuning, so you only need to edit the values shown in the following example.
The example is an illustration, not a file to copy as is. The hostnames, ingress class, TLS Secret name, load balancer annotation, region, and organization ID are placeholders, so replace them with your own values. The example also uses AWS Secrets Manager as the secret store, so change the vault values to match the store you use. The table after the example explains where each value comes from.
Leave all other values at their defaults.
Next steps
With the keys stored and values.yaml configured, install the Passport Proxy.

