Create a credential binding
A credential binding ties a secret (referenced in your secret manager, never inlined) to an upstream under one of the credential modes. The broker resolves it at the edge — the secret never reaches the agent or audit.
- Validate the binding (mode, secret reference, scope).
- Create it — it enters approval.
- Rotate / disable / revoke over its lifetime as needed.
Create the binding
Section titled “Create the binding”- Open Access → Credential bindings → New.
- Choose the credential mode, select approved targets and active policies, and point at the secret reference.
- For Agent scoped, select one approved agent. The selection becomes the immutable agent subject.
- Confirm every item under Ready for review, then submit the binding.
curl -X POST "$GATEWAY/v1/credential-bindings" \
-H "authorization: Bearer $TOKEN" \
-H "content-type: application/json" \
--data '{
"mode": "service_account",
"server_id": "legal-contract-review",
"secret_ref": "vault://kv/data/mcp/legal-sa"
}'createCredentialBinding in the API reference →gatewayctl validate-credential-binding binding.yaml --format jsonValidate with validate-credential-binding; create/update via the API or `gatewayctl credential-binding update`.
An agent_scoped binding cannot activate until the selected agent is approved
for that environment and credential mode. The detail page shows the expected
agent, identity source, allowed surfaces, and instance requirements. Create a
replacement binding when ownership must move to another agent.
Activation rechecks the selected server or imported API operation and every policy reference. A deleted, unselected, unpublished, inactive, or unapproved reference blocks activation before a runtime projection is created. An imported API source may still be awaiting approval because its approval step verifies the credential binding. The source remains unavailable to runtime traffic until that later approval succeeds.
The detail page reports a credential locator as Reference accepted after its format and lifecycle checks pass. The gateway verifies provider material only when a permitted runtime call resolves the locator. This distinction prevents a typed Vault, AWS, Azure, GCP, or Kubernetes path from appearing as a successful secret-manager lookup before one has occurred.
Rotate, disable, or revoke
Section titled “Rotate, disable, or revoke”- Open the binding under Access → Credential bindings.
- Use Rotate, Disable, or Revoke — each is recorded as an auditable transition.
curl -X POST \
"$GATEWAY/v1/credential-bindings/cb_123/rotate" \
-H "authorization: Bearer $TOKEN"rotateCredentialBinding in the API reference →gatewayctl credential-binding rotate cb_123 --format jsoncredential-binding supports list / get / update / rotate / disable / revoke / status.
Type set in Geist, Source Serif 4, and Departure Mono.