github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-09 23:35:09 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

issue: LDAP still requires TLS certificate path #4701

New Issue
Closed
opened 2025-11-11 16:01:02 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-11 16:01:02 -06:00
Owner
Copy Link

Originally created by @zenorbi on GitHub (Apr 3, 2025).

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

v0.6.0

Ollama Version (if applicable)

No response

Operating System

Debian 12

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 listed steps to reproduce the bug in detail.

Expected Behavior

The settings page should accept and apply empty LDAP TLS certificate path as fixed in https://github.com/open-webui/open-webui/issues/11294

Actual Behavior

The form submits but I get an error toast: "TLS is enabled but certificate file path is missing"

Settings are not saved.

Steps to Reproduce

  1. Optional: Have an LDAP server with certificate that is trusted by default
  2. Set the LDAP config on the admin page
    1. Enable TLS
    2. Don't set a TLS certificate path
  3. Click Save

Logs & Screenshots

Image

openwebui-1  | 2025-04-03 15:04:16.110 | INFO     | open_webui.config:save:242 - Saving 'WEBHOOK_URL' to the database - {}
openwebui-1  | 2025-04-03 15:04:16.119 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 131.152.136.233:0 - "POST /api/webhook HTTP/1.1" 200 - {}
openwebui-1  | 2025-04-03 15:04:16.128 | INFO     | open_webui.config:save:242 - Saving 'SHOW_ADMIN_DETAILS' to the database - {}
openwebui-1  | 2025-04-03 15:04:16.133 | INFO     | open_webui.config:save:242 - Saving 'WEBUI_URL' to the database - {}
openwebui-1  | 2025-04-03 15:04:16.138 | INFO     | open_webui.config:save:242 - Saving 'ENABLE_SIGNUP' to the database - {}
openwebui-1  | 2025-04-03 15:04:16.143 | INFO     | open_webui.config:save:242 - Saving 'ENABLE_API_KEY' to the database - {}
openwebui-1  | 2025-04-03 15:04:16.148 | INFO     | open_webui.config:save:242 - Saving 'ENABLE_API_KEY_ENDPOINT_RESTRICTIONS' to the database - {}
openwebui-1  | 2025-04-03 15:04:16.152 | INFO     | open_webui.config:save:242 - Saving 'API_KEY_ALLOWED_ENDPOINTS' to the database - {}
openwebui-1  | 2025-04-03 15:04:16.158 | INFO     | open_webui.config:save:242 - Saving 'ENABLE_CHANNELS' to the database - {}
openwebui-1  | 2025-04-03 15:04:16.162 | INFO     | open_webui.config:save:242 - Saving 'DEFAULT_USER_ROLE' to the database - {}
openwebui-1  | 2025-04-03 15:04:16.167 | INFO     | open_webui.config:save:242 - Saving 'JWT_EXPIRES_IN' to the database - {}
openwebui-1  | 2025-04-03 15:04:16.171 | INFO     | open_webui.config:save:242 - Saving 'ENABLE_COMMUNITY_SHARING' to the database - {}
openwebui-1  | 2025-04-03 15:04:16.177 | INFO     | open_webui.config:save:242 - Saving 'ENABLE_MESSAGE_RATING' to the database - {}
openwebui-1  | 2025-04-03 15:04:16.181 | INFO     | open_webui.config:save:242 - Saving 'ENABLE_USER_WEBHOOKS' to the database - {}
openwebui-1  | 2025-04-03 15:04:16.186 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 131.152.136.233:0 - "POST /api/v1/auths/admin/config HTTP/1.1" 200 - {}
openwebui-1  | 2025-04-03 15:04:16.198 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 131.152.136.233:0 - "POST /api/v1/auths/admin/config/ldap/server HTTP/1.1" 400 - {}
openwebui-1  | 2025-04-03 15:04:16.214 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 131.152.136.233:0 - "GET /api/config HTTP/1.1" 200 - {}

Additional Information

We get certificates from Let's Encrypt for our LDAP, it shouldn't be mandatory to set a certificate path.

Originally created by @zenorbi on GitHub (Apr 3, 2025). ### 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 v0.6.0 ### Ollama Version (if applicable) _No response_ ### Operating System Debian 12 ### 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 listed steps to reproduce the bug in detail. ### Expected Behavior The settings page should accept and apply empty LDAP TLS certificate path as fixed in https://github.com/open-webui/open-webui/issues/11294 ### Actual Behavior The form submits but I get an error toast: "TLS is enabled but certificate file path is missing" Settings are not saved. ### Steps to Reproduce 1. Optional: Have an LDAP server with certificate that is trusted by default 2. Set the LDAP config on the admin page 1. Enable TLS 2. Don't set a TLS certificate path 3. Click Save ### Logs & Screenshots ![Image](https://github.com/user-attachments/assets/f217cb04-3553-45ca-92aa-434642870d90) ``` openwebui-1 | 2025-04-03 15:04:16.110 | INFO | open_webui.config:save:242 - Saving 'WEBHOOK_URL' to the database - {} openwebui-1 | 2025-04-03 15:04:16.119 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 131.152.136.233:0 - "POST /api/webhook HTTP/1.1" 200 - {} openwebui-1 | 2025-04-03 15:04:16.128 | INFO | open_webui.config:save:242 - Saving 'SHOW_ADMIN_DETAILS' to the database - {} openwebui-1 | 2025-04-03 15:04:16.133 | INFO | open_webui.config:save:242 - Saving 'WEBUI_URL' to the database - {} openwebui-1 | 2025-04-03 15:04:16.138 | INFO | open_webui.config:save:242 - Saving 'ENABLE_SIGNUP' to the database - {} openwebui-1 | 2025-04-03 15:04:16.143 | INFO | open_webui.config:save:242 - Saving 'ENABLE_API_KEY' to the database - {} openwebui-1 | 2025-04-03 15:04:16.148 | INFO | open_webui.config:save:242 - Saving 'ENABLE_API_KEY_ENDPOINT_RESTRICTIONS' to the database - {} openwebui-1 | 2025-04-03 15:04:16.152 | INFO | open_webui.config:save:242 - Saving 'API_KEY_ALLOWED_ENDPOINTS' to the database - {} openwebui-1 | 2025-04-03 15:04:16.158 | INFO | open_webui.config:save:242 - Saving 'ENABLE_CHANNELS' to the database - {} openwebui-1 | 2025-04-03 15:04:16.162 | INFO | open_webui.config:save:242 - Saving 'DEFAULT_USER_ROLE' to the database - {} openwebui-1 | 2025-04-03 15:04:16.167 | INFO | open_webui.config:save:242 - Saving 'JWT_EXPIRES_IN' to the database - {} openwebui-1 | 2025-04-03 15:04:16.171 | INFO | open_webui.config:save:242 - Saving 'ENABLE_COMMUNITY_SHARING' to the database - {} openwebui-1 | 2025-04-03 15:04:16.177 | INFO | open_webui.config:save:242 - Saving 'ENABLE_MESSAGE_RATING' to the database - {} openwebui-1 | 2025-04-03 15:04:16.181 | INFO | open_webui.config:save:242 - Saving 'ENABLE_USER_WEBHOOKS' to the database - {} openwebui-1 | 2025-04-03 15:04:16.186 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 131.152.136.233:0 - "POST /api/v1/auths/admin/config HTTP/1.1" 200 - {} openwebui-1 | 2025-04-03 15:04:16.198 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 131.152.136.233:0 - "POST /api/v1/auths/admin/config/ldap/server HTTP/1.1" 400 - {} openwebui-1 | 2025-04-03 15:04:16.214 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 131.152.136.233:0 - "GET /api/config HTTP/1.1" 200 - {} ``` ### Additional Information We get certificates from Let's Encrypt for our LDAP, it shouldn't be mandatory to set a certificate path.
GiteaMirror added the bug label 2025-11-11 16:01:02 -06:00
GiteaMirror commented 2025-11-11 16:01:03 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Apr 3, 2025):

Most likely addressed with a1f3300767 in dev, testing wanted here!

@tjbck commented on GitHub (Apr 3, 2025): Most likely addressed with a1f3300767898df33c6ebcb002b7ba6060353994 in dev, testing wanted here!
GiteaMirror commented 2025-11-11 16:01:03 -06:00
Author
Owner
Copy Link

@zenorbi commented on GitHub (Apr 4, 2025):

I can confirm that the issue is fixed when I use the dev branch (v0.6.0 + commit be20e6dec0). Thank you for the fix!

@zenorbi commented on GitHub (Apr 4, 2025): I can confirm that the issue is fixed when I use the dev branch (v0.6.0 + commit be20e6dec038d4066fa1400ffe6a3053ad3f7c6c). Thank you for the fix!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#4701
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?