CX-10

CredentialBinding

40 typed shared schemas, source/config schemas, examples, required fields, old/new compatibility, dependent flows and approval validity.

Acceptance · Changing meaning, required fields or approved mappings invalidates affected approval/test evidence as policy requires. Operations listSourceContracts, validateContract

Synthetic connector workspace. Every profile here is a proposed target. Nothing on this screen is a live, qualified or certified adapter, no payload is a captured vendor wire message, and the simulation engine has no code path to a real endpoint.

bundle status: proposed; not signed V9 canonical schemas← all schemas

Fields

Field	Type	Required	Permitted values / reference
bindingId	string	required	—
scope	ref → Scope	required	—
mechanism	string	required	oauth2 · api_key · mtls · username_password · windows_identity · ssh_key · cloud_identity · network_boundary
secretProviderRef	string	required	—
principalRef	string	required	—
permittedResources	array	required	—
expiresAt	any	required	—

References these contracts

Scope

Depended on by

No other contract depends on this one.

Synthetic example

{
  "bindingId": "secret-binding:fixture-only",
  "scope": {
    "tenantId": "fixture-tenant-a",
    "siteId": "fixture-plant-01",
    "environment": "test"
  },
  "mechanism": "mtls",
  "secretProviderRef": "vault-binding:fixture",
  "principalRef": "identity:fixture-worker",
  "permittedResources": [
    "fixture:source-01"
  ],
  "expiresAt": null
}