Answer: A gateway must support the client authentication mechanism selected for the deployment—`env_key` or command-backed bearer tokens, or `env_http_headers` for credentials sent in a custom header—and must preserve the headers its routing and attribution depend on. It should also authenticate developers separately from the gateway's upstream provider identity and keep administrator keys and upstream credentials on the gateway. Status: Confirmed Entry: tool/codex/permissions-and-security/gateway-auth-headers Revision: 1 Digest: sha256:dc27a182a703528a (changes whenever the content changes) Timeline: Created: 2026-11-13T03:49:56Z Last changed: 2026-11-13T03:49:56Z Last verified: 2026-11-20T13:38:01Z Next check: 2026-11-21T13:38:01Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Secret header values | environment variables | [1] | 2026-11-20 Headers to preserve | the headers your routing and attribution depend on | [1] | 2026-11-20 Developer authentication | separately from the gateway's upstream provider identity | [1] | 2026-11-20 Credential storage | administrator keys and upstream credentials | [1] | 2026-11-20 Sources: [1] OpenAI. "Gateway compatibility requirements". https://learn.chatgpt.com/docs/enterprise/gateway-compatibility.md Role: primary. Accessed: 2026-11-20T13:38:01Z Quote: "Use environment variables for secret header values;" (Supports: Secret header values) Quote: "Preserve the headers your routing and attribution depend on" (Supports: Headers to preserve) Quote: "Authenticate developers separately from the gateway's upstream provider identity." (Supports: Developer authentication) Quote: "Keep administrator keys and upstream credentials on the gateway." (Supports: Credential storage) Snapshot SHA-256: 12e67546a9838a10adcc791affb295a4fe662d2636438759e9212d6011b678ad (captured 2026-11-13T03:49:56Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:49:56Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:38:01Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:38:01Z Last attempt: 2026-11-20T13:38:01Z Notes and limitations: Extracted automatically from a single official source (section "Authentication and headers"). Related: https://latestn.com/tool/codex/permissions-and-security/gateway-authentication-methods Which authentication methods can Codex use to connect to a gateway? https://latestn.com/tool/codex/permissions-and-security/gateway-authentication-options What authentication options does a Codex gateway support? https://latestn.com/tool/codex/permissions-and-security/how-policies-combine How do Global, Local, and Codex Cloud policies combine in Codex Agent Security? https://latestn.com/tool/codex/permissions-and-security/export-with-triage-status How do I include triage status, close reasons, or notes when exporting Codex findings? https://latestn.com/tool/codex/permissions-and-security/fix-finding-in-conversation How do I fix a security finding from a conversation in Codex? https://latestn.com/tool/codex/permissions-and-security/fix-finding-in-ui How do I generate, review, apply, and verify a patch for a security finding in Codex? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:49:56Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/permissions-and-security/gateway-auth-headers/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/codex/permissions-and-security/gateway-auth-headers POST: https://latestn.com/dispute/tool/codex/permissions-and-security/gateway-auth-headers with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/permissions-and-security/gateway-auth-headers?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What authentication and headers must a gateway preserve for Codex? Revision 1, last verified 2026-11-20T13:38:01Z. https://latestn.com/tool/codex/permissions-and-security/gateway-auth-headers (accessed 2026-11-21T09:57:30Z). @misc{LatestN_tool_codex_permissions_and_security_gateway_auth_headers_r1, title = {What authentication and headers must a gateway preserve for Codex?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/permissions-and-security/gateway-auth-headers}}, note = {Revision 1; digest sha256:dc27a182a703528a; last verified 2026-11-20T13:38:01Z; accessed 2026-11-21T09:57:30Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/codex/permissions-and-security/gateway-auth-headers