Session management in Supabase - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to initialize Supabase client with session persistence.

Supabase

const supabase = createClient(supabaseUrl, supabaseKey, { auth: { persistSession: [1] } });

Drag options to blanks, or click blank then click option'

Atrue

Bundefined

Cnull

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using false disables session persistence, so user sessions won't be saved.

Using null or undefined will cause errors or default behavior.

Setting persistSession to true enables session persistence in Supabase client.

2fill in blank

medium

Complete the code to get the current user session from Supabase auth.

Supabase

const session = await supabase.auth.[1]();

Drag options to blanks, or click blank then click option'

AgetSession

BgetUser

CfetchSession

DcurrentSession

Attempts:

3 left

💡 Hint

Common Mistakes

Using getUser returns user info, not the full session.

fetchSession and currentSession are not valid Supabase auth methods.

The method getSession() returns the current user session object.

3fill in blank

hard

Fix the error in the code to listen for auth state changes and update session.

Supabase

supabase.auth.onAuthStateChange((event, [1]) => { session = [1]; });

Drag options to blanks, or click blank then click option'

AsessionData

Bsession

CuserSession

DauthSession

Attempts:

3 left

💡 Hint

Common Mistakes

Using a variable name not matching the callback parameter causes reference errors.

Confusing event and session parameters.

The callback provides the new session as the second argument named session.

4fill in blank

hard

Fill both blanks to sign in a user with email and password using Supabase auth.

Supabase

const { data, error } = await supabase.auth.[1]({ email: userEmail, [2]: userPassword });

Drag options to blanks, or click blank then click option'

AsignInWithPassword

BsignUp

Cpassword

Dpass

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'signUp' instead of 'signInWithPassword' signs up a new user.

Using 'pass' instead of 'password' causes authentication failure.

Use signInWithPassword method and the key password to authenticate with email and password.

5fill in blank

hard

Fill all three blanks to refresh the session token manually using Supabase auth.

Supabase

const { data, error } = await supabase.auth.[1](); if (!error) { const newAccessToken = data.[2].[3]; }

Drag options to blanks, or click blank then click option'

ArefreshSession

Bsession

Caccess_token

DupdateSession

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'updateSession' is not a valid method.

Trying to access access token directly from data without session.

The method refreshSession() refreshes tokens. The new access token is accessed via data.session.access_token.

Practice

1. What does session management in Supabase primarily help you do?

easy

A. Keep track of who is logged in

B. Store database tables

C. Manage server resources

D. Create new users automatically

Solution

1. Step 1: Understand session management purpose

   Session management is about tracking user login status.

2. Step 2: Match with Supabase context

   Supabase uses sessions to know who is logged in or out.

3. Final Answer:

   Keep track of who is logged in -> Option A

4. Quick Check:

   Session management = tracking logged-in users [OK]

Hint: Sessions track logged-in users, not data or servers [OK]

Common Mistakes:

• Confusing session with database storage
• Thinking session manages server resources
• Assuming session creates users automatically

2. Which Supabase method is used to log a user in with email and password?

easy

A. signOut

B. getSession

C. signInWithPassword

D. createUser

Solution

1. Step 1: Identify login method

   Supabase uses signInWithPassword to log users in with email and password.

2. Step 2: Eliminate other options

   signOut logs out, getSession checks session, createUser is not a Supabase method.

3. Final Answer:

   signInWithPassword -> Option C

4. Quick Check:

   Login method = signInWithPassword [OK]

Hint: Login uses signInWithPassword, logout uses signOut [OK]

Common Mistakes:

• Choosing signOut to log in
• Confusing getSession with login
• Assuming createUser is a Supabase method

3. What will the following code return if a user is logged in?

const { data } = await supabase.auth.getSession();
console.log(data.session);

medium

A. An object with session details

B. null

C. An error message

D. Undefined

Solution

1. Step 1: Understand getSession behavior

   getSession returns session info if user is logged in.

2. Step 2: Analyze console output

   Logging data.session shows session object, not null or error.

3. Final Answer:

   An object with session details -> Option A

4. Quick Check:

   Logged-in session = session object [OK]

Hint: getSession returns session object if logged in, else null [OK]

Common Mistakes:

• Expecting null when user is logged in
• Thinking getSession throws error
• Assuming undefined is returned

4. You wrote this code to log out a user:

await supabase.auth.signInWithPassword();

What is wrong here?

medium

A. You need to pass email and password to signInWithPassword

B. signInWithPassword is for logging in, not logging out

C. signInWithPassword does not exist in Supabase

D. You should use getSession to log out

Solution

1. Step 1: Identify method purpose

   signInWithPassword is for logging in users, not logging out.

2. Step 2: Correct logout method

   To log out, use signOut method instead.

3. Final Answer:

   signInWithPassword is for logging in, not logging out -> Option B

4. Quick Check:

   Logout method ≠ signInWithPassword [OK]

Hint: Use signOut to log out, not signInWithPassword [OK]

Common Mistakes:

• Using signInWithPassword to log out
• Forgetting to pass credentials to signInWithPassword
• Confusing getSession with logout

5. You want to check if a user is logged in before showing a dashboard. Which code snippet correctly does this using Supabase session management?

hard

A. const session = await supabase.auth.signInWithPassword(); if (session) { showDashboard(); } else { showLogin(); }

B. const session = supabase.auth.signOut(); if (session) { showDashboard(); } else { showLogin(); }

C. const session = supabase.auth.getUser(); if (session) { showDashboard(); } else { showLogin(); }

D. const { data } = await supabase.auth.getSession(); if (data.session) { showDashboard(); } else { showLogin(); }

Solution

1. Step 1: Identify correct session check method

   getSession returns current session info to check login status.

2. Step 2: Verify conditional logic

   If data.session exists, user is logged in; else show login screen.

3. Step 3: Eliminate incorrect options

   signInWithPassword logs users in, signOut logs users out, getUser requires await and checking data.user (e.g. const { data } = await supabase.auth.getUser(); if (data.user)) but const session = supabase.auth.getUser(); if (session) { showDashboard(); } else { showLogin(); } lacks both.

4. Final Answer:

   const { data } = await supabase.auth.getSession(); if (data.session) { showDashboard(); } else { showLogin(); } -> Option D

5. Quick Check:

   Check session with getSession before showing dashboard [OK]

Hint: Use getSession and check data.session to confirm login [OK]

Common Mistakes:

• Using signOut or signInWithPassword to check session
• Using getUser without await and proper data.user check
• Not checking if session is null