This page defines the canonical SecretRef credential surface: which credential fields accept a SecretRef (env/file/exec/store-backed reference) instead of a raw secret value.

Scope:

The lists below are generated from the source target registry and checked against docs/reference/secretref-user-supplied-credentials-matrix.json in CI; do not hand-edit entries.

Source generation fails if a present channel secret-contract artifact cannot load, rather than publishing an incomplete list. A plugin without that optional artifact contributes no channel targets. This generation check does not change runtime SecretRef owner-isolation behavior.

Supported credentials

apus.json targets (secrets configure + secrets apply + secrets audit)

agents

channels

cron

gateway

memory

models

plugins

skills

talk

tts

SQLite auth-profile targets (secrets configure + secrets apply + secrets audit)

Node-host connection targets

These fields live in the node host's canonical nodeHost.config SQLite machine-state value, not apus.json. They accept the same SecretInput forms and resolve through the configured SecretRef providers when the node starts. The conventional CF_ACCESS_CLIENT_ID / CF_ACCESS_CLIENT_SECRET fallback persists env refs for these fields automatically. They are not targets for secrets configure or secrets apply.

Notes:

Unsupported credentials

These credentials are minted, rotated, session-bearing, or OAuth-durable classes that do not fit read-only external SecretRef resolution:

Related