ID Wispera can programmatically create API keys at vendor APIs and wrap them as governed
passports in a single operation, ensuring every provisioned credential is tracked with
audit trail and policy enforcement.
The provisioning module provides a unified interface: provision at the vendor, create a
passport in the vault, then manage the lifecycle (rotate, revoke, list) through the same
API.
Provisioning requires admin-level credentials for the target provider. Use
idw auth bootstrap to store them as encrypted admin passports in the vault with
privilege visa type — then provisionAndCreatePassport() resolves auth automatically.
See the Authentication guide for details.
Rotation creates a new key and returns the old key ID for later revocation.
After rotation, revoke the old key at the source to ensure it can no longer be used.
The two-step pattern (rotate then revoke) avoids downtime during the switchover window.
Never hard-code admin credentials in source code. Run idw auth bootstrap to store
them as privilege passports in the vault. When the auth parameter is omitted,
provisionAndCreatePassport() resolves admin credentials from the vault automatically.
The idw provision command provides CLI access to the provisioning module, enabling you to create, rotate, and list scoped credentials directly from the terminal.
Provision a new scoped credential at the specified provider
idw provision rotate <provider> --passport <id>
Rotate an existing provisioned credential
idw provision list <provider>
List all provisioned credentials at the specified provider
Prerequisites: Run idw auth bootstrap <provider> first to store your admin
credentials in the vault. The idw provision command requires the latest version of the CLI.
Use provisionAndCreatePassport for the unified workflow. This ensures every provisioned key immediately gets a passport with audit trail and policy enforcement.
Store admin keys in the vault too. Run idw auth bootstrap to store provider admin credentials as privilege passports. Provisioning then resolves auth automatically.
Rotate regularly. Use rotateCredential on a schedule. The function handles create-before-revoke to avoid downtime.
Set expiry where supported. For AWS STS credentials, use expiresIn to create short-lived tokens. For Azure Entra, set secretExpiryDays to limit secret lifetime.
Tag provisioned passports. Use tags like provisioned, production, or the provider name to make it easy to find and audit provisioned credentials.
Prefer scoped credentials. Use project-scoped keys (OpenAI), STS temporary credentials (AWS), API restrictions (Google Cloud), and fine-grained permissions (GitHub) to follow the principle of least privilege.
GitHub tokens are short-lived. Installation access tokens expire in 1 hour. Use rotateCredential to refresh them before expiry.
Anthropic is management-only. Create keys manually at console.anthropic.com, then use ID Wispera to list, track, and disable them.