Choose a stronger account password.
Use the reset token produced by the existing OTP workflow to update your account credentials.
Create a new password.
Use at least eight characters with uppercase, lowercase, and numeric characters.
Account access should feel simple, even when the case is complex.
Visible requirements
Password quality rules update while you type.
Token validation
The existing reset token is sent back to the current backend endpoint.
Safe return
After a successful update, the user is sent to login.
A visible sequence from access to protected workspace.
Open reset link
Arrive with the reset token from OTP verification.
Choose password
Meet the displayed strength requirements.
Confirm match
Repeat the new password accurately.
Sign in again
Use the updated credentials on the login page.
Use strong credentials and keep account access private.
The frontend keeps the existing JWT-based backend flow. Your browser stores the current session token exactly as the existing application expects.
One account, several protection actions.
Once authenticated, users can move into the existing protection portal to submit cases, review records, and follow case progress.
Common access questions.
No. The frontend continues to call the same signup, login, OTP, password-reset, and account endpoints.
Need a fresh recovery code?
Restart the recovery flow if the reset token is missing or expired.