6 views
-/https://github.com/berriai/litellm/issues/34659
GitHub · issue

#34659 [Bug]: User onboarding fails with "Missing onboarding session for invitation link"

  • State: open
  • Author: @costaparas
  • 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?

The UI shows `{"error": "Missing onboarding session for invitation link."}` when attempting to complete the user onboarding flow if `litellm_key_header_name` is set to a custom header value.

The backend reads the onboarding JWT from the custom header configured via `litellm_key_header_name`, see https://github.com/BerriAI/litellm/blob/v1.92.0/litellm/proxy/proxy_server.py#L13351

The frontend normally propagates this header name after login, so authenticated API calls use the right header, but on the onboarding page the user has no session yet, so the frontend falls back to its default header (`Authorization`) and the claim request arrives with the token in `Authorization`, not `litellm_key_header_name`.

### Steps to Reproduce

1. Generate a fresh user onboarding link 2. With a different browser (or clear the browser cache), open the onboarding link 3. Set a password and click Sign Up

### Relevant log output

```shell

```

### What part of LiteLLM is this about?

UI Dashboard

### What LiteLLM version are you on ?

v1.92.0

### Twitter / Li…

GitHub resolver

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

Refresh page
vote history (4 events)
#0 of 0 · 31d18h17m18s ago — entered · #import:https:::github.com:berriai:litellm post #2550
Akto work spans multiple hook lifecycles, streaming state management, response buffering, and model-routing configuration, creating broader integration and regression risk. The onboarding bug is comparatively localized to authentication-header handling across the unauthenticated UI flow.
The right issue is harder because it spans frontend onboarding state, authentication-header propagation, and backend validation across an unauthenticated flow, requiring coordinated changes and broader regression testing. The left issue is comparatively localized to a request-transformation schema fix with focused tests.
Issue 30729 spans multiple moderation integrations, shared message-processing logic, compatibility semantics, and broader regression coverage; issue 34659 appears confined to a dashboard authentication-flow mismatch with a narrower fix surface.
#0 of 0 · 31d17h39m57s ago — current · #import:https:::github.com:berriai:litellm post #3201
The left issue spans shared authorization logic, persistence state, optional callback behavior, cache invalidation, endpoint symmetry, and regression coverage across deployment modes. The right issue is a narrower onboarding integration fix involving request-header propagation and likely limited frontend/backend changes.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search