GitHub sign-in in Firebase - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

What happens after a successful GitHub sign-in with Firebase?

After a user signs in successfully using GitHub with Firebase Authentication, what is the immediate result in the Firebase system?

A Firebase deletes the user's GitHub account information after sign-in.

B The user is redirected to the GitHub website to create a new account.

C The user must manually verify their email address before Firebase creates a user record.

D The user receives a Firebase ID token and a user record is created or updated in Firebase Authentication.

💡 Hint

Think about what Firebase Authentication does after a third-party sign-in.

When a user signs in with GitHub, Firebase creates or updates a user record and issues a Firebase ID token to identify the user in your app.

❓ Configuration

intermediate

Which Firebase configuration is required for GitHub sign-in?

To enable GitHub sign-in in Firebase Authentication, which configuration step is mandatory?

A Register the GitHub OAuth client ID and client secret in the Firebase console under Authentication providers.

B Add the GitHub repository URL to the Firebase Realtime Database rules.

C Enable GitHub sign-in by uploading a GitHub SSH key to Firebase Storage.

D Configure a Firebase Cloud Function to listen for GitHub webhook events.

💡 Hint

Think about what OAuth credentials Firebase needs to connect with GitHub.

Firebase requires the GitHub OAuth client ID and secret to authenticate users via GitHub.

❓ security

advanced

What is the best practice to secure GitHub OAuth credentials in Firebase?

When configuring GitHub sign-in in Firebase, how should you handle the OAuth client secret to keep it secure?

A Publish the client secret in a public GitHub repository for transparency.

B Include the client secret in the client app code to allow direct GitHub authentication.

C Store the client secret only in the Firebase console and never expose it in client-side code.

D Send the client secret as a URL parameter during sign-in requests.

💡 Hint

Consider where sensitive credentials should be stored to prevent leaks.

The OAuth client secret must be kept confidential and stored securely in the Firebase console, never exposed in client code.

❓ Architecture

advanced

How does Firebase handle user identity when linking GitHub sign-in with other providers?

If a user signs in with GitHub and later signs in with Google using Firebase Authentication, how does Firebase manage the user's identity?

A Firebase creates two separate user records for GitHub and Google sign-ins automatically.

B Firebase links both sign-in methods to a single user record if the developer explicitly links accounts.

C Firebase deletes the first user record when the second sign-in occurs.

D Firebase requires the user to create a new account for each provider.

💡 Hint

Think about how Firebase supports multiple sign-in methods for one user.

Firebase allows linking multiple sign-in providers to one user record when the developer links accounts explicitly.

🧠 Conceptual

expert

Why does Firebase require redirect URLs in GitHub OAuth setup?

When setting up GitHub sign-in with Firebase, why must you specify redirect URLs in the GitHub OAuth app settings?

A To tell GitHub where to send the user after authentication so Firebase can complete sign-in securely.

B To let GitHub bypass user consent screens during sign-in.

C To enable Firebase to send emails to users after sign-in.

D To allow GitHub to store user data in Firebase Realtime Database.

💡 Hint

Consider the OAuth flow and how the app receives the authentication response.

The redirect URL is where GitHub sends the user after sign-in so Firebase can receive the authorization code and complete authentication.