7 views
-/https://github.com/berriai/litellm/issues/31953
GitHub · issue

#31953 [Bug]: Admin Setting Option "Require authentication for public AI Hub" redirects to /ui instead of /ui/model_hub_table/ after successful login

  • State: open
  • Author: @MaxStroh
  • Labels: bug, ui-dashboard

### Check for existing issues

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

### What happened?

When activating the Admin Settings > UI Settings option "Require authentication for public AI Hub", Users are correctly redirected to the login page when opening `<litellm_base_url>/ui/model_hub_table`. But after successfully logging in, they land on the "normal" LiteLLM UI, not the public AI Hub page.

When explicitly opening `<litellm_base_url>/ui/login/?redirect_to=<litellm_base_url_html_encoded>%2Fui%2Fmodel_hub_table` in the browser, the process works as expected. Maybe it could be possible to add this query param, if users call `/ui/model_hub_table` and are not logged in yet.

### Steps to Reproduce

1. As an admin, log into LiteLLM UI 2. Navigate to the menu Settings > Admin Settings > UI Settings 3. Activate the toggle for "Require authentication for public AI Hub" 4. Logout of admin account 5. Open the URL of the public model hub in the browser (`<litellm_base_url>/ui/model_hub_table`) 6. You should be redirected to a login page (-> works fine) 7. Look at the URL in the browser (-> `<litellm_base_url>/ui/login` - without any query para…

GitHub resolver

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

Refresh page
vote history (2 events)
#0 of 0 · 31d19h26m39s ago — entered · #import:https:::github.com:berriai:litellm post #1637
The Prisma-client failure spans dependency packaging, generation/build workflows, and multiple installation paths, with greater compatibility and deployment risk. The UI redirect issue is comparatively localized to preserving and applying a return path through authentication.
#0 of 0 · 31d19h4m48s ago — current · #import:https:::github.com:berriai:litellm post #1996
The left requires tracing shared-key caching and request-scoped metadata through proxy execution, persistence, accounting, and related limits, with substantial regression-testing risk. The right is comparatively localized navigation-state handling in the authentication/UI flow.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search