Why authentication identifies users in Firebase - Visual Breakdown

Process Flow - Why authentication identifies users

User enters credentials

↓

Firebase checks credentials

↓

User is [Access denied

↓

User gets access to app

User inputs credentials, Firebase verifies them, then either identifies the user or denies access.

Execution Sample

Firebase

firebase.auth().signInWithEmailAndPassword(email, password)
  .then(userCredential => {
    const user = userCredential.user;
    console.log('User ID:', user.uid);
  })
  .catch(error => console.error(error));

This code signs in a user with email and password, then logs the user's unique ID if successful.

Process Table

Step	Action	Input	Firebase Response	Result
1	User enters email and password	[e-mail], password123	N/A	Credentials sent to Firebase
2	Firebase checks credentials	[e-mail], password123	Credentials valid	User identified with UID
3	User ID retrieved	N/A	User object with UID	User ID logged: uid_abc123
4	Access granted	N/A	User authenticated	User can use app features
5	If credentials invalid	wrong email or password	Credentials invalid	Access denied, error shown

💡 Execution stops when user is either identified and authenticated or denied access due to invalid credentials.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
email	undefined	[e-mail]	[e-mail]	[e-mail]	[e-mail]
password	undefined	password123	password123	password123	password123
userCredential	undefined	undefined	{user: {...}}	{user: {...}}	{user: {...}}
user	undefined	undefined	undefined	{uid: 'uid_abc123'}	{uid: 'uid_abc123'}
error	undefined	undefined	undefined	undefined	undefined or error object if failed

Key Moments - 3 Insights

Why does Firebase need to check credentials before identifying the user?

Because only valid credentials prove the user is who they claim to be, as shown in execution_table step 2 where Firebase verifies credentials.

What happens if the credentials are wrong?

Firebase rejects the login attempt and denies access, as shown in execution_table step 5 where invalid credentials cause an error.

Why do we get a unique user ID after authentication?

The unique ID identifies the user securely in Firebase, allowing the app to recognize them, as shown in execution_table step 3.

Visual Quiz - 3 Questions

Look at the execution table, what is the Firebase response at step 2?

A User ID logged

B Credentials valid

C Access denied

D User enters credentials

💡 Hint

Check the 'Firebase Response' column in row for step 2.

At which step does the user get identified with a unique ID?

A Step 3

B Step 1

C Step 5

D Step 4

💡 Hint

Look for 'User ID logged' in the 'Result' column.

If the password is incorrect, which step shows the outcome?

A Step 2

B Step 3

C Step 5

D Step 4

💡 Hint

Find where 'Access denied' appears in the 'Result' column.

Concept Snapshot

Authentication means checking who a user is by verifying credentials.
Firebase compares entered email and password to stored data.
If valid, Firebase identifies user with a unique ID (UID).
If invalid, access is denied.
This process ensures only real users get access.

Full Transcript

Authentication identifies users by verifying their credentials. When a user enters their email and password, Firebase checks if these match stored records. If the credentials are correct, Firebase returns a unique user ID, confirming the user's identity. This ID lets the app recognize the user and grant access. If credentials are wrong, Firebase denies access and shows an error. This process protects the app by allowing only verified users.

Practice

1. What is the main purpose of authentication in Firebase?

easy

A. To store user data

B. To confirm the identity of a user

C. To speed up app loading

D. To design the app interface

Solution

1. Step 1: Understand authentication role

   Authentication is the process that confirms who a user is by checking their credentials.

2. Step 2: Differentiate from other functions

   Storing data, speeding up loading, or designing interfaces are not related to identifying users.

3. Final Answer:

   To confirm the identity of a user -> Option B

4. Quick Check:

   Authentication = Confirm identity [OK]

Hint: Authentication means checking who you are [OK]

Common Mistakes:

• Confusing authentication with data storage
• Thinking authentication speeds up apps
• Mixing authentication with design tasks

2. Which Firebase method is used to sign in a user with email and password?

easy

A. firebase.auth().signInWithEmailAndPassword()

B. firebase.auth().createUserWithEmailAndPassword()

C. firebase.auth().signOut()

D. firebase.auth().sendPasswordResetEmail()

Solution

1. Step 1: Identify sign-in method

   The method to sign in a user with email and password is signInWithEmailAndPassword().

2. Step 2: Differentiate from other methods

   createUserWithEmailAndPassword() creates a new user, signOut() logs out, and sendPasswordResetEmail() sends reset instructions.

3. Final Answer:

   firebase.auth().signInWithEmailAndPassword() -> Option A

4. Quick Check:

   Sign in = signInWithEmailAndPassword() [OK]

Hint: Sign in uses signInWithEmailAndPassword() method [OK]

Common Mistakes:

• Using createUserWithEmailAndPassword() to sign in
• Confusing signOut() with sign-in
• Mixing password reset with sign-in

3. What will the following Firebase code output if the user is not signed in?

firebase.auth().onAuthStateChanged(user => { if (user) { console.log('User ID:', user.uid); } else { console.log('No user signed in'); } });

medium

A. No user signed in

B. User ID: null

C. Error: user is null

D. User ID: undefined

Solution

1. Step 1: Understand onAuthStateChanged behavior

   This listener runs when the authentication state changes. If no user is signed in, the user parameter is null.

2. Step 2: Analyze the if-else condition

   If user is null (no signed-in user), the else block runs, printing 'No user signed in'.

3. Final Answer:

   No user signed in -> Option A

4. Quick Check:

   Null user triggers else message [OK]

Hint: Null user means no one signed in [OK]

Common Mistakes:

• Assuming user.uid exists when user is null
• Expecting an error instead of else message
• Confusing null with undefined

4. Identify the error in this Firebase authentication code snippet:

firebase.auth().signInWithEmailAndPassword(email, password).then(user => { console.log('Signed in:', user.uid); }).catch(error => { console.error(error.message); });

medium

A. The then callback receives a user object directly

B. The catch block should be before then

C. signInWithEmailAndPassword requires three arguments

D. The then callback receives a userCredential object, not user

Solution

1. Step 1: Check the promise return type

   signInWithEmailAndPassword returns a promise resolving to a userCredential object, not a user directly.

2. Step 2: Understand how to access user ID

   The user ID is accessed via userCredential.user.uid, so the code should use userCredential in the then callback.

3. Final Answer:

   The then callback receives a userCredential object, not user -> Option D

4. Quick Check:

   Then gets userCredential, not user [OK]

Hint: Then callback gets userCredential, access user inside it [OK]

Common Mistakes:

• Treating then argument as user directly
• Placing catch before then
• Passing wrong number of arguments

5. You want to restrict access to certain app features only to authenticated users. Which Firebase approach best identifies users to enforce this?

hard

A. Use anonymous sign-in without checking user identity

B. Store user data in Firestore without authentication

C. Use Firebase Authentication to sign in users and check their UID before access

D. Allow all users to access features without sign-in

Solution

1. Step 1: Understand access control needs

   Restricting features requires knowing who the user is, which Firebase Authentication provides by signing in users and giving unique IDs.

2. Step 2: Evaluate other options

   Storing data without authentication or allowing anonymous/no sign-in does not identify users, so access cannot be controlled securely.

3. Final Answer:

   Use Firebase Authentication to sign in users and check their UID before access -> Option C

4. Quick Check:

   Authentication + UID check = secure access control [OK]

Hint: Check user UID after sign-in to restrict access [OK]

Common Mistakes:

• Relying on data storage without authentication
• Using anonymous sign-in without identity checks
• Allowing access without sign-in