[GH-ISSUE #6034] Add Option to Forward User Information to External OpenAI-Compatible APIs #14213

New Issue

GiteaMirror · 2026-04-19T20:39:08-05:00

GiteaMirror commented

2026-04-19 20:39:08 -05:00

Originally created by @DucNgn on GitHub (Oct 8, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/6034

Feature Request: Forward User Information to OpenAI-Compatible API

Current Behavior

The Open-AI Adapter in OpenWebUI currently only passes user information (name, email, role) to pipelines models.

Proposed Feature

Add an option to forward user information to the external OpenAI-compatible API URL, either as part of the payload or in the headers. This feature would be beneficial when integrating with OpenAI-compatible APIs that can make use of user-specific data.

Implementation Details

Add a configuration flag to enable/disable this feature
When enabled, include user information in API requests
Allow flexibility in how the information is sent (payload vs. headers). I'm leaning toward passing as headers to avoid conflicting with OpenAI schema.

I am willing to work on this feature if the community approves.

Questions

Should this be an opt-in or opt-out feature?
Are there any security considerations we need to address?
Which specific user information fields should be included?

https://github.com/open-webui/open-webui/blob/main/backend/open_webui/apps/openai/main.py#L399-L405

Originally created by @DucNgn on GitHub (Oct 8, 2024). Original GitHub issue: https://github.com/open-webui/open-webui/issues/6034 # Feature Request: Forward User Information to OpenAI-Compatible API ## Current Behavior The Open-AI Adapter in OpenWebUI currently only passes user information (name, email, role) to `pipelines` models. ## Proposed Feature Add an option to forward user information to the external OpenAI-compatible API URL, either as part of the payload or in the headers. This feature would be beneficial when integrating with OpenAI-compatible APIs that can make use of user-specific data. ## Implementation Details - Add a configuration flag to enable/disable this feature - When enabled, include user information in API requests - Allow flexibility in how the information is sent (payload vs. headers). I'm leaning toward passing as headers to avoid conflicting with OpenAI schema. I am willing to work on this feature if the community approves. ## Questions - Should this be an opt-in or opt-out feature? - Are there any security considerations we need to address? - Which specific user information fields should be included? ## Related Code https://github.com/open-webui/open-webui/blob/main/backend/open_webui/apps/openai/main.py#L399-L405

GiteaMirror closed this issue

2026-04-19 20:39:09 -05:00

GiteaMirror referenced this issue

2026-04-19 22:54:45 -05:00

[GH-ISSUE #14213] issue: Can't use OAI. Requires tooling. #17183

GiteaMirror referenced this issue

2026-04-25 06:35:40 -05:00

[GH-ISSUE #14213] issue: Can't use OAI. Requires tooling. #32712

GiteaMirror referenced this issue

2026-05-05 18:09:47 -05:00

[GH-ISSUE #14213] issue: Can't use OAI. Requires tooling. #55849

Sign in to join this conversation.