[PR #16248] [CLOSED] feat: Allow sign-in with username #127737

Closed
opened 2026-05-21 09:50:56 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/16248
Author: @silentoplayz
Created: 8/3/2025
Status: ❌ Closed

Base: dev ← Head: login-with-username


📝 Commits (1)

  • 365a0f9 feat: Allow sign-in with username or email

📊 Changes

7 files changed (+113 additions, -44 deletions)

View changed files

📝 backend/open_webui/constants.py (+2 -1)
📝 backend/open_webui/models/auths.py (+7 -4)
📝 backend/open_webui/models/users.py (+19 -0)
📝 backend/open_webui/routers/auths.py (+8 -5)
📝 backend/open_webui/utils/oauth.py (+8 -8)
📝 src/lib/apis/auths/index.ts (+8 -3)
📝 src/routes/auth/+page.svelte (+61 -23)

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.

Before submitting, make sure you've checked the following:

  • Target branch: Please verify that the pull request targets the dev branch.
  • Description: Provide a concise description of the changes made in this pull request.
  • Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
  • Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
  • Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
  • Testing: Have you written and run sufficient tests to validate the changes?
  • Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
  • Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
    • 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

Changelog Entry

Description

  • This pull request introduces the ability for users to sign in with either their username or their email address. It also improves the error messaging on the sign-in page to be more specific to the login method used.

Added

  • Users can now sign in with their username in addition to their email address.
  • A toggle has been added to the login page to switch between signing in with an email or a username.
  • New error message constants for invalid username and email credentials.

Changed

  • The sign-in form now sends the login method (email or username) to the backend.
  • The backend now uses the login method to return a more specific error message if the credentials are invalid.
  • The sign-in logic is now case-insensitive for both usernames and emails.

Deprecated

  • ERROR_MESSAGES.INVALID_CRED has been deprecated in favor of ERROR_MESSAGES.INVALID_EMAIL_CRED and ERROR_MESSAGES.INVALID_USERNAME_CRED.

Fixed

  • The error message for invalid credentials is now more specific to the login method.

Additional Information

  • This pull request addresses the feature request to allow sign-in with a username.

Screenshots or Videos

image image

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/16248 **Author:** [@silentoplayz](https://github.com/silentoplayz) **Created:** 8/3/2025 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `login-with-username` --- ### 📝 Commits (1) - [`365a0f9`](https://github.com/open-webui/open-webui/commit/365a0f960b4553c91feb3d2256cc766fe524b793) feat: Allow sign-in with username or email ### 📊 Changes **7 files changed** (+113 additions, -44 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/constants.py` (+2 -1) 📝 `backend/open_webui/models/auths.py` (+7 -4) 📝 `backend/open_webui/models/users.py` (+19 -0) 📝 `backend/open_webui/routers/auths.py` (+8 -5) 📝 `backend/open_webui/utils/oauth.py` (+8 -8) 📝 `src/lib/apis/auths/index.ts` (+8 -3) 📝 `src/routes/auth/+page.svelte` (+61 -23) </details> ### 📄 Description # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) and describe your changes before submitting a pull request. **Before submitting, make sure you've checked the following:** - [X] **Target branch:** Please verify that the pull request targets the `dev` branch. - [X] **Description:** Provide a concise description of the changes made in this pull request. - [X] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [X] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources? - [X] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [X] **Testing:** Have you written and run sufficient tests to validate the changes? - [X] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [X] **Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **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 # Changelog Entry ### Description - This pull request introduces the ability for users to sign in with either their username or their email address. It also improves the error messaging on the sign-in page to be more specific to the login method used. ### Added - Users can now sign in with their username in addition to their email address. - A toggle has been added to the login page to switch between signing in with an email or a username. - New error message constants for invalid username and email credentials. ### Changed - The sign-in form now sends the login method (email or username) to the backend. - The backend now uses the login method to return a more specific error message if the credentials are invalid. - The sign-in logic is now case-insensitive for both usernames and emails. ### Deprecated - `ERROR_MESSAGES.INVALID_CRED` has been deprecated in favor of `ERROR_MESSAGES.INVALID_EMAIL_CRED` and `ERROR_MESSAGES.INVALID_USERNAME_CRED`. ### Fixed - The error message for invalid credentials is now more specific to the login method. ### Additional Information - This pull request addresses the feature request to allow sign-in with a username. ### Screenshots or Videos <img width="523" height="334" alt="image" src="https://github.com/user-attachments/assets/c41da606-4134-46ce-a904-b62fb102c2ba" /> <img width="1578" height="667" alt="image" src="https://github.com/user-attachments/assets/f4856489-0de6-49e9-8f12-a5b483b9f6f2" /> ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-05-21 09:50:56 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#127737