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

#34555 [Bug]: Non-enterprise (legacy SMTP) invitation email links to bare PROXY_BASE_URL - no invitation_id, user cannot onboard

  • State: open
  • Author: @tomaskir
  • Labels: proxy

### Check for existing issues

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

Closest existing issues are #20499 ("no invite mails sent" - different symptom) and the closed enterprise / `/invitation/new` link-id fixes #12130 / #11978 / #15375. None cover the legacy OSS SMTP template.

### What happened?

On a self-hosted **OSS deployment (no enterprise license)**, creating an internal user with `send_invite_email: true` sends the invitation email fine, but the **"Get Started here" button links to the bare `PROXY_BASE_URL`** - no invitation id/hash. The link lands on the login page; onboarding can never complete because `GET /onboarding/get_token` requires the invitation id in the URL, and it's never there. The invited user cannot join.

**Root cause (source-verified @ `v1.93.0`):** the legacy email path builds the button from `PROXY_BASE_URL` only.

- `litellm/integrations/email_templates/templates.py` - `USER_INVITED_EMAIL_TEMPLATE`:

```html <a href="{base_url}" ...>Get Started here</a> ```

- `litellm/integrations/SlackAlerting/slack_alerting.py` - `send_key_created_or_user_invited_email` formats it with `base_url=base_url, team_na…

GitHub resolver

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

Refresh page
vote history (4 events)
#0 of 0 · 31d19h30m27s ago — entered · #import:https:::github.com:berriai:litellm post #1684
34555 requires code-path investigation, URL/token flow validation, backward-compatibility consideration, and regression tests; 26235 is a narrowly scoped documentation correction.
Issue 34555 is harder because it requires coordinating invitation-link construction, token/onboarding flow compatibility, configuration handling, and regression coverage across the legacy email path. Issue 28642 is comparatively localized to API response mapping or serialization for a single persisted field.
The left issue is harder because it involves provider-specific request translation, edge-case handling, upstream compatibility, and regression testing across model variants. The right issue is comparatively localized to proxy invitation-link construction and associated email-flow tests.
#0 of 0 · 31d18h54m16s ago — current · #import:https:::github.com:berriai:litellm post #2278
26879 requires coordinated changes across Responses-to-chat translation and provider-specific message normalization, with broader compatibility and regression-testing risk; 34555 is comparatively localized email URL construction and template plumbing.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search