[codex] Scope managed Bedrock auth cache by provider#31324
Draft
celia-oai wants to merge 1 commit into
Draft
Conversation
This was referenced Jul 7, 2026
92e0751 to
7c28baa
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Managed Amazon Bedrock API keys are persisted in the same durable auth store as general Codex credentials, but they need an independent cache and reload lifetime. A single cached auth slot couples Bedrock credential updates to the general auth snapshot: replacing the persisted record with Bedrock credentials can cause a generic auth reload to discard the OpenAI credentials already held by a loaded session.
This is the first PR in the Phase 1 provider-scoped auth stack. It keeps managed Bedrock credentials represented as
CodexAuth::BedrockApiKey, while establishing the cache and provider boundaries needed for later PRs to add managed Bedrock login/logout APIs without changing credentials underneath existing sessions. It does not add a new user-facing login flow by itself.What changed
AuthManager's in-memory state into general and managed Bedrock cache slots, with Bedrock-specific persistence and reload paths that leave cached general auth untouched.BedrockApiKeyAuthinCodexAuthand have the Amazon Bedrock provider expose managed credentials asCodexAuth::BedrockApiKey.Debugoutput.CodexAuthreporting, and API-key redaction.Validation
just test -p codex-loginjust test -p codex-model-providerjust test -p codex-cliStack
maincodex/provider-auth-foundationcodex/managed-bedrock-apicodex/managed-bedrock-login-v2