I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.
Verify Feature Scope
I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
Problem Description
When Open WebUI forwards requests to the pipelines container, it includes a user dict which includes id, name, email, and role. The Pipelines container currently does not have access to user groups, api keys, or oauth tokens.
Oauth: Useful for authentication against downstream databases.
API Key: Useful for reverse proxy through OWUI when connecting to the LLM while logging usage.
Without user API keys, reverse proxy requires a service account making all custom Pipeline tool calls appear to come from a single source.
Groups: Useful for filtering vector databases at query time.
Desired Solution you'd like
Add opt-in environment variables to permit and control the flow of additional user context.
All flags will default to "false" to preserve existing behavior.
"True" status will enhance the user dict with additional user auth context.
Modification of Pipelines.py pipelines with an inlet function may serve as the most reasonable modification.
Use of configurable environment variables results in minimal impact to the community.
Alternatives Considered
Similar modifications were considered for openai.py to modify pipe functions without an inlet function,
but this approach may impact more users.
Open WebUI function scripts were also considered but would require more administrative burden when it is desired to apply this change to all pipelines employed by an organization. Manifold functions would apply to all pipelines within the pipeline container, but require turning off the native pipeline connection to avoid duplication and therefore results in a loss of features provided by the native pipelines tab.
Additional Context
No response
Originally created by @shawn-core-bpmi on GitHub (Apr 10, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23579
### Check Existing Issues
- [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request.
### Verify Feature Scope
- [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
### Problem Description
When Open WebUI forwards requests to the pipelines container, it includes a user dict which includes id, name, email, and role. The Pipelines container currently does not have access to user groups, api keys, or oauth tokens.
1) Oauth: Useful for authentication against downstream databases.
2) API Key: Useful for reverse proxy through OWUI when connecting to the LLM while logging usage.
Without user API keys, reverse proxy requires a service account making all custom Pipeline tool calls appear to come from a single source.
3) Groups: Useful for filtering vector databases at query time.
### Desired Solution you'd like
Add opt-in environment variables to permit and control the flow of additional user context.
All flags will default to "false" to preserve existing behavior.
"True" status will enhance the user dict with additional user auth context.
Modification of Pipelines.py pipelines with an inlet function may serve as the most reasonable modification.
Use of configurable environment variables results in minimal impact to the community.
### Alternatives Considered
Similar modifications were considered for openai.py to modify pipe functions without an inlet function,
but this approach may impact more users.
Open WebUI function scripts were also considered but would require more administrative burden when it is desired to apply this change to all pipelines employed by an organization. Manifold functions would apply to all pipelines within the pipeline container, but require turning off the native pipeline connection to avoid duplication and therefore results in a loss of features provided by the native pipelines tab.
### Additional Context
_No response_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @shawn-core-bpmi on GitHub (Apr 10, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23579
Check Existing Issues
Verify Feature Scope
Problem Description
When Open WebUI forwards requests to the pipelines container, it includes a user dict which includes id, name, email, and role. The Pipelines container currently does not have access to user groups, api keys, or oauth tokens.
Oauth: Useful for authentication against downstream databases.
API Key: Useful for reverse proxy through OWUI when connecting to the LLM while logging usage.
Without user API keys, reverse proxy requires a service account making all custom Pipeline tool calls appear to come from a single source.
Groups: Useful for filtering vector databases at query time.
Desired Solution you'd like
Add opt-in environment variables to permit and control the flow of additional user context.
All flags will default to "false" to preserve existing behavior.
"True" status will enhance the user dict with additional user auth context.
Modification of Pipelines.py pipelines with an inlet function may serve as the most reasonable modification.
Use of configurable environment variables results in minimal impact to the community.
Alternatives Considered
Similar modifications were considered for openai.py to modify pipe functions without an inlet function,
but this approach may impact more users.
Open WebUI function scripts were also considered but would require more administrative burden when it is desired to apply this change to all pipelines employed by an organization. Manifold functions would apply to all pipelines within the pipeline container, but require turning off the native pipeline connection to avoid duplication and therefore results in a loss of features provided by the native pipelines tab.
Additional Context
No response