Password reset flow in Firebase - Step-by-Step Execution

Process Flow - Password reset flow

User requests password reset

↓

System sends reset email with link

↓

User clicks link and opens reset page

↓

User enters new password

↓

System verifies and updates password

↓

User receives confirmation

↓

END

The flow starts when the user requests a password reset, then the system sends an email with a reset link. The user clicks the link, enters a new password, and the system updates it, confirming success.

Execution Sample

Firebase

firebase.auth().sendPasswordResetEmail(email)
  .then(() => {
    console.log('Reset email sent');
  })
  .catch(error => {
    console.error(error);
  });

This code sends a password reset email to the user and logs success or error.

Process Table

Step	Action	Input/Condition	Result	Next Step
1	User requests password reset	User enters email	System receives request	Send reset email
2	System sends reset email	Email valid?	Email sent successfully	Wait for user to click link
3	User clicks reset link	Link valid and not expired?	Reset page opens	User enters new password
4	User submits new password	Password meets criteria?	Password updated in system	Send confirmation
5	System sends confirmation	Update successful	User notified of success	END

💡 Process ends after user receives confirmation of password reset.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
email	undefined	[e-mail]	[e-mail]	[e-mail]	[e-mail]	[e-mail]
resetLinkSent	false	false	true	true	true	true
linkValid	false	false	true	true	true	true
newPassword	undefined	undefined	undefined	undefined	userNewPass123	userNewPass123
passwordUpdated	false	false	false	false	true	true
confirmationSent	false	false	false	false	false	true

Key Moments - 3 Insights

Why does the system check if the reset link is valid before allowing password change?

The system must ensure the link is valid and not expired to prevent unauthorized password changes, as shown in step 3 of the execution_table.

What happens if the user enters a password that doesn't meet criteria?

The system will not update the password and will prompt the user to enter a valid password, preventing progression past step 4 in the execution_table.

Why is confirmation sent after password update?

Sending confirmation assures the user that the password reset was successful, as indicated in step 5 of the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does the system verify the reset link validity?

A Step 3

B Step 2

C Step 4

D Step 5

💡 Hint

Check the 'Input/Condition' column for link validity in the execution_table.

According to variable_tracker, what is the value of 'passwordUpdated' after step 4?

A undefined

B true

C false

D null

💡 Hint

Look at the 'passwordUpdated' row under 'After Step 4' in variable_tracker.

If the user never clicks the reset link, which variable remains false according to variable_tracker?

A resetLinkSent

B confirmationSent

C linkValid

D newPassword

💡 Hint

Consider the 'linkValid' variable and when it changes in variable_tracker.

Concept Snapshot

Password Reset Flow:
1. User requests reset by email.
2. System sends reset link email.
3. User clicks link; system verifies it.
4. User enters new password; system updates it.
5. System confirms success to user.
Always verify link validity and password criteria.

Full Transcript

The password reset flow begins when a user requests a reset by providing their email. The system sends a reset email containing a link. When the user clicks this link, the system checks if the link is valid and not expired. If valid, the user is prompted to enter a new password. The system verifies the password meets criteria and updates it. Finally, the system sends a confirmation to the user indicating the reset was successful. Variables such as 'resetLinkSent', 'linkValid', and 'passwordUpdated' track the process state. Key moments include link validation to prevent unauthorized resets and confirmation to assure the user. This flow ensures security and user clarity.