[Bug] Inconsistent Password Validation Rule in Signup and Signin

[KokaChernov]

Describe the bug "Password must contain at least one alphabet" in local deployment.

To Reproduce Steps to reproduce the behavior:

1. Deploy agenta locally
2. Login for the first time with the "123456789" password. Observe system is working as expected.
3. Log out
4. Try logging in using the same "123456789" password.

Expected behavior Default user is able to login

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Browser Chrome/Edge

---

[dosubot[bot]]

Hi @KokaChernov! I'm Dosu and I’m helping the agenta team.

This issue is caused by inconsistent password validation logic in Agenta's local deployment. When you create the first user, the system may allow a password with only digits (like "123456789"), but on subsequent logins, the backend enforces a rule requiring at least one alphabet character in the password. This mismatch leads to the error you’re seeing.

There are no existing tickets or discussions directly addressing this bug, and recent code changes do not mention password validation fixes. The relevant validation is likely enforced in the authentication backend, possibly in files like auth_router.py or user management services, and may differ between user creation and login flows.

As a workaround, use a password that includes at least one alphabet character when creating your initial user. If you’re locked out, you may need to reset the user database or redeploy with a compliant password. For reference on initial user creation and related issues, see this discussion and this issue.

It may be helpful for maintainers to review and unify password validation rules for both signup and login to prevent this inconsistency.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}