OAuth providers (Google, GitHub) in Supabase - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

OAuth Sign-in Flow Behavior

When a user signs in using Google OAuth via Supabase, what is the expected behavior immediately after successful authentication?

A The user must manually refresh the page to complete sign-in.

B The user is redirected to the callback URL with an access token in the URL fragment.

C The user receives an email with a verification link before access is granted.

D The user is redirected to the homepage without any token or session information.

💡 Hint

Think about how OAuth typically returns tokens after authentication.

OAuth providers like Google redirect users back to the app with an access token in the URL fragment, allowing the app to establish a session immediately.

❓ Configuration

intermediate

Configuring GitHub OAuth in Supabase

Which of the following is required to configure GitHub OAuth provider in Supabase?

A GitHub OAuth redirect URI set to 'https://github.com/login/oauth/authorize'.

B GitHub username and password for API access.

C GitHub Client ID and Client Secret from GitHub Developer Settings.

D A personal access token with repo permissions.

💡 Hint

Consider what OAuth apps require to identify themselves.

OAuth apps need a Client ID and Client Secret from GitHub Developer Settings to authenticate users via GitHub.

❓ security

advanced

Preventing OAuth Redirect URI Mismatch

What is the most secure way to avoid redirect URI mismatch errors when configuring OAuth providers in Supabase?

A Set the redirect URI to 'http://localhost' for all environments.

B Use a wildcard redirect URI like 'https://*.example.com/callback' to allow all subdomains.

C Leave the redirect URI blank to accept any redirect URI during OAuth flow.

D Set the redirect URI in the OAuth provider settings exactly to the Supabase callback URL used by your app.

💡 Hint

Redirect URIs must match exactly for security reasons.

OAuth providers require the redirect URI to match exactly what is registered to prevent malicious redirection attacks.

❓ Architecture

advanced

OAuth Token Storage Best Practice

After a user signs in with GitHub OAuth in a Supabase app, where should the access token be stored to maintain security and usability?

A Store the access token securely in an HttpOnly cookie to prevent JavaScript access.

B Store the access token in localStorage for easy access by client scripts.

C Embed the access token in the URL query parameters for sharing.

D Store the access token in a global JavaScript variable.

💡 Hint

Think about how to protect tokens from cross-site scripting attacks.

HttpOnly cookies prevent JavaScript from accessing tokens, reducing risk of token theft via XSS attacks.

🧠 Conceptual

expert

OAuth Provider Scope Impact

How does changing the OAuth scope in GitHub provider settings affect the Supabase authentication process?

A It changes the permissions requested from the user, affecting what data the app can access after sign-in.

B It changes the user's password requirements during sign-in.

C It modifies the OAuth redirect URI dynamically during authentication.

D It disables multi-factor authentication for the user.

💡 Hint

Scopes define what the app can do on behalf of the user.

OAuth scopes specify permissions the app requests, controlling access to user data and actions after sign-in.