[PR #2702] [CLOSED] feat: Support trusted name header for user signup #21063

New Issue

GiteaMirror · 2026-04-20T03:19:42-05:00

GiteaMirror commented

2026-04-20 03:19:42 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/2702
Author: @sample
Created: 6/1/2024
Status: ❌ Closed

Base: dev ← Head: dev

📄 Description

Added support for WEBUI_AUTH_TRUSTED_NAME_HEADER to allow using a trusted name header during user signup if the header is present. Updated signup logic to use the trusted name when available, while preserving the trusted email as a fallback.

- Added `WEBUI_AUTH_TRUSTED_NAME_HEADER` configuration.
- Enhanced /signin endpoint to handle trusted name header.
- Updated main.py and auths.py to include the new header in the config imports.

Pull Request Checklist

Before submitting, make sure you've checked the following:

Target branch: Please verify that the pull request targets the dev branch.
Description: Provide a concise description of the changes made in this pull request.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
Testing: Have you written and run sufficient tests for validating the changes?
Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
Label: To cleary categorize this pull request, assign a relevant label to the pull request title, using one of the following:
- BREAKING CHANGE: Significant changes that may affect compatibility
- build: Changes that affect the build system or external dependencies
- ci: Changes to our continuous integration processes or workflows
- chore: Refactor, cleanup, or other non-functional code changes
- docs: Documentation update or addition
- feat: Introduces a new feature or enhancement to the codebase
- fix: Bug fix or error correction
- i18n: Internationalization or localization changes
- perf: Performance improvement
- refactor: Code restructuring for better maintainability, readability, or scalability
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)
- test: Adding missing tests or correcting existing tests
- WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

Added support for WEBUI_AUTH_TRUSTED_NAME_HEADER to allow using a trusted name header during user signup if the header is present. Updated signup logic to use the trusted name when available, while preserving the trusted email as a fallback.

Added

Added support for the WEBUI_AUTH_TRUSTED_NAME_HEADER environment variable.
Enhanced user signup logic in the /signin endpoint to use the trusted name header (WEBUI_AUTH_TRUSTED_NAME_HEADER) if present.

Changed

Updated main.py and auths.py to include the import of the new configuration variable.
Modified the signin function to handle the new header and use its value for the user's name during signup.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/2702 **Author:** [@sample](https://github.com/sample) **Created:** 6/1/2024 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `dev` --- ### 📄 Description Added support for `WEBUI_AUTH_TRUSTED_NAME_HEADER` to allow using a trusted name header during user signup if the header is present. Updated signup logic to use the trusted name when available, while preserving the trusted email as a fallback. - Added `WEBUI_AUTH_TRUSTED_NAME_HEADER` configuration. - Enhanced /signin endpoint to handle trusted name header. - Updated main.py and auths.py to include the new header in the config imports. # Pull Request Checklist **Before submitting, make sure you've checked the following:** - [x] **Target branch:** Please verify that the pull request targets the `dev` branch. - [x] **Description:** Provide a concise description of the changes made in this pull request. - [x] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [ ] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources? - [ ] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [ ] **Testing:** Have you written and run sufficient tests for validating the changes? - [x] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [ ] **Label:** To cleary categorize this pull request, assign a relevant label to the pull request title, using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description Added support for WEBUI_AUTH_TRUSTED_NAME_HEADER to allow using a trusted name header during user signup if the header is present. Updated signup logic to use the trusted name when available, while preserving the trusted email as a fallback. ### Added - Added support for the `WEBUI_AUTH_TRUSTED_NAME_HEADER` environment variable. - Enhanced user signup logic in the `/signin` endpoint to use the trusted name header (`WEBUI_AUTH_TRUSTED_NAME_HEADER`) if present. ### Changed - Updated `main.py` and `auths.py` to include the import of the new configuration variable. - Modified the `signin` function to handle the new header and use its value for the user's name during signup. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-20 03:19:42 -05:00

GiteaMirror closed this issue

2026-04-20 03:19:43 -05:00

GiteaMirror referenced this issue

2026-04-20 06:11:56 -05:00

[PR #21063] [CLOSED] fix: web search not working in native FC mode when builtin_tools is disabled #25908

GiteaMirror referenced this issue

2026-04-25 13:44:59 -05:00

[PR #21063] [CLOSED] fix: web search not working in native FC mode when builtin_tools is disabled #41538

GiteaMirror referenced this issue

2026-04-30 01:12:17 -05:00

[PR #21063] [CLOSED] fix: web search not working in native FC mode when builtin_tools is disabled #48956