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
Currently, there is a lack of support for third-party login and permission group management integrated with authentication systems such as Casdoor. Additionally, there is no clear mechanism to pass user permission group information to backend model requests, which limits fine-grained access control and permission verification for model API calls.
Desired Solution you'd like
Add support for third-party login and authentication integration with Casdoor and similar identity providers.
Implement configurable permission group / role management for user access control.
Support passing user permission group information to backend model inference requests for further permission validation.
Please let me know if these features are already available; if not, kindly consider adding them.
Alternatives Considered
No response
Additional Context
No response
Originally created by @ShawnXsw on GitHub (Apr 13, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23664
### 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
Currently, there is a lack of support for third-party login and permission group management integrated with authentication systems such as Casdoor. Additionally, there is no clear mechanism to pass user permission group information to backend model requests, which limits fine-grained access control and permission verification for model API calls.
### Desired Solution you'd like
1. Add support for third-party login and authentication integration with Casdoor and similar identity providers.
2. Implement configurable permission group / role management for user access control.
3. Support passing user permission group information to backend model inference requests for further permission validation.
Please let me know if these features are already available; if not, kindly consider adding them.
### Alternatives Considered
_No response_
### Additional Context
_No response_
@pr-validator-bot commented on GitHub (Apr 13, 2026):
⚠️ Invalid Issue Title
Hey @ShawnXsw, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:" or "feat:") make it difficult for volunteer contributors to understand and triage issues.
Please update the title to reflect the content of your issue.
⚠️ Missing Issue Title Prefix
@ShawnXsw, your issue title is missing a prefix (e.g., bug:, feat:, docs:).
Please update your issue title to include one of the following prefixes:
bug: Bug report or error you've encountered
feat: Feature request or enhancement suggestion
docs: Documentation issue or improvement request
question: Question about usage or functionality
help: Request for help or support
Example: bug: Login fails when using special characters in password
<!-- gh-comment-id:4236101825 -->
@pr-validator-bot commented on GitHub (Apr 13, 2026):
# ⚠️ Invalid Issue Title
Hey @ShawnXsw, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:" or "feat:") make it difficult for volunteer contributors to understand and triage issues.
Please update the title to reflect the content of your issue.
---
# ⚠️ Missing Issue Title Prefix
@ShawnXsw, your issue title is missing a prefix (e.g., `bug:`, `feat:`, `docs:`).
Please update your issue title to include one of the following prefixes:
- **bug**: Bug report or error you've encountered
- **feat**: Feature request or enhancement suggestion
- **docs**: Documentation issue or improvement request
- **question**: Question about usage or functionality
- **help**: Request for help or support
Example: `bug: Login fails when using special characters in password`
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 @ShawnXsw on GitHub (Apr 13, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23664
Check Existing Issues
Verify Feature Scope
Problem Description
Currently, there is a lack of support for third-party login and permission group management integrated with authentication systems such as Casdoor. Additionally, there is no clear mechanism to pass user permission group information to backend model requests, which limits fine-grained access control and permission verification for model API calls.
Desired Solution you'd like
Please let me know if these features are already available; if not, kindly consider adding them.
Alternatives Considered
No response
Additional Context
No response
@pr-validator-bot commented on GitHub (Apr 13, 2026):
⚠️ Invalid Issue Title
Hey @ShawnXsw, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:" or "feat:") make it difficult for volunteer contributors to understand and triage issues.
Please update the title to reflect the content of your issue.
⚠️ Missing Issue Title Prefix
@ShawnXsw, your issue title is missing a prefix (e.g.,
bug:,feat:,docs:).Please update your issue title to include one of the following prefixes:
Example:
bug: Login fails when using special characters in password