Route Fed API-key logins with existing base-url config#17171
Route Fed API-key logins with existing base-url config#17171
Conversation
|
All contributors have signed the CLA ✍️ ✅ |
Probe OpenAI /v1/me during API-key login, persist a Gov API base URL for FedRAMP current orgs, and apply the saved base when constructing OpenAI API providers. Testing: just fmt; cargo test -p codex-login; cargo test -p codex-core openai_api_key_routing. cargo check -p codex-cli blocked by local disk full. Co-authored-by: Codex <noreply@openai.com>
cc2d9b4 to
8069205
Compare
|
I have read the CLA Document and I hereby sign the CLA |
|
recheck |
Validate API-key login with /v1/me, use the current org FedRAMP flag to persist the existing openai_base_url override, and keep runtime provider construction on the existing config path. Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
|
1 open question is im not sure what the best logout behavior should be? should we reset |
|
Security review note: I think the FedRAMP routing config write needs to happen before the API key is persisted, or the auth write needs to be rolled back if the config write fails. In the current Could we either write the required |
Co-authored-by: Codex <noreply@openai.com>
|
Addressed in The |
Summary:
Depends on: