[GH-ISSUE #166] bug: Trusted Header auth not working #85

Open
opened 2026-10-18 14:02:47 +00:00 by bsakaguchi · 2 comments
Owner

Originally created by @jcbshw on GitHub (Jul 23, 2026).
Original GitHub issue: https://github.com/open-webui/computer/issues/166

I am unable to setup trusted header auth with computer. Already running fine with Open WebU, Authelia and Traefik.

After doing the initial setup, I modify config.toml with the following.

[auth]
mode = "trusted_header"
header = "Remote-User"
trusted_sources = ["172.16.2.2"]

The endpoint /api/auth always returns {"authenticated":false}.

Reviewing the code, I believe check_access needs to send remote_user_header github.com/open-webui/computer@3b0e0f8dc3/cptr/routers/auth.py (L57)

Though if that's added in then the following is returned AuthResult(user_id=None, username='<redacted>', role='user', exp=0) and it never enters the next block because user_id is None.

github.com/open-webui/computer@3b0e0f8dc3/cptr/routers/auth.py (L59)

Not sure what the correct fix is but that is my investigation so far.

Originally created by @jcbshw on GitHub (Jul 23, 2026). Original GitHub issue: https://github.com/open-webui/computer/issues/166 I am unable to setup trusted header auth with computer. Already running fine with Open WebU, Authelia and Traefik. After doing the initial setup, I modify config.toml with the following. ``` [auth] mode = "trusted_header" header = "Remote-User" trusted_sources = ["172.16.2.2"] ``` The endpoint /api/auth always returns {"authenticated":false}. Reviewing the code, I believe check_access needs to send remote_user_header https://github.com/open-webui/computer/blob/3b0e0f8dc384434a09d76bb9776e0511698eb2b4/cptr/routers/auth.py#L57 Though if that's added in then the following is returned `AuthResult(user_id=None, username='<redacted>', role='user', exp=0)` and it never enters the next block because user_id is None. https://github.com/open-webui/computer/blob/3b0e0f8dc384434a09d76bb9776e0511698eb2b4/cptr/routers/auth.py#L59 Not sure what the correct fix is but that is my investigation so far.
Author
Owner

@owui-terminator[bot] commented on GitHub (Jul 23, 2026):

⚠️ Missing Issue Title Prefix

@jcbshw, your issue title is missing a categorising prefix (e.g. bug:, feat:, docs:).

Please update the title to lead with one of:

  • bug: bug report or error
  • feat: feature request or enhancement
  • docs: documentation issue
  • question: usage question
  • help: support request

Example: bug: Login fails when the password contains special characters

<!-- gh-comment-id:5063388142 --> @owui-terminator[bot] commented on GitHub (Jul 23, 2026): # ⚠️ Missing Issue Title Prefix @jcbshw, your issue title is missing a categorising prefix (e.g. `bug:`, `feat:`, `docs:`). Please update the title to lead with one of: - **bug**: bug report or error - **feat**: feature request or enhancement - **docs**: documentation issue - **question**: usage question - **help**: support request Example: `bug: Login fails when the password contains special characters`
Author
Owner

@owui-terminator[bot] commented on GitHub (Jul 23, 2026):

🔍 Related Issues Found

I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:

  1. 🟣 #77 Openweb UI implementation not working properly
    This reports OpenWebUI integration behaving incorrectly even though the official web UI works, which is the same general auth/integration surface as trusted header login problems in cptr.
    by thgilciffart

  2. 🟣 #50 Gateway connection hangs in OpenWebUI
    This issue is about cptr/OpenWebUI gateway behavior and shows that integration-specific behavior can fail even when the standalone cptr app works, making it adjacent to auth flow issues in the computer component.
    by naqerl


💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.

This comment was generated automatically. React with 👍 if helpful, 👎 if not.

<!-- gh-comment-id:5063389816 --> @owui-terminator[bot] commented on GitHub (Jul 23, 2026): <!-- terminator-bot:related-issues-reply --> 🔍 **Related Issues Found** I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions: 1. 🟣 [#77](https://github.com/open-webui/computer/issues/77) **Openweb UI implementation not working properly** *This reports OpenWebUI integration behaving incorrectly even though the official web UI works, which is the same general auth/integration surface as trusted header login problems in cptr.* *by thgilciffart* 2. 🟣 [#50](https://github.com/open-webui/computer/issues/50) **Gateway connection hangs in OpenWebUI** *This issue is about cptr/OpenWebUI gateway behavior and shows that integration-specific behavior can fail even when the standalone cptr app works, making it adjacent to auth flow issues in the computer component.* *by naqerl* --- 💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead. *This comment was generated automatically.* React with 👍 if helpful, 👎 if not.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
open-webui/computer#85
No description provided.