Manage OIDC trusts — how CI authenticates as a service account
An OIDC trust lets tokens from an external issuer (e.g. GitHub Actions) authenticate as a service account: tokens whose issuer and subject exactly match the trust are exchanged for short-lived Synthetiq tokens. No credentials are stored anywhere.All trust commands require the org:trusts scope on your organization role.
Optional JWK Set file pinning the issuer’s signing keys — verification then never contacts the issuer. Omit to resolve keys via OIDC discovery (issuer must be reachable from the Synthetiq platform; rotation is automatic)
ID SERVICE ACCOUNT ISSUER SUBJECT3c1f8a44-9b2d-4e07-8f1a-6d5c2e9b7a01 infra-apply token.actions.githubusercontent.com repo:acme/infra:ref:refs/heads/main