#Credential

Credential features let Sandbox0 authenticate outbound traffic without placing raw secret material inside the sandbox process.

The Three Objects#

ObjectWhat it storesWhere it lives
credential sourceSecret material such as tokens, headers, client certificates, or username/password pairsCredential source API
credential bindingA stable local ref plus projection rules that map a source into a runtime auth shapenetwork.credentialBindings
credential ruleDestination match rules that decide when outbound auth should be injectednetwork.egress.credentialRules

These objects work together: create a source, expose it through a stable binding ref, and then match outbound traffic with credentialRules that reference that ref. Keep traffic control separate with trafficRules.

ℹ

trafficRules and credentialRules are orthogonal. trafficRules decide whether traffic is allowed. credentialRules decide whether matching traffic gets outbound authentication.

Where You Configure It#

credentialBindings now live under the same network object everywhere:

  • Template defaults: spec.network
  • Claim-time config: config.network
  • Runtime update: PUT /api/v1/sandboxes/{id}/network

That public shape is SandboxNetworkPolicy in all three places.

Supported Projections#

Projection typeTypical use
http_headersInject HTTP or gRPC headers such as Authorization
tls_client_certificatePresent a client certificate during TLS terminate-reoriginate flows
username_passwordProvide username/password material for protocols such as SOCKS5 or MQTT

Supported Source Types#

Resolver kindPurpose
static_headersStore named header values or tokens
static_tls_client_certificateStore certificate PEM, private key PEM, and optional CA PEM
static_username_passwordStore a username/password pair

Next Steps#

Sources

Create and manage reusable credential sources

Egress Auth

Bind sources and inject outbound auth for matching destinations

Sandbox Network

Control traffic allow and deny behavior with trafficRules