⚠️ Missing PR Title Prefix

@SCBionicle, your PR title is missing a prefix (e.g., feat:, fix:, docs:).

Please update your PR title to include one of the following prefixes:

• BREAKING CHANGE: Significant changes that may affect compatibility
• build: Changes that affect the build system or external dependencies
• ci: Changes to our continuous integration processes or workflows
• chore: Refactor, cleanup, or other non-functional code changes
• docs: Documentation update or addition
• feat: Introduces a new feature or enhancement to the codebase
• fix: Bug fix or error correction
• i18n: Internationalization or localization changes
• perf: Performance improvement
• refactor: Code restructuring for better maintainability, readability, or scalability
• style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
• test: Adding missing tests or correcting existing tests
• WIP: Work in progress, a temporary label for incomplete or ongoing work

Example: feat: Add new authentication method

👋 Welcome and Thank You for Contributing!

We appreciate you taking the time to submit a pull request to Open WebUI!

⚠️ Important: Testing Requirements

We've recently seen an increase in PRs that have significant issues:

• PRs that don't actually fix the bug they claim to fix
• PRs that don't implement the feature they describe
• PRs that break existing functionality
• PRs that are clearly AI-generated without proper testing being done by the author
• PRs that simply don't work as intended

These untested PRs consume significant time from maintainers and volunteer contributors who review and test PRs in their free time.
Time that could be spent testing other PRs or improving Open WebUI in other ways.

Before marking your PR as "Ready for Review":

Please explicitly confirm:

1. ✅ You have personally tested ALL changes in this PR
2. ✅ How you tested it (specific steps you took to verify it works)
3. ✅ Visual evidence where applicable (screenshots or videos showing the feature/fix working) - if applicable to your specific PR

If you're not certain your PR works exactly as intended, please leave it in DRAFT mode until you've thoroughly tested it.

Thank you for helping us maintain quality and respecting the time of our community! 🙏

⚠️ Warning: Possible Non-Atomic / Scope Creep PR Detected

Your PR was subjected to automated review by AI to determine if it could fall under Open WebUI's non-atomicity ruleset or scope creep.

This PR appears to contain multiple unrelated changes that could be split into separate pull requests.

🔍 AI Analysis Summary

Primary Intent: Enhance SCIM user provisioning by integrating OIDC 'sub' (externalId) mapping and improving user lookup logic.

Secondary Changes Detected:

• Refactoring 'get_user_by_email' to support case-insensitive lookups.
• Modifying 'insert_new_user' signature to support optional 'username' field.
• Updating SCIM filter logic to support 'emails eq' and a custom 'emails eq_ci' (case-insensitive) filter.
• Adding a helper method 'get_oauth_sub' to the UserModel.

Why Atomic PRs With Narrow Scopes Matter

Atomic PRs (single-purpose PRs) are:

• Easier to review - Reviewers can focus on one thing at a time
• Easier to test - Each change can be verified independently
• Easier to revert - If something breaks, we can revert just the problematic change
• Faster to merge - Smaller, focused PRs get reviewed and merged quicker

What Makes a PR Atomic / Narrow in Scope?

An atomic PR should contain one semantic change:

• ✅ Just one bug fix (even if it touches multiple files)
• ✅ Just one feature (even if it requires changes across multiple files)
• ✅ Just i18n/translation updates
• ✅ Just documentation updates
• ✅ Just refactoring of one specific thing
• ✅ Just one performance improvement

What To Do

This is an automated analysis. If you believe this assessment is incorrect and your PR is actually atomic (all changes serve one unified purpose), please explain in a comment below.

Consider splitting this PR into separate, focused pull requests. Each PR should address one specific thing.

For example, if you have a bug fix and a new feature, submit them as two separate PRs.

The modification to get_user_by_email and the addition of username to the user model was necessary to enable SCIM providers to link existing accounts to Open WebUI via Filtering and conflict detection.

Just noticed a bug with the External ID logic and am looking to fix it.

The force push is to rebase my branch on the dev branch rather than the main branch.

Fixed issue that manifested with provisioning accounts and fixed the filtering rules due to related syntax issues. This is ready for review again.

Addressed in dev