ADR 0028: A SPIFFE JWT-SVID binds like an OIDC token

Decision

A JWT-SVID is an identity token for rung 2, judged by the four rules of ADRs 0023 and 0026. tik bridge workload --token-file binds one the way it binds a GitHub Actions token. Four differences in the format are handled where they arise:

Context

SPIFFE gives a workload a short-lived identity with no long-lived secret, which is the property rung 2 for machines exists for. SPIRE’s server configuration reference gives jwt_key_type a default of ec-p256, and a P-256 key signs a JWS as ES256 (RFC 7518). tik verified EdDSA and RS256 only, and required both iss and, with several keys pinned, kid.

X509-SVIDs are out of scope. Checking one means RFC 5280 certificate path validation, and CertPathValidator cannot be resolved under babashka, which every tik runtime must support. PS256 is out for the same kind of reason: RSASSA-PSS needs PSSParameterSpec, which babashka does not expose. The JWT-SVID format allows RS, ES and PS algorithms, so an SVID signed with PS256 is reported as an unsupported alg.

Consequences

see history · edit this page