OAuth providers (Google, GitHub) in Supabase - Step-by-Step Execution

Process Flow - OAuth providers (Google, GitHub)

User clicks Login

↓

Redirect to OAuth Provider

↓

User authenticates on Provider

↓

Provider sends Auth Code

↓

App exchanges Code for Token

↓

User logged in with Token

User starts login, is sent to Google or GitHub to authenticate, then returns with a token to log in.

Execution Sample

Supabase

supabase.auth.signInWithOAuth({ provider: 'google' })

Starts OAuth login flow with Google provider.

Process Table

Step	Action	State Change	Result
1	User clicks login button	No state change yet	Redirect to Google OAuth page
2	User enters Google credentials	Google verifies user	Google sends auth code to app
3	App receives auth code	App exchanges code for access token	Access token received
4	App uses token to get user info	User session created in app	User logged in
5	User accesses app features	Session active	Access granted

💡

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
authCode	null	received from provider	used for token exchange	null (exchanged)	null
accessToken	null	null	received from provider	used to get user info	valid token
userSession	null	null	null	created	active

Key Moments - 3 Insights

Why does the app redirect the user to Google or GitHub instead of asking for credentials directly?

The app redirects to the OAuth provider to keep user credentials safe and let the provider handle authentication, as shown in step 1 and 2 of the execution table.

What happens to the auth code after the app exchanges it for an access token?

The auth code is used once to get the access token and then discarded, as seen in variable 'authCode' becoming null after step 3.

How does the app know the user is logged in?

After receiving the access token and user info, the app creates a user session, shown in step 4 and tracked by 'userSession' variable.

Visual Quiz - 3 Questions

Look at the execution table, what happens at step 3?

A User enters credentials on provider page

B User session is created

C App exchanges auth code for access token

D User clicks login button

💡 Hint

Check the 'Action' and 'Result' columns for step 3 in the execution table

According to variable_tracker, when does 'userSession' become active?

A After Step 4

B After Step 3

C After Step 2

D At Start

💡 Hint

Look at the 'userSession' row and see when it changes from null to active

If the auth code was never received, what would happen in the flow?

A User would be logged in immediately

B App would not get access token and login would fail

C User session would be created without token

D App would skip OAuth and use password login

💡 Hint

Refer to the importance of authCode in variable_tracker and step 3 in execution_table

Concept Snapshot

OAuth login flow:
1. User clicks login
2. Redirect to provider (Google/GitHub)
3. User authenticates
4. Provider sends auth code
5. App exchanges code for token
6. User session created
Keep credentials safe by using provider's login page.

Full Transcript

This visual execution shows how OAuth providers like Google and GitHub work with Supabase. The user clicks login, then is redirected to the provider's page to enter credentials. The provider sends an authorization code back to the app. The app exchanges this code for an access token. Using the token, the app creates a user session and logs the user in. Variables like authCode, accessToken, and userSession change state step-by-step. Key moments include why redirection is needed, what happens to the auth code, and how the app knows the user is logged in. The quiz tests understanding of these steps and variable changes.