[PR #18200] [CLOSED] Final commit #40330

New Issue

GiteaMirror · 2026-04-25T12:49:18-05:00

GiteaMirror commented

2026-04-25 12:49:18 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/18200
Author: @Mohaneswari-Pugazenthi
Created: 10/9/2025
Status: ❌ Closed

Base: main ← Head: main

📝 Commits (1)

08f32ed Final commit

📊 Changes

6 files changed (+91 additions, -100 deletions)

View changed files

📝 backend/open_webui/alembic.ini (+9 -66)
📝 backend/open_webui/models/auths.py (+4 -3)
📝 backend/open_webui/models/users.py (+1 -2)
➕ backend/open_webui/test/apps/webui/alembic.ini (+59 -0)
📝 backend/requirements.txt (+1 -1)
📝 docker-compose.yaml (+17 -28)

📄 Description

It seems you are looking for a description to use in your Pull Request (PR) to submit your fix for the long password login issue in Open WebUI!

Here is a concise, professionally formatted description that addresses the problem, explains the solution, and references the original issue number, which is essential for a good PR.

Pull Request Description: Fix for Issue #18157
Title
Fix: #18157 Resolve Login Failure for Long Passwords by Increasing DB/API Limits

Description
This Pull Request addresses the critical regression introduced in v0.6.33 where users with long, secure passwords (≥64 characters) were unable to log in, receiving an incorrect "email or password are wrong" error. This also prevented users from setting a new long password.

The root cause was traced to overly restrictive length constraints on both the API validation model and the database schema.

🛠️ Changes Implemented:
Database Schema Fix (Auth Model):

Modified the password column in the Auth database model (likely in auth.py) from Column(Text) (or a short String) to Column(String(255)).

This ensures that modern, longer password hashes (like those generated from 128-character user passwords) fit and are saved correctly, resolving the login failure.

A corresponding Alembic migration file was generated to apply this schema change.

API Validation Fix:

Updated the UpdatePasswordForm and relevant Pydantic models (likely in auth.py and user.py) to explicitly set the new_password field with a max_length=255.

This prevents the API from rejecting long passwords during the user update process.

Verification
Tested locally by attempting to log in with an originally-failing long password, and successfully updating a password to a new length over 100 characters.

_{🔄 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/18200 **Author:** [@Mohaneswari-Pugazenthi](https://github.com/Mohaneswari-Pugazenthi) **Created:** 10/9/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (1) - [`08f32ed`](https://github.com/open-webui/open-webui/commit/08f32eda64d526d76e6f140c2e9b689e273910b4) Final commit ### 📊 Changes **6 files changed** (+91 additions, -100 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/alembic.ini` (+9 -66) 📝 `backend/open_webui/models/auths.py` (+4 -3) 📝 `backend/open_webui/models/users.py` (+1 -2) ➕ `backend/open_webui/test/apps/webui/alembic.ini` (+59 -0) 📝 `backend/requirements.txt` (+1 -1) 📝 `docker-compose.yaml` (+17 -28) </details> ### 📄 Description It seems you are looking for a description to use in your Pull Request (PR) to submit your fix for the long password login issue in Open WebUI! Here is a concise, professionally formatted description that addresses the problem, explains the solution, and references the original issue number, which is essential for a good PR. Pull Request Description: Fix for Issue #18157 Title Fix: #18157 Resolve Login Failure for Long Passwords by Increasing DB/API Limits Description This Pull Request addresses the critical regression introduced in v0.6.33 where users with long, secure passwords (≥64 characters) were unable to log in, receiving an incorrect "email or password are wrong" error. This also prevented users from setting a new long password. The root cause was traced to overly restrictive length constraints on both the API validation model and the database schema. 🛠️ Changes Implemented: Database Schema Fix (Auth Model): Modified the password column in the Auth database model (likely in auth.py) from Column(Text) (or a short String) to Column(String(255)). This ensures that modern, longer password hashes (like those generated from 128-character user passwords) fit and are saved correctly, resolving the login failure. A corresponding Alembic migration file was generated to apply this schema change. API Validation Fix: Updated the UpdatePasswordForm and relevant Pydantic models (likely in auth.py and user.py) to explicitly set the new_password field with a max_length=255. This prevents the API from rejecting long passwords during the user update process. Verification Tested locally by attempting to log in with an originally-failing long password, and successfully updating a password to a new length over 100 characters. --- <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-04-25 12:49:18 -05:00

GiteaMirror closed this issue

2026-04-25 12:49:41 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#40330