acrognale-oai a20092a7a2 Expose effective login methods in config requirements (#45495) ...

## 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

2026-09-14 19:11:29 +00:00

..

schema

Expose effective login methods in config requirements (#45495)

2026-09-14 19:11:29 +00:00

scripts

Generate Python SDK types from repository app-server schemas (#44032)

2026-09-09 03:27:31 +00:00

src

Expose effective login methods in config requirements (#45495)

2026-09-14 19:11:29 +00:00

BUILD.bazel

Add a cacheable Bazel app-server schema bundle (#42174)

2026-09-02 02:00:18 +00:00

Cargo.toml

Keep credentials out of app-server logs (#39993)

2026-08-21 19:04:32 +00:00