[GH-ISSUE #15544] issue: OIDC provider not activating despite correct config, env vars, and successful network connectivity #17595

New Issue

GiteaMirror · 2026-04-19T23:23:48-05:00

GiteaMirror commented

2026-04-19 23:23:48 -05:00

Originally created by @nguyendev on GitHub (Jul 6, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/15544

Check Existing Issues

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

Installation Method

Git Clone

Open WebUI Version

0.6.15

Ollama Version (if applicable)

No response

Operating System

Windows Server 2024

Browser (if applicable)

No response

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

Describe the bug

The OIDC login button does not appear on the login page, and the /api/config endpoint returns an empty oauth.providers object, even when all environment variables are correctly loaded and network connectivity from within the container to the OIDC provider is successful.

Have you read the Contributing Guidelines on issues?

Yes

File: .env

OAUTH_CONFIG=[{"oidc_enabled":true,"display_name":"Login with Solann ID","client_id":"open-webui-client","client_secret":"XXX","well_known_url":"https://X/.well-known/openid-configuration","scopes":"openid profile email roles"}]

OPENAI_API_BASE_URL=https://api.XXX/api/ai-proxy/v1
OPENAI_API_KEY=DUMMY_KEY

File: docker-compose.yml

version: '3.8'

services:
open-webui:
image: ghcr.io/open-webui/open-webui:v0.6.15
container_name: solann-ai-webui-final
ports:
- "8080:8080"

# Nạp các biến từ file .env
env_file:
  - ./.env
  
volumes:
  - open-webui-data-final:/app/backend/data
restart: unless-stopped

volumes:
open-webui-data-final:

Actual Behavior

To Reproduce

Set up Open WebUI using the docker-compose.yml and .env files below on Docker Desktop for Windows Server.
Start the container using docker-compose up -d.
Access the Web UI. The OIDC login button is missing.
The /api/config endpoint shows {"oauth": {"providers": {}}}.

Steps to Reproduce

Expected behavior

The OIDC login button should appear on the login page, and the /api/config endpoint should reflect the OIDC provider configuration.

Logs & Screenshots

Screenshots

Result of /api/config:

{
    "status": true,
    "name": "Open WebUI",
    "version": "0.6.15",
    "oauth": {
        "providers": {}
    },
    "features": {
        "auth": true,
        "enable_login_form": true
    }
}

### Additional Information

_No response_

Originally created by @nguyendev on GitHub (Jul 6, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/15544 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Git Clone ### Open WebUI Version 0.6.15 ### Ollama Version (if applicable) _No response_ ### Operating System Windows Server 2024 ### Browser (if applicable) _No response_ ### 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 ### Describe the bug The OIDC login button does not appear on the login page, and the `/api/config` endpoint returns an empty `oauth.providers` object, even when all environment variables are correctly loaded and network connectivity from within the container to the OIDC provider is successful. ### Have you read the [Contributing Guidelines on issues](httpshttps://github.com/open-webui/open-webui/blob/main/CONTRIBUTING.md#reporting-bugs)? Yes # File: .env OAUTH_CONFIG=[{"oidc_enabled":true,"display_name":"Login with Solann ID","client_id":"open-webui-client","client_secret":"XXX","well_known_url":"https://X/.well-known/openid-configuration","scopes":"openid profile email roles"}] OPENAI_API_BASE_URL=https://api.XXX/api/ai-proxy/v1 OPENAI_API_KEY=DUMMY_KEY # File: docker-compose.yml version: '3.8' services: open-webui: image: ghcr.io/open-webui/open-webui:v0.6.15 container_name: solann-ai-webui-final ports: - "8080:8080" # Nạp các biến từ file .env env_file: - ./.env volumes: - open-webui-data-final:/app/backend/data restart: unless-stopped volumes: open-webui-data-final: ### Actual Behavior ### To Reproduce 1. Set up Open WebUI using the `docker-compose.yml` and `.env` files below on Docker Desktop for Windows Server. 2. Start the container using `docker-compose up -d`. 3. Access the Web UI. The OIDC login button is missing. 4. The `/api/config` endpoint shows `{"oauth": {"providers": {}}}`. ### Steps to Reproduce ### Expected behavior The OIDC login button should appear on the login page, and the `/api/config` endpoint should reflect the OIDC provider configuration. ### Logs & Screenshots ### Screenshots *Result of `/api/config`:* ```json { "status": true, "name": "Open WebUI", "version": "0.6.15", "oauth": { "providers": {} }, "features": { "auth": true, "enable_login_form": true } } ### Additional Information _No response_

GiteaMirror added the bug label 2026-04-19 23:23:48 -05:00

GiteaMirror closed this issue

2026-04-19 23:23:49 -05:00

GiteaMirror commented

2026-04-19 23:23:51 -05:00

@Classic298 commented on GitHub (Jul 6, 2025):

where is your config? I dont see you set all the required environment variables for proper OIDC / OAUTH as per the docs?

@Classic298 commented on GitHub (Jul 6, 2025): where is your config? I dont see you set all the required environment variables for proper OIDC / OAUTH as per the docs?

GiteaMirror commented

2026-04-19 23:23:51 -05:00

@nguyendev commented on GitHub (Jul 6, 2025):

Hi, thank you for looking into this.

I apologize if the configuration wasn't clear in the initial report. Here are the complete configuration files and a summary of the debugging steps we've already taken.

Configuration Files

This setup uses the newer OAUTH_CONFIG environment variable, as discussed in other community threads, instead of the deprecated individual OIDC_* variables.

My docker-compose.yml:

version: '3.8'

services:
  open-webui:
    image: ghcr.io/open-webui/open-webui:v0.6.15
    container_name: my-webui
    ports:
      - "8080:8080"
    env_file:
      - ./.env
    volumes:
      - open-webui-data:/app/backend/data
    restart: unless-stopped

volumes:
  open-webui-data:

My .env file:
OAUTH_CONFIG=[{"oidc_enabled":true,"display_name":"Login with Solann ID","client_id":"open-webui-client","client_secret":"**********","well_known_url":"[https://solannsoftware.com/.well-known/openid-configuration](https://solannsoftware.com/.well-known/openid-configuration)","scopes":"openid profile email roles"}]

Summary of Debugging Steps
We have already performed extensive debugging and can confirm this is not a simple configuration or network issue.

✅ Environment Variables are Loaded Correctly: I have run docker exec my-webui env and confirmed that the OAUTH_CONFIG JSON string is present and correct inside the running container.

✅ Network Connectivity is Successful: I have run curl -v https://solannsoftware.com/.well-known/openid-configuration from inside the container (docker exec -it my-webui /bin/sh). The command returns HTTP/2 200 OK and SSL certificate verify ok.. This proves the container has full, successful network and SSL/TLS connectivity to the OIDC provider.

🔴 The Problem Persists: Despite the two points above, the application's /api/config endpoint still returns {"oauth": {"providers": {}}} and the OIDC login button does not appear.

The Core Question
Given that the container receives the correct configuration and can successfully communicate with the OIDC provider, could there be any internal logic, dependency, or bug in version v0.6.15 that would cause it to silently fail to parse or activate the OAUTH_CONFIG variable?

Please let me know what other information or logs I can provide to help diagnose this further. Thank you!


Note: I am using ABP.io

@nguyendev commented on GitHub (Jul 6, 2025): Hi, thank you for looking into this. I apologize if the configuration wasn't clear in the initial report. Here are the complete configuration files and a summary of the debugging steps we've already taken. ### Configuration Files This setup uses the newer `OAUTH_CONFIG` environment variable, as discussed in other community threads, instead of the deprecated individual `OIDC_*` variables. **My `docker-compose.yml`:** ```yaml version: '3.8' services: open-webui: image: ghcr.io/open-webui/open-webui:v0.6.15 container_name: my-webui ports: - "8080:8080" env_file: - ./.env volumes: - open-webui-data:/app/backend/data restart: unless-stopped volumes: open-webui-data: My .env file: OAUTH_CONFIG=[{"oidc_enabled":true,"display_name":"Login with Solann ID","client_id":"open-webui-client","client_secret":"**********","well_known_url":"[https://solannsoftware.com/.well-known/openid-configuration](https://solannsoftware.com/.well-known/openid-configuration)","scopes":"openid profile email roles"}] Summary of Debugging Steps We have already performed extensive debugging and can confirm this is not a simple configuration or network issue. ✅ Environment Variables are Loaded Correctly: I have run docker exec my-webui env and confirmed that the OAUTH_CONFIG JSON string is present and correct inside the running container. ✅ Network Connectivity is Successful: I have run curl -v https://solannsoftware.com/.well-known/openid-configuration from inside the container (docker exec -it my-webui /bin/sh). The command returns HTTP/2 200 OK and SSL certificate verify ok.. This proves the container has full, successful network and SSL/TLS connectivity to the OIDC provider. 🔴 The Problem Persists: Despite the two points above, the application's /api/config endpoint still returns {"oauth": {"providers": {}}} and the OIDC login button does not appear. The Core Question Given that the container receives the correct configuration and can successfully communicate with the OIDC provider, could there be any internal logic, dependency, or bug in version v0.6.15 that would cause it to silently fail to parse or activate the OAUTH_CONFIG variable? Please let me know what other information or logs I can provide to help diagnose this further. Thank you! Note: I am using ABP.io

GiteaMirror referenced this issue

2026-04-20 00:30:47 -05:00

[GH-ISSUE #17476] feat: Improve first-screen loading speed and reduce resource loading size. #18301

GiteaMirror referenced this issue

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

[PR #17595] [CLOSED] feat: Dynamically load Overview.svelte to improve first-screen loading speed (-470KB) #24482

GiteaMirror referenced this issue

2026-04-25 07:43:12 -05:00

[GH-ISSUE #17476] feat: Improve first-screen loading speed and reduce resource loading size. #33830

GiteaMirror referenced this issue

2026-04-25 12:31:46 -05:00

[PR #17595] [CLOSED] feat: Dynamically load Overview.svelte to improve first-screen loading speed (-470KB) #40112