Passport app is now generally available

passport

Passport is now generally available. With Passport, you can give your team access to the authenticated APIs they need without handing out the real secrets behind them. Every request is resolved inside your own cloud.

The Passport Proxy, app, and CLI work together to keep secrets secure. The Proxy resolves secret references before forwarding each request. The app issues those references and manages access. The CLI authenticates your machine and either sends requests directly or routes existing tools like curl through the proxy.

Group related APIs together using namespaces, with each namespace containing resources that represent the APIs and their associated secrets. You can add resources from a variety of sources like OpenAPI specifications, exported proxy traffic (OTEL), or Postman collections. Map secret references to your own secret store — HashiCorp Vault, AWS Secrets Manager, or Google Cloud Secret Manager — and control access through API requests that Admins approve or deny.

Learn how to get started with Passport.

Passport CLI is now generally available

passport-cli

The Passport CLI is now generally available, with full production support. Run passport login to authenticate, then passport setup to connect your machine to the Passport Proxy. Use passport request to forward HTTPS requests through the proxy using secret references instead of real secrets. A local daemon transparently routes requests from external clients like curl, scripts, and SDKs. Run passport whoami at any time to check your identity and API access. You can also use passport logs to get visibility into the activity of the local daemon and the commands you run, which is useful for troubleshooting.

Learn how to install the latest version of the Passport CLI.