Error Message Displayed When Setting New Password to Existing Password

[shige]

Self Checks

• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.

Cloud or Self Hosted

Cloud

Version (only for Self Hosted)

No response

Steps to reproduce

An error message is displayed when attempting to set a new password on the "Set new password" screen that is identical to the user's existing password.

1. Navigate to the "Reset your password" screen and enter your account information.
2. Open the "Set new password" screen using the link provided in the email.
3. Enter your existing password in the "New Password" field.
4. Click the "Verify" button.

Expected Behavior

The system should either:

• Display a validation error message indicating that the new password cannot be the same as the old password,
• Or successfully update the password if the application allows it.

Actual Behavior

The following error message is displayed:

Authentication Error
An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.

Additional Context

This behavior is unexpected and suggests a problem with either password validation or the password update process. The vague nature of the error message doesn't provide enough information to the user regarding the specific issue. It should be either rejected during the validation process or successfully changed.

[gentamura]

@shige I have tried to reproduce it and it seems to be fixed.
I am confirming this with commit 36eb4cb.

[shige]

@gentamura

After QA, I'm still encountering the error from #301 (comment).

The following error log was output in the Vercel Logs:

⨯ Error: No session returned
    at f (.next/server/app/(auth)/password_reset/confirm/route.js:1:7519)
    at async (.next/server/chunks/8034.js:14:50046)

However, since it seems to be difficult to reproduce, it's okay to un-assign for now.

Thank you!