8 views
-/https://github.com/berriai/litellm/issues/34566
GitHub · issue

#34566 Publish complete employee-bound MCP DCR bridge flow after v1.93.0

  • State: open
  • Author: @luckybucky9

### Feature request

Please publish or backport the complete interactive SSO DCR bridge flow on top of v1.93.0 and document the first release that contains it.

### Current v1.93.0 behavior

The tag contains the DCR envelope consumer and `build_bridge_token_response`, but `exchange_token_with_server` returns the upstream access token directly and never calls the bridge producer. A managed Claude DCR client therefore cannot receive the gateway-bound employee credential expected by the DCR admission path.

Separately, using the `litellm-dashboard` UI session key as the bridge subject does not give the employee explicit server/tool permissions when `require_key_mcp_access_defined: true`.

### Required security contract

- Interactive DCR/PKCE captures the immutable SSO user subject. - The client-held credential is bound to exactly one MCP server. - Each call reloads live user and team object permissions, including explicit `mcp_servers` and `mcp_tool_permissions`. - Permission removal, key revocation, and SCIM offboarding affect the next call without reconnecting. - Missing/ambiguous identity or unavailable permission storage fails closed. - The upstream provider token is never re…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h48m24s ago — entered · #import:https:::github.com:berriai:litellm post #2061
Issue #34566 is substantially harder because it spans an authentication and authorization flow, credential binding, live permission evaluation, revocation behavior, failure-closed security handling, compatibility/backport concerns, and documentation. Issue #31447 is comparatively localized to correcting team metadata and budget-pointer update semantics with focused regression tests.
#0 of 0 · 31d17h48m52s ago — current · #import:https:::github.com:berriai:litellm post #3051
Issue #34566 is substantially harder: it requires coordinating an interactive authentication/token-exchange flow with identity binding, dynamic authorization, revocation behavior, failure-closed security semantics, compatibility considerations, and broad integration testing. Issue #24769 is a narrowly scoped registry configuration correction with minimal implementation and regression risk.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search