[GH-ISSUE #17208] issue: OIDC access_denied Error page #18207

New Issue

2026-04-20T00:25:15-05:00

GiteaMirror commented

2026-04-20 00:25:15 -05:00

Originally created by @BenCoden on GitHub (Sep 4, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17208

Check Existing Issues

I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

0.6.26

Ollama Version (if applicable)

No response

Operating System

Fargate

Browser (if applicable)

Chrome, Firefox, Edge

Confirmation

I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

This is probably more of a feature request, because I do not think OWUI is doing anything it wasn't designed to do. Or maybe someone can share how they are solving this problem.

We have ODIC set up but when I user is login in to but does not have access to the OWUI it returns a Json message. Which is a poor user experience.

Actual Behavior

It would be great if OWUI would display this in a HTML page. Something similar to the login page, but with the text form the json in red somewhere. Maybe I am getting a little crazy, but it would also be nice if I could customize that message in the admin panel, to give them steps on how to request the app.

Steps to Reproduce

set up ODIC
try to access the app, but the user does not have access

Logs & Screenshots

Error Json message:

Endpoint:

Additional Information

No response

Originally created by @BenCoden on GitHub (Sep 4, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/17208 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version 0.6.26 ### Ollama Version (if applicable) _No response_ ### Operating System Fargate ### Browser (if applicable) Chrome, Firefox, Edge ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior This is probably more of a feature request, because I do not think OWUI is doing anything it wasn't designed to do. Or maybe someone can share how they are solving this problem. We have ODIC set up but when I user is login in to but does not have access to the OWUI it returns a Json message. Which is a poor user experience. <img width="933" height="39" alt="Image" src="https://github.com/user-attachments/assets/1d5dbf1f-b8b5-4f8a-bc54-48dd95d00e81" /> ### Actual Behavior It would be great if OWUI would display this in a HTML page. Something similar to the login page, but with the text form the json in red somewhere. Maybe I am getting a little crazy, but it would also be nice if I could customize that message in the admin panel, to give them steps on how to request the app. <img width="1247" height="573" alt="Image" src="https://github.com/user-attachments/assets/e47f3eeb-0f20-4832-92b8-f8be4afc98bd" /> ### Steps to Reproduce 1. set up ODIC 2. try to access the app, but the user does not have access ### Logs & Screenshots Error Json message: <img width="839" height="67" alt="Image" src="https://github.com/user-attachments/assets/1e9c1efc-a6f0-4ea8-975e-9c84220389f3" /> Endpoint: <img width="1002" height="25" alt="Image" src="https://github.com/user-attachments/assets/b0f42225-b735-4d5f-95e8-e5c5af95bd20" /> ### Additional Information _No response_

GiteaMirror added the bug label 2026-04-20 00:25:15 -05:00

GiteaMirror closed this issue

2026-04-20 00:25:16 -05:00

GiteaMirror commented

2026-04-20 00:25:17 -05:00

@tjbck commented on GitHub (Sep 6, 2025):

Addressed with 3d6d050ad8

@tjbck commented on GitHub (Sep 6, 2025): Addressed with 3d6d050ad82d360adc42d6e9f42e8faf8d13c9f4

GiteaMirror commented

2026-04-20 00:25:17 -05:00

@BenCoden commented on GitHub (Sep 7, 2025):

Thank you

@BenCoden commented on GitHub (Sep 7, 2025): Thank you