[PR #19768] [MERGED] feat: new OAUTH_AUDIENCE config #80212

New Issue

GiteaMirror · 2026-05-13T14:16:24-05:00

GiteaMirror commented

2026-05-13 14:16:24 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/19768
Author: @bitsofinfo
Created: 12/4/2025
Status: ✅ Merged
Merged: 12/6/2025
Merged by: @tjbck

Base: dev ← Head: dev

📝 Commits (2)

50d562e feat: new config AUTH0_AUDIENCE
1722f48 feat: OAUTH_AUDIENCE config

📊 Changes

2 files changed (+13 additions, -1 deletions)

View changed files

📝 backend/open_webui/config.py (+5 -0)
📝 backend/open_webui/utils/oauth.py (+8 -1)

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request.

This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR.

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

[X ] Target branch: Verify that the pull request targets the dev branch. Not targeting the dev branch will lead to immediate closure of the PR.
[ X] Description: Provide a concise description of the changes made in this pull request down below.
[ X] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[ X] Documentation: If necessary, update relevant documentation Open WebUI Docs like environment variables, the tutorials, or other documentation sources.
Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
Testing: Perform manual tests to verify the implemented fix/feature works as intended AND does not break any other functionality. Take this as an opportunity to make screenshots of the feature/fix and include it in the PR description.
Agentic AI Code: Confirm this Pull Request is not written by any AI Agent or has at least gone through additional human review AND manual testing. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR.
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?
Title Prefix: To clearly categorize this pull request, prefix 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

Added

OAUTH_AUDIENCE lets oauth OIDC integrations optionally specify an audience which will be provided to the provider's authorization endpoint as an additional query parameter during handle login.

Description

See #19730.
Some oauth provider's support an optional audience value presented as a query parameter to the authorization endpoint. If this value is present it will be added as a query parameter to the providers' configured authorization endpoint during the handle login process.
I've renamed the variable OAUTH_AUDIENCE. From what I can see in the RFC this additional query parameter is not part of the official spec for the authorization endpoints parameters. Its serves as a hint for the provider for the token generation that follows a user login. Hence why the original name, however.... there are other providers that support this other than just auth0.
see: ory, auth0 etc

Added

New configuration variable OAUTH_AUDIENCE (string)

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.

Note

Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.

_{🔄 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/19768 **Author:** [@bitsofinfo](https://github.com/bitsofinfo) **Created:** 12/4/2025 **Status:** ✅ Merged **Merged:** 12/6/2025 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `dev` --- ### 📝 Commits (2) - [`50d562e`](https://github.com/open-webui/open-webui/commit/50d562ee825c872d6cec3d9cf9158a26ed0fbca8) feat: new config AUTH0_AUDIENCE - [`1722f48`](https://github.com/open-webui/open-webui/commit/1722f48c24d1c66f3a8b44b98ba3970326e8fef9) feat: OAUTH_AUDIENCE config ### 📊 Changes **2 files changed** (+13 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/config.py` (+5 -0) 📝 `backend/open_webui/utils/oauth.py` (+8 -1) </details> ### 📄 Description # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request. This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR. **Before submitting, make sure you've checked the following:** - [X ] **Target branch:** Verify that the pull request targets the `dev` branch. **Not targeting the `dev` branch will lead to immediate closure of the PR.** - [ X] **Description:** Provide a concise description of the changes made in this pull request down below. - [ 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. - [ X] **Documentation:** If necessary, update relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs) like environment variables, the tutorials, or other documentation sources. - [X] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [X] **Testing:** Perform manual tests to **verify the implemented fix/feature works as intended AND does not break any other functionality**. Take this as an opportunity to **make screenshots of the feature/fix and include it in the PR description**. - [X] **Agentic AI Code:** Confirm this Pull Request is **not written by any AI Agent** or has at least **gone through additional human review AND manual testing**. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR. - [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? - [X] **Title Prefix:** To clearly categorize this pull request, prefix 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 ### Added - OAUTH_AUDIENCE lets oauth OIDC integrations optionally specify an `audience` which will be provided to the provider's authorization endpoint as an additional query parameter during handle login. ### Description - See #19730. - Some oauth provider's support an optional `audience` value presented as a query parameter to the authorization endpoint. If this value is present it will be added as a query parameter to the providers' configured authorization endpoint during the handle login process. - I've renamed the variable OAUTH_AUDIENCE. From what I can see in the RFC this additional query parameter is not part of the official spec for the authorization endpoints parameters. Its serves as a hint for the provider for the token generation that follows a user login. Hence why the original name, however.... there are other providers that support this other than just auth0. - see: [ory](https://www.ory.com/docs/hydra/guides/audiences), [auth0](https://support.auth0.com/center/s/article/opaque-versus-jwt-access-token) etc ### Added - New configuration variable `OAUTH_AUDIENCE` (string) --- ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](https://github.com/open-webui/open-webui/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. > [!NOTE] > Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in. --- <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-05-13 14:16:24 -05:00

GiteaMirror closed this issue

2026-05-13 14:16:27 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#80212