# auth0 password strength error on signup: policy configuration

## TL;DR

The Auth0 password policy rejects the chosen password, but the signup form does not explain the rules, so users fail blindly. Either relax the policy to match what the form allows, or surface the exact requirements in the form. The policy and the UX must agree.

```text
PasswordStrengthError: Password is too weak (Auth0)
```

## Steps

1. Read the active password policy in the Auth0 dashboard (database connection settings).
   Expected: The actual rules are known.

2. Compare against what the signup form tells the user.
   Expected: The gap is visible.

3. Align them: update the form to show the real requirements, or adjust the policy to the product's decision.
   Expected: Policy and UX agree.

4. Test the signup flow with passwords at the boundary (just strong enough, just too weak).
   Expected: The behavior matches the stated rules.

5. Consider breached-password detection as the real protection; length rules alone are weak.
   Expected: The policy is meaningful, not just strict.

## When to use

- Auth0 rejects passwords at signup
- the form does not show the rules
- the policy changed recently

## When not to use

- the error is a different Auth0 error (read it)
- the policy is intentionally strict (then fix the form, not the policy)
- using social login (no password involved)

## Tool compatibility

- Auth0 database connections
- password policies

## Variant phrasings

- "auth0 password strength error signup"
- "auth0 password too weak"
- "auth0 password policy configuration"

## Why it happens

Auth0 enforces the connection's password policy server-side, but the signup form is your code. When they disagree, users fail with a generic error and no guidance. The policy is doing its job; the UX is not doing its. Either side can move, but they must meet.

## Edge cases

- the policy applies per database connection; check you are reading the right one
- breached-password detection catches what strength rules miss
- passwordless options sidestep the whole problem for many products

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_pCDr4oD_wHeHMstQ_oEL1w