Authentication errors in context in GraphQL

Introduction

Authentication errors tell us when someone tries to access data without permission. They help keep data safe.

When a user tries to log in with wrong username or password.

When a user tries to access data without logging in.

When a user's login session has expired and they try to use the system.

When a user tries to access data they are not allowed to see.

Syntax

GraphQL

type Query {
  secureData: String
}

const resolvers = {
  Query: {
    secureData(parent, args, context) {
      if (!context.user) {
        throw new AuthenticationError('You must be logged in');
      }
      return 'Secret info';
    }
  }
};

Authentication errors are usually thrown inside resolvers when user info is missing or invalid.

The context object often holds user info after login.

Examples

This checks if the user is missing in context and throws an error.

GraphQL

if (!context.user) {
  throw new AuthenticationError('Not logged in');
}

This checks if the user is an admin before allowing access.

GraphQL

if (!context.user.isAdmin) {
  throw new AuthenticationError('Admin access required');
}

Sample Program

This GraphQL server checks if the user is logged in by looking for a valid token in the request headers. If the token is missing or invalid, it throws an authentication error when trying to get the secret message.

GraphQL

const { ApolloServer, gql, AuthenticationError } = require('apollo-server');

const typeDefs = gql`
  type Query {
    secretMessage: String
  }
`;

const resolvers = {
  Query: {
    secretMessage(parent, args, context) {
      if (!context.user) {
        throw new AuthenticationError('You must be logged in to see this message');
      }
      return 'This is a secret message';
    }
  }
};

const server = new ApolloServer({
  typeDefs,
  resolvers,
  context: ({ req }) => {
    // Simulate user authentication
    const token = req.headers.authorization || '';
    if (token === 'valid-token') {
      return { user: { id: 1, name: 'Alice' } };
    }
    return {};
  }
});

server.listen().then(({ url }) => {
  console.log(`Server ready at ${url}`);
});

Important Notes

Always check authentication early in your resolver to avoid exposing data.

Use clear error messages so users know why access was denied.

Summary

Authentication errors protect data by stopping unauthorized access.

They are thrown inside resolvers using the context user info.

Check user info in context before returning sensitive data.

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