Authentication errors in context in GraphQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an authentication error in GraphQL context?

An authentication error occurs when a user tries to access a GraphQL API without valid credentials or tokens, causing the server to reject the request.

beginner

How is authentication information typically passed in a GraphQL request context?

Authentication info is usually passed via HTTP headers (like Authorization) and then added to the GraphQL context object for resolvers to check.

intermediate

Why should authentication errors be handled in the GraphQL context?

Handling authentication errors in context centralizes security checks, making it easier to reject unauthorized requests before resolver logic runs.

intermediate

What is a common way to signal an authentication error in GraphQL?

Throwing an AuthenticationError (from packages like apollo-server-errors) which sends a clear error message and HTTP 401 status to the client.

beginner

How can you protect a GraphQL resolver from unauthorized access?

Check the user's authentication status in the context before running resolver logic; if unauthorized, throw an authentication error.

Where is authentication data usually stored for GraphQL resolvers to access?

A In the client-side cookies only

B In the query string

C In the GraphQL context object

D In the database schema

Authentication data is passed in HTTP headers and then added to the GraphQL context object for resolvers to use.

What HTTP status code is commonly returned for authentication errors in GraphQL?

A 401

B 200

C 404

D 500

401 Unauthorized is the standard status code for authentication errors.

Which package is often used to throw authentication errors in Apollo Server?

A graphql-tools

B jsonwebtoken

C express-session

D apollo-server-errors

apollo-server-errors provides AuthenticationError to signal auth failures.

What happens if a resolver does not check authentication in context?

A The server crashes

B The resolver runs normally, possibly exposing data

C The client automatically retries

D The query is blocked by default

Without checks, unauthorized users may access sensitive data.

Why is it better to handle authentication errors early in the GraphQL request lifecycle?

A To reduce unnecessary resolver execution

B To speed up client rendering

C To avoid database schema changes

D To allow anonymous access

Early handling stops unauthorized requests before expensive resolver logic runs.

Explain how authentication errors are detected and handled in the GraphQL context.

Think about where the server checks credentials and how it responds to unauthorized requests.

Describe why it is important to check authentication in GraphQL resolvers and what could happen if you don't.

Consider the consequences of skipping authentication checks.

Practice

1. What is the main purpose of checking user information in the GraphQL context during a query?

easy

A. To prevent unauthorized users from accessing sensitive data

B. To speed up the query execution

C. To format the data before sending it

D. To log the query for analytics

Solution

1. Step 1: Understand the role of context in GraphQL

   The context carries user information that helps identify who is making the request.

2. Step 2: Recognize the purpose of authentication checks

   Checking user info in context ensures only authorized users get sensitive data.

3. Final Answer:

   To prevent unauthorized users from accessing sensitive data -> Option A

4. Quick Check:

   Authentication protects data = D [OK]

Hint: Always check user info in context to block unauthorized access [OK]

Common Mistakes:

• Thinking context is for speeding queries
• Assuming context formats data
• Believing context is only for logging

2. Which of the following is the correct way to throw an authentication error inside a GraphQL resolver using context?

easy

A. throw new Error('Not authenticated') without checking context

B. if (context.user) throw new Error('Not authenticated')

C. return 'Not authenticated' without throwing error

D. if (!context.user) throw new Error('Not authenticated')

Solution

1. Step 1: Check user presence in context

   We must verify if context.user exists to confirm authentication.

2. Step 2: Throw error when user is missing

   If no user info, throw an error to stop unauthorized access.

3. Final Answer:

   if (!context.user) throw new Error('Not authenticated') -> Option D

4. Quick Check:

   Throw error if no user = C [OK]

Hint: Throw error only when user info is missing in context [OK]

Common Mistakes:

• Throwing error when user exists
• Not checking context before throwing
• Returning error message instead of throwing

3. Given this resolver snippet:

function resolver(parent, args, context) {
  if (!context.user) {
    throw new Error('Not authenticated');
  }
  return 'Secret Data';
}

What will be the output if context.user is null?

medium

A. null

B. Error: Not authenticated

C. 'Secret Data'

D. undefined

Solution

1. Step 1: Check the condition with context.user null

   Since context.user is null, the condition !context.user is true.

2. Step 2: Understand error throwing behavior

   The resolver throws an error 'Not authenticated' and stops execution.

3. Final Answer:

   Error: Not authenticated -> Option B

4. Quick Check:

   Null user triggers error = A [OK]

Hint: Null or missing user causes error throw [OK]

Common Mistakes:

• Assuming it returns secret data anyway
• Expecting null instead of error
• Confusing error message with return value

4. Identify the error in this resolver code snippet:

function resolver(parent, args, context) {
  if (context.user === undefined) {
    throw new Error('Not authenticated');
  }
  return 'User data';
}

medium

A. Throwing error without message is wrong

B. Return statement is missing

C. It should check if context.user is falsy, not just undefined

D. No error, code is correct

Solution

1. Step 1: Analyze the user check condition

   The code only checks if context.user is exactly undefined, missing null or false cases.

2. Step 2: Explain why broader check is needed

   Users can be null or falsy; checking only undefined misses those cases, allowing unauthorized access.

3. Final Answer:

   It should check if context.user is falsy, not just undefined -> Option C

4. Quick Check:

   Check all falsy user values = B [OK]

Hint: Check all falsy user values, not just undefined [OK]

Common Mistakes:

• Checking only undefined misses null users
• Assuming error message is missing
• Thinking return is missing

5. You want to protect a GraphQL query that returns user profile data. Which approach correctly uses context to throw an authentication error only if the user is not logged in, and returns the profile otherwise?

function getUserProfile(parent, args, context) {
  // Your code here
}

hard

A. if (!context.user) throw new Error('Not authenticated'); return context.user.profile;

B. if (context.user) throw new Error('Not authenticated'); return context.user.profile;

C. return context.user.profile; if (!context.user) throw new Error('Not authenticated');

D. throw new Error('Not authenticated'); return context.user.profile;

Solution

1. Step 1: Check user presence before returning data

   The code must first verify if context.user exists to confirm authentication.

2. Step 2: Throw error if user is missing, else return profile

   If no user, throw error; otherwise, safely return user profile data.

3. Final Answer:

   if (!context.user) throw new Error('Not authenticated'); return context.user.profile; -> Option A

4. Quick Check:

   Check user first, then return profile = A [OK]

Hint: Check user before return; throw error if missing [OK]

Common Mistakes:

• Throwing error when user exists
• Returning before checking user
• Throwing error unconditionally