I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.
Verify Feature Scope
I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
Problem Description
I've added Authentik as an OICD idp and it works pretty good with open-webui. I've also removed the login for, which results in an awkward black page:
Has there been some thought about this "edgecase" or is it just just pure coincidence? :)
Desired Solution you'd like
When the only way to intertact (e.g. there is no emergency-login form) is to ckick the button, get rid of it at all and just redirect directly to your oicd workflow starter like /oauth/oidc/login.
If you still want the user in the loop, show a short & small spinner indicating that you're connecting their idp (or something alike).
The first 1 btw look seemlessly when youve got a idps session already :)
Alternatives Considered
Workarounds exists that are tiny proxies just for adressing this mini problem:
Originally created by @jk779 on GitHub (May 3, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24325
### Check Existing Issues
- [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request.
### Verify Feature Scope
- [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
### Problem Description
I've added Authentik as an OICD idp and it works pretty good with open-webui. I've also removed the login for, which results in an awkward black page:
<img width="712" height="399" alt="Image" src="https://github.com/user-attachments/assets/c3793acf-793e-4ac2-85d0-5cd9ceffe361" />
Has there been some thought about this "edgecase" or is it just just pure coincidence? :)
### Desired Solution you'd like
1. **When the only way to intertact** (e.g. there is no emergency-login form) is to ckick the button, get rid of it at all and just redirect directly to your oicd workflow starter like `/oauth/oidc/login`.
2. If you still want the user in the loop, show a short & small spinner indicating that you're connecting their idp (or something alike).
The first 1 btw look seemlessly when youve got a idps session already :)
### Alternatives Considered
Workarounds exists that are tiny proxies just for adressing this mini problem:
```
location = /auth {
return 302 /oauth/oidc/login;
}
```
i', not a fan of that ;/
### Additional Context
_No response_
#18587issue: SSO authentication requests request loops by mohammeddanishrabbani · bug
💡 If this is a duplicate, consider closing it and adding details to the existing issue.
This comment was generated automatically. React with 👍 if helpful, 👎 if not.
<!-- gh-comment-id:4365091473 -->
@owui-terminator[bot] commented on GitHub (May 3, 2026):
🔍 **Similar Issues Found**
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
1. [#19182](https://github.com/open-webui/open-webui/issues/19182) **feat: SSO custom logout URI**
*by BikersDelight · `good first issue`*
2. [#19708](https://github.com/open-webui/open-webui/issues/19708) **feat: Keycloak authentication support**
*by fux-dev*
3. [#18924](https://github.com/open-webui/open-webui/issues/18924) **feat: Allow authorization code flow with SSO logins**
*by pllopis*
4. [#15239](https://github.com/open-webui/open-webui/issues/15239) **feat: Enable Oauth Popup flow**
*by Ardakilic*
5. [#18587](https://github.com/open-webui/open-webui/issues/18587) **issue: SSO authentication requests request loops**
*by mohammeddanishrabbani · `bug`*
---
💡 If this is a duplicate, consider closing it and adding details to the existing issue.
*This comment was generated automatically.* React with 👍 if helpful, 👎 if not.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @jk779 on GitHub (May 3, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24325
Check Existing Issues
Verify Feature Scope
Problem Description
I've added Authentik as an OICD idp and it works pretty good with open-webui. I've also removed the login for, which results in an awkward black page:
Has there been some thought about this "edgecase" or is it just just pure coincidence? :)
Desired Solution you'd like
When the only way to intertact (e.g. there is no emergency-login form) is to ckick the button, get rid of it at all and just redirect directly to your oicd workflow starter like
/oauth/oidc/login.If you still want the user in the loop, show a short & small spinner indicating that you're connecting their idp (or something alike).
The first 1 btw look seemlessly when youve got a idps session already :)
Alternatives Considered
Workarounds exists that are tiny proxies just for adressing this mini problem:
i', not a fan of that ;/
Additional Context
No response
@owui-terminator[bot] commented on GitHub (May 3, 2026):
🔍 Similar Issues Found
I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:
#19182 feat: SSO custom logout URI
by BikersDelight ·
good first issue#19708 feat: Keycloak authentication support
by fux-dev
#18924 feat: Allow authorization code flow with SSO logins
by pllopis
#15239 feat: Enable Oauth Popup flow
by Ardakilic
#18587 issue: SSO authentication requests request loops
by mohammeddanishrabbani ·
bug💡 If this is a duplicate, consider closing it and adding details to the existing issue.
This comment was generated automatically. React with 👍 if helpful, 👎 if not.