issue: Using ADFS and OIDC breaks the OIDC flow #4320

New Issue

GiteaMirror · 2025-11-11T15:51:28-06:00

GiteaMirror commented

2025-11-11 15:51:28 -06:00

Originally created by @icsy7867 on GitHub (Mar 8, 2025).

Check Existing Issues

I have searched the existing issues and discussions.

Installation Method

Docker

Open WebUI Version

v0.5.20

Ollama Version (if applicable)

No response

Operating System

Container in kubernetes

Browser (if applicable)

N.A

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 checked the browser console logs.
I have checked the Docker container logs.
I have listed steps to reproduce the bug in detail.

Expected Behavior

This isnt really an issue with open-webui, but I wanted to make a note of it. I didnt realize you were using oauth2-proxy on the backend (I love this container BTW...)

https://oauth2-proxy.github.io/oauth2-proxy/configuration/providers/adfs

Note: When using the ADFS Auth provider with nginx and the cookie session store you may find the cookie is too large and doesn't get passed through correctly. Increasing the proxy_buffer_size in nginx or implementing the [redis session storage](https://oauth2-proxy.github.io/oauth2-proxy/configuration/session_storage#redis-storage) should resolve this.

I ultimately just added redis, which was pretty easy to do. However, without redis, I just get failed OAUTH attempts in my console, 403 issues, and other oddities. The proxy buffer is basically getting cut off so oauth2-proxy is only receiving part of the response.

SO if you are coming from the magical land of ADFS, make sure to increase your proxy buffer size if using nginx (Either via and ingress annotation in kubernetes, or via and nginx config) or implement redis!

I am working now with a seperate oauth2-proxy and redis container, and it is working quite well. The only thing I might suggest is to add ENV variables for connecting to a redis backend or something.

Actual Behavior

N/A

Steps to Reproduce

Run ADFS, create an OIDC integration, watch it fail repeatedly.

Logs & Screenshots

Not really applicable. I just wanted to share the information :D

Feel free to close.

Additional Information

No response

Originally created by @icsy7867 on GitHub (Mar 8, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Installation Method Docker ### Open WebUI Version v0.5.20 ### Ollama Version (if applicable) _No response_ ### Operating System Container in kubernetes ### Browser (if applicable) N.A ### 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 checked the browser console logs. - [x] I have checked the Docker container logs. - [x] I have listed steps to reproduce the bug in detail. ### Expected Behavior This isnt really an issue with open-webui, but I wanted to make a note of it. I didnt realize you were using oauth2-proxy on the backend (I love this container BTW...) https://oauth2-proxy.github.io/oauth2-proxy/configuration/providers/adfs ``` Note: When using the ADFS Auth provider with nginx and the cookie session store you may find the cookie is too large and doesn't get passed through correctly. Increasing the proxy_buffer_size in nginx or implementing the [redis session storage](https://oauth2-proxy.github.io/oauth2-proxy/configuration/session_storage#redis-storage) should resolve this. ``` I ultimately just added redis, which was pretty easy to do. However, without redis, I just get failed OAUTH attempts in my console, 403 issues, and other oddities. The proxy buffer is basically getting cut off so oauth2-proxy is only receiving part of the response. SO if you are coming from the magical land of ADFS, make sure to increase your proxy buffer size if using nginx (Either via and ingress annotation in kubernetes, or via and nginx config) or implement redis! I am working now with a seperate oauth2-proxy and redis container, and it is working quite well. The only thing I might suggest is to add ENV variables for connecting to a redis backend or something. ### Actual Behavior N/A ### Steps to Reproduce Run ADFS, create an OIDC integration, watch it fail repeatedly. ### Logs & Screenshots Not really applicable. I just wanted to share the information :D Feel free to close. ### Additional Information _No response_

GiteaMirror added the bug label 2025-11-11 15:51:28 -06:00

GiteaMirror closed this issue

2025-11-11 15:51:29 -06:00

GiteaMirror commented

2025-11-11 15:51:29 -06:00

@rgaricano commented on GitHub (Mar 9, 2025):

https://docs.openwebui.com/tutorials/integrations/redis#setting-up-redis
https://docs.openwebui.com/getting-started/env-configuration#redis

@rgaricano commented on GitHub (Mar 9, 2025): https://docs.openwebui.com/tutorials/integrations/redis#setting-up-redis https://docs.openwebui.com/getting-started/env-configuration#redis

GiteaMirror commented

2025-11-11 15:51:29 -06:00

@icsy7867 commented on GitHub (Mar 9, 2025):

Good information. But that sounds like it's used for managing websockets, I don't think the oauth2- proxy integration knows to use that as well?

@icsy7867 commented on GitHub (Mar 9, 2025): Good information. But that sounds like it's used for managing websockets, I don't think the oauth2- proxy integration knows to use that as well?

GiteaMirror referenced this issue

2026-04-19 20:15:53 -05:00

[GH-ISSUE #4320] In Hybrid Search, the file summary query does not work #13566

GiteaMirror referenced this issue

2026-04-25 03:32:41 -05:00

[GH-ISSUE #4320] In Hybrid Search, the file summary query does not work #29094

GiteaMirror referenced this issue

2026-05-05 13:23:04 -05:00

[GH-ISSUE #4320] In Hybrid Search, the file summary query does not work #52232

Sign in to join this conversation.