Repository navigation
Expose effective login methods in config requirements - #45495
Merged
copyberry[bot] merged 1 commit intoSep 14, 2026
Merged
copyberry[bot] merged 1 commit into
copyberry[bot] merged 1 commit into
Conversation
## Why Configuration requirements did not report which login methods the running app server permits after applying managed policy, forced login settings, and workspace restrictions. ## What changed - Add `allowedLoginMethods` to `configRequirements/read`, using the running authentication manager's effective policy rather than newly read authentication settings. - Return requirements when login methods are restricted even without managed requirements, while preserving `requirements: null` for the unrestricted default. - Update protocol schemas and generated TypeScript and Python types. An empty list permits no login method; older servers may omit the field. ## Testing Add coverage for managed and forced login restrictions, workspace intersections, policy reporting after requirements files change, invalid login methods, and API-only Amazon Bedrock without ChatGPT requests. Extend tests for conflicting authentication requirements and cloud policy precedence. GitOrigin-RevId: 56c0767a74143e793aac2ac165d0cbe98a09469b
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/56c0767a74143e793aac2ac165d0cbe98a09469b
branch
from
September 14, 2026 19:11
ecbc33a to
a20092a
Compare
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/56c0767a74143e793aac2ac165d0cbe98a09469b
branch
September 14, 2026 19:11
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Expose effective login methods in config requirements
Why
Configuration requirements did not report which login methods the running app server permits after applying managed policy, forced login settings, and workspace restrictions.
What changed
allowedLoginMethodstoconfigRequirements/read, using the running authentication manager's effective policy rather than newly read authentication settings.requirements: nullfor the unrestricted default.Testing
Add coverage for managed and forced login restrictions, workspace intersections, policy reporting after requirements files change, invalid login methods, and API-only Amazon Bedrock without ChatGPT requests. Extend tests for conflicting authentication requirements and cloud policy precedence.