Custom authentication tokens in Firebase - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

What happens when a Firebase custom token expires?

You create a Firebase custom authentication token with a 1-hour expiration. What happens if a client tries to use this token after it expires?

A The client is denied access and must request a new token to authenticate again.

B The client can continue using the expired token without interruption.

C Firebase automatically refreshes the token without client intervention.

D The client is permanently blocked from accessing Firebase services.

💡 Hint

Think about how tokens maintain security by limiting their valid time.

Firebase custom tokens expire after their set time. Clients must get a new token to continue authenticating. Expired tokens are rejected to keep access secure.

❓ Configuration

intermediate

Which Firebase Admin SDK method creates a custom token?

You want to generate a custom authentication token for a user with ID 'user123'. Which Firebase Admin SDK method correctly creates this token?

A admin.auth().signInWithCustomToken('user123')

B admin.auth().generateToken('user123')

C admin.auth().createCustomToken('user123')

D admin.auth().getCustomToken('user123')

💡 Hint

Look for the method that explicitly mentions 'create' and 'CustomToken'.

The Firebase Admin SDK uses createCustomToken(uid) to generate a custom token for a user ID. Other methods do not exist or serve different purposes.

❓ security

advanced

What is the best practice to secure the private key used for signing Firebase custom tokens?

You have a private key to sign Firebase custom tokens. Which practice best protects this key?

A Store the private key in a secure environment variable or secret manager, never in client code.

B Embed the private key directly in the client app for faster token generation.

C Share the private key with all developers via email for easy access.

D Commit the private key to the public source code repository for transparency.

💡 Hint

Think about who should have access to sensitive keys and where they should be stored.

Private keys must be kept secret and stored securely, such as in environment variables or secret managers. Exposing keys in client code or public repos risks compromise.

❓ Architecture

advanced

How should you architect a system to issue Firebase custom tokens for users authenticated by an external system?

You have an external user database and want to allow those users to access Firebase services using custom tokens. What architecture best supports this?

A Use Firebase client SDK to create custom tokens without backend verification.

B Allow clients to generate custom tokens directly using the Firebase Admin SDK in the frontend.

C Store Firebase private keys in the external user database for token generation.

D Create a secure backend service that verifies external user credentials and issues Firebase custom tokens on demand.

💡 Hint

Consider where sensitive operations like token signing should happen.

A secure backend service should verify external users and generate custom tokens. This keeps private keys safe and ensures only valid users get tokens.

🧠 Conceptual

expert

What is the main difference between Firebase custom tokens and ID tokens?

Firebase uses both custom tokens and ID tokens in authentication. What is the key difference between them?

A ID tokens are created by your backend; custom tokens are issued by Firebase after sign-in.

B Custom tokens are short-lived tokens created by your backend to sign in users; ID tokens are issued by Firebase after sign-in and used to authorize requests.

C Custom tokens and ID tokens are the same and can be used interchangeably.

D ID tokens are used only for anonymous users; custom tokens are for registered users.

💡 Hint

Think about who creates each token and when they are used.

Custom tokens are created by your backend to sign in users. After sign-in, Firebase issues ID tokens to the client to authorize requests. They serve different roles.