OpenAI API makes mTLS and X.509 workload identity generally available

OpenAI has made mutual TLS (mTLS) and X.509 workload identity federation generally available for the OpenAI API. The release gives organizations certificate-based controls for API requests and a way for trusted workloads to exchange a certificate identity for a short-lived OpenAI access token.

mTLS verifies the calling workload

With mTLS enabled, an API request must present an accepted client certificate in addition to its normal bearer credential. Organizations can upload and activate trust anchors at the organization or project level, then optionally constrain accepted client certificates with a CEL filter.

Activation changes request behavior, so OpenAI recommends testing with a non-critical project before expanding a certificate policy. Teams also need a certificate rotation and recovery plan: OpenAI’s guide says it does not retrieve missing intermediates from certificate URLs and does not perform CRL or OCSP checks.

X.509 federation replaces the long-lived API key

X.509 workload identity federation lets a workload present its TLS client certificate to OpenAI’s token endpoint and receive a short-lived bearer token. The certificate remains part of later API requests; the flow replaces the API key, not the client certificate.

An organization creates an X.509 Workload Identity Provider, maps a derived certificate identity to a project service account, and grants that service account only the permissions the workload needs. OpenAI says Codex does not support X.509 federation; Codex users should use the OIDC or SPIFFE JWT-SVID path described in the Codex workload-identity guidance.

What to review before rollout

Keep private keys, certificate contents, and access tokens outside source control and logs. Test direct and chained certificate validation, provider mappings, certificate deactivation, token renewal, and failure behavior before enabling the policy for production traffic.

The practical distinction is straightforward: mTLS adds certificate verification to API authorization, while X.509 federation uses that verified certificate identity to issue short-lived access. Teams can adopt either control independently, or combine them for workloads that need both certificate-level trust and keyless credential rotation.

Sources

• OpenAI — “Release Notes” (August 29, 2026): https://openai.com/products/release-notes/
• OpenAI Developers — “Mutual TLS”: https://developers.openai.com/api/docs/guides/mutual-tls
• OpenAI Developers — “Configure workload identity federation with X.509 certificates”: https://developers.openai.com/api/docs/guides/workload-identity-federation/x509
• OpenAI Developers — “Workload identity federation”: https://developers.openai.com/api/docs/guides/workload-identity-federation