-/https://github.com/berriai/litellm/issues/30641

7 views

-/https://github.com/berriai/litellm/issues/30641

GitHub · issue

#30641 [Feature]: Surface Helm/env-configured SSO settings in the Admin UI (treat declarative config as a first-class citizen)

State: open
Author: @niklasfrick
Labels: enhancement, ui-dashboard

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### The Feature

## Check for existing issues

- [x] I have searched the existing issues and checked that this is not a duplicate.

Related but distinct: - #11623 (config-file models intermittently appear/disappear in the UI under `STORE_MODEL_IN_DB`) - #15061 (UI-created MCP servers non-functional when `STORE_MODEL_IN_DB=false`) - #25770 (cannot change `ui_settings` from the UI when store-models-in-db is disabled) - #19312 / #19620 (SSO role mapping / role sync) — these concern role propagation, not config visibility.

None of these track the gap below: SSO providers configured declaratively (env vars / Helm values / `proxy_config.yaml`) are not reflected in the Admin UI's SSO settings.

## The problem

When SSO is configured declaratively rather than through the UI, e.g. via the official env-var approach:

```yaml # Helm values -> rendered into the Deployment env env: GENERIC_CLIENT_ID: "..." GENERIC_CLIENT_SECRET: "..." GENERIC_AUTHORIZATION_ENDPOINT: "https://idp.example.com/auth" GENERIC_TOKEN_ENDPOINT: "https://idp.example.com/token" GENERIC_USERIN…

GitHub resolver

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

vote history (20 events)

#0 of 0 · 31d18h11m37s ago — entered · #import:https:::github.com:berriai:litellm post #2670

-/https://github.com/berriai/litellm/issues/30641⭐4:1-/https://github.com/berriai/litellm/issues/33893

Issue 30641 is harder because it spans backend configuration discovery, secure secret handling, API/UI state synchronization, deployment variants, and broad regression testing. Issue 33893 is more localized to provider authentication and request-routing logic with focused adapter tests.

#0 of 0 · 31d17h34m52s ago · #import:https:::github.com:berriai:litellm post #3309

-/https://github.com/berriai/litellm/issues/318213:1-/https://github.com/berriai/litellm/issues/30641⭐

The left task spans quota semantics, persistent usage accounting, calendar and timezone handling, concurrency safety, API changes, UI work, and distributed-system edge cases. The right task is primarily configuration discovery, safe presentation, and dashboard integration, with a narrower behavioral scope.

#0 of 0 · 31d17h33m17s ago · #import:https:::github.com:berriai:litellm post #3335

-/https://github.com/berriai/litellm/issues/30641⭐5:3-/https://github.com/berriai/litellm/issues/27852

The right issue spans configuration-resolution semantics, backend exposure, frontend presentation, provider coverage, secret-handling, and compatibility testing. The left issue is a narrower distributed-state synchronization problem, though it carries meaningful concurrency and infrastructure-debugging risk.

#0 of 0 · 31d17h33m14s ago · #import:https:::github.com:berriai:litellm post #3336

-/https://github.com/berriai/litellm/issues/30641⭐3:2-/https://github.com/berriai/litellm/issues/32456

The right issue is harder because it spans backend configuration discovery, precedence and secret-handling concerns, API contracts, and Admin UI state/rendering. The left issue is narrower, primarily requiring an image-edit request-path change, provider-specific translation, and focused regression tests.

#0 of 0 · 31d17h33m11s ago · #import:https:::github.com:berriai:litellm post #3337

-/https://github.com/berriai/litellm/issues/322017:4-/https://github.com/berriai/litellm/issues/30641⭐

The left issue is harder because it crosses the pass-through execution path, raw provider response formats, guardrail enforcement semantics, and regression testing across endpoint variants. The right issue is primarily a configuration-discovery/API and dashboard presentation change with a narrower integration surface.

#0 of 0 · 31d17h33m7s ago · #import:https:::github.com:berriai:litellm post #3338

-/https://github.com/berriai/litellm/issues/30641⭐5:3-/https://github.com/berriai/litellm/issues/26897

30641 is harder because it spans backend configuration discovery, API design, frontend state handling, precedence and secret-safety rules, plus deployment-oriented tests. 26897 is narrower, primarily requiring diagnosis and correction of one request-routing/parameter propagation path with focused regression coverage.

#0 of 0 · 31d17h33m4s ago · #import:https:::github.com:berriai:litellm post #3339

-/https://github.com/berriai/litellm/issues/30641⭐3:2-/https://github.com/berriai/litellm/issues/30501

Issue 30641 is harder because it spans configuration discovery, backend/API exposure, secret handling, UI state and presentation, deployment-specific behavior, and compatibility testing. Issue 30501 is narrower in scope, primarily involving multimodal input normalization and provider-specific translation with validation and MIME handling.

#0 of 0 · 31d17h32m23s ago · #import:https:::github.com:berriai:litellm post #3351

-/https://github.com/berriai/litellm/issues/265353:1-/https://github.com/berriai/litellm/issues/30641⭐

The left task spans a multi-provider compatibility test framework, CI integration, version handling, proxy configuration, and broad end-to-end validation, creating substantially greater coordination and environmental risk. The right task is a more contained backend-to-dashboard configuration visibility change with focused UI and regression testing.

#0 of 0 · 31d17h29m36s ago · #import:https:::github.com:berriai:litellm post #3396

-/https://github.com/berriai/litellm/issues/238413:2-/https://github.com/berriai/litellm/issues/30641⭐

The left issue spans multiple request-conversion paths and compatibility-sensitive translation behavior, requiring coordinated code changes and broad regression testing. The right issue is a more bounded configuration-visibility change across backend and dashboard layers, with masking and precedence considerations but less protocol-surface risk.

#0 of 0 · 31d17h28m45s ago · #import:https:::github.com:berriai:litellm post #3410

-/https://github.com/berriai/litellm/issues/252974:1-/https://github.com/berriai/litellm/issues/30641⭐

#25297 requires architectural changes to proxy request routing, extensibility boundaries, configuration, execution semantics, and broad compatibility testing; #30641 is primarily an admin-UI and configuration-discovery integration with narrower behavioral scope.

#0 of 0 · 31d17h25m2s ago · #import:https:::github.com:berriai:litellm post #3471

-/https://github.com/berriai/litellm/issues/30641⭐3:1-/https://github.com/berriai/litellm/issues/32562

The left issue spans backend configuration discovery, secure redaction, API/UI changes, and compatibility across multiple declarative deployment paths. The right issue is narrower, mainly requiring robust failure propagation and event-stream tests within one execution flow.

#0 of 0 · 31d17h23m6s ago · #import:https:::github.com:berriai:litellm post #3502

-/https://github.com/berriai/litellm/issues/30641⭐3:2-/https://github.com/berriai/litellm/issues/27989

The left issue spans backend configuration discovery, provider normalization, secret-safe presentation, and Admin UI changes across multiple deployment paths. The right issue is narrower in surface area, though it carries meaningful concurrency and database correctness risk.

#0 of 0 · 31d17h23m2s ago · #import:https:::github.com:berriai:litellm post #3503

-/https://github.com/berriai/litellm/issues/312963:1-/https://github.com/berriai/litellm/issues/30641⭐

The left item is harder because it spans security-sensitive protocol behavior, request handling, standards-compliant discovery responses, configuration validation, and interoperability testing. The right item is primarily a bounded backend-to-frontend configuration visibility change with UI and regression coverage.

#0 of 0 · 31d17h21m42s ago · #import:https:::github.com:berriai:litellm post #3521

-/https://github.com/berriai/litellm/issues/30641⭐3:1-/https://github.com/berriai/litellm/issues/33772

The left task spans backend configuration discovery, Helm/environment precedence, secure secret handling, API exposure, and Admin UI integration with broad regression risk. The right task is a more localized cost-model and token-parsing correction with focused provider and billing tests.

#0 of 0 · 31d17h21m38s ago · #import:https:::github.com:berriai:litellm post #3522

-/https://github.com/berriai/litellm/issues/30641⭐8:1-/https://github.com/berriai/litellm/issues/28554

The left issue spans backend configuration discovery, declarative-versus-persisted state handling, secure secret presentation, API/UI behavior, and likely deployment and regression testing. The right issue is a narrowly scoped schema correction with focused validation coverage, so the left carries substantially greater integration risk.

#0 of 0 · 31d17h20m1s ago · #import:https:::github.com:berriai:litellm post #3542

-/https://github.com/berriai/litellm/issues/347325:4-/https://github.com/berriai/litellm/issues/30641⭐

The concurrency fix is harder because it requires a race-free, distributed accounting design with atomic admission, failure handling, compatibility guarantees, and stress testing. The UI work is broader across configuration sources and security boundaries but is comparatively conventional read-only API and frontend integration.

#0 of 0 · 31d17h18m40s ago · #import:https:::github.com:berriai:litellm post #3558

-/https://github.com/berriai/litellm/issues/333255:3-/https://github.com/berriai/litellm/issues/30641⭐

The right-side fix has greater engineering risk because it affects distributed state consistency, lifecycle behavior, and concurrency-sensitive admission guarantees; the left is mainly a bounded backend/UI integration with configuration mapping and security-aware presentation.

#0 of 0 · 31d17h18m11s ago · #import:https:::github.com:berriai:litellm post #3564

-/https://github.com/berriai/litellm/issues/30641⭐3:1-/https://github.com/berriai/litellm/issues/27755

The left task spans backend configuration discovery, secure secret handling, API/UI integration, declarative-versus-database precedence, and comprehensive dashboard testing. The right task is primarily a provider-specific compatibility/debugging fix with a narrower implementation surface, though it may depend on external service behavior.

#0 of 0 · 31d17h18m2s ago · #import:https:::github.com:berriai:litellm post #3566

-/https://github.com/berriai/litellm/issues/339213:1-/https://github.com/berriai/litellm/issues/30641⭐

Three independent provider integrations require broader API-translation work, model metadata and pricing coverage, parameter compatibility, authentication, and regression testing. The other task is primarily a focused configuration-to-dashboard exposure change, with some security and deployment-environment complexity but a narrower implementation surface.

#0 of 0 · 31d17h17m16s ago — current · #import:https:::github.com:berriai:litellm post #3575

-/https://github.com/berriai/litellm/issues/30641⭐3:1-/https://github.com/berriai/litellm/issues/34998

#30641 spans configuration ingestion, backend APIs, frontend settings behavior, provider coverage, and secure secret handling, creating broader integration and regression risk; #34998 is primarily a focused authorization/data-resolution fix with narrower testing scope.

discussed in #import:https:::github.com:berriai:litellm

ranked child groups
scope depth

no voted pairs yet in this scope

cli

spread