OIDC tokens / Short lived identity
Trade a secret for identity.
When enabled, a trusted job can request a short-lived signed JWT and exchange it with a cloud provider for that provider's credential. The private signing key stays on the worker host.
Worker prerequisites
- Configure an HTTPS issuer URL with no query, fragment, or trailing slash using
--oidc-issuer. - Keep the issuer signing keys in the worker key directory and protect them as host credentials.
- Start the worker with
--github-repository OWNER/NAMEand--network bridgewhen the job needs to reach the cloud provider. - Grant
id-token: writein the workflow's permissions. This is the only write permission accepted by the token contract. - For same-repository pull requests, also opt in with
--oidc-pull-request.
Publish public verification keys
Publish the public OpenID configuration and JWKS for the issuer. The command writes only public key members from the OIDC key directory:
python -m execution_core --state STATE oidc publish --issuer ISSUER --out OUTPUTCheck oidc publish --help for the optional --key-dir KEY_DIR setting. The public files must be served from the configured issuer URL.
Trust rules
- OIDC is off unless the worker has
--oidc-issuer. - Forks never receive a token, even if a poll override admits a run.
- Runs admitted with
--allow-untrustedor--allow-pr-workflowcannot mint tokens. - Same-repository pull requests require
--oidc-pull-request. - Tokens expire five minutes after mint and are bound to one audience.
Plan cloud trust policies around issuer, audience, and subject claims. A same-repository pull request has a pull-request subject; a branch-pinned cloud policy will not accept it. Read the v0.1.10 OIDC design before configuring production trust.