Password Validation Inconsistency
This is a known behavior difference between sign-in and reset password flows. The password validation error messages work differently in these contexts.
Why This Happens
1. Sign-in flows validate passwords client-side using the password component, showing "Value does not comply with requirements"
2. Reset password flows use server-side validation that returns generic error messages like "Failed to update user password"
Solutions
1.
Customize error handling in your reset password flow
- Use error handling options in your flow to catch password policy violations
- Configure custom error messages for password policy failures
2.
Add client-side validation to reset password screens
- Use the "new password" input component with policy previewer enabled
- This shows password requirements before submission
The documentation covers customizing flow errors and password components, but doesn't specifically address this validation message inconsistency between flows. I'd recommend adding client-side validation to your reset password screen and confirming the exact error handling approach with Descope support.
Password Component | Descope Documentation
Customizing Flow Errors | Descope Documentation