Authentication at gateway level in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main role of an API gateway in microservices architecture?

An API gateway acts as a single entry point for all client requests. It routes requests to appropriate microservices, handles cross-cutting concerns like authentication, logging, and rate limiting.

intermediate

Why is authentication at the gateway level beneficial?

It centralizes authentication, reducing duplicated code in microservices, improves security by enforcing consistent policies, and simplifies client interactions by handling tokens and credentials in one place.

intermediate

What is a common method used by gateways to authenticate requests?

Gateways often use JSON Web Tokens (JWT) to authenticate requests. The gateway verifies the token's signature and claims before forwarding the request to microservices.

beginner

How does the gateway handle an unauthenticated request?

The gateway rejects the request immediately, usually returning a 401 Unauthorized response, preventing unauthenticated traffic from reaching microservices.

advanced

What is a potential drawback of authenticating only at the gateway?

If microservices trust the gateway blindly, a compromised gateway could allow unauthorized access. Also, internal service-to-service authentication might still be needed for defense in depth.

What does an API gateway primarily do in microservices?

A Manages database transactions

B Stores user data

C Acts as a single entry point and handles authentication

D Runs background jobs

The API gateway acts as a single entry point and handles cross-cutting concerns like authentication.

Which token type is commonly verified by gateways for authentication?

A JWT (JSON Web Token)

B SAML

C OAuth 1.0

D API Key

JWTs are commonly used because they carry claims and can be verified by the gateway without contacting an auth server.

What response does a gateway send if authentication fails?

A 200 OK

B 403 Forbidden

C 500 Internal Server Error

D 401 Unauthorized

401 Unauthorized indicates the client failed to authenticate.

What is a key benefit of authenticating at the gateway instead of each microservice?

A Increases network traffic

B Centralizes authentication logic

C Requires more code in each microservice

D Slows down request processing

Centralizing authentication reduces duplicated code and enforces consistent security.

What is a security risk if microservices trust the gateway without additional checks?

A Gateway can become a single point of failure

B Microservices will run slower

C Clients must authenticate twice

D Gateway will reject all requests

If the gateway is compromised, attackers can bypass microservice security if no further checks exist.

Explain how authentication at the gateway level works in a microservices architecture.

Think about how the gateway checks credentials before letting requests reach microservices.

Discuss the advantages and potential risks of handling authentication only at the gateway.

Consider both the simplicity and the security implications.

Practice

1. What is the main benefit of performing authentication at the gateway level in a microservices architecture?

easy

A. It slows down the request processing by adding extra steps.

B. It allows each microservice to handle its own authentication independently.

C. It eliminates the need for authorization in microservices.

D. It centralizes authentication, reducing repeated checks in each microservice.

Solution

1. Step 1: Understand the role of gateway authentication

   Authentication at the gateway means checking user identity once before requests reach microservices.

2. Step 2: Identify benefits of centralizing authentication

   This reduces repeated authentication logic inside each microservice, improving maintainability and security.

3. Final Answer:

   It centralizes authentication, reducing repeated checks in each microservice. -> Option D

4. Quick Check:

   Centralized authentication = It centralizes authentication, reducing repeated checks in each microservice. [OK]

Hint: Gateway authentication centralizes checks, avoiding repetition [OK]

Common Mistakes:

• Thinking each microservice should authenticate independently
• Confusing authentication with authorization
• Assuming gateway authentication slows down system

2. Which of the following is the correct way to implement authentication at the gateway level?

easy

A. The gateway validates user tokens and forwards requests with user info.

B. The gateway forwards requests without checking authentication.

C. Each microservice validates user tokens independently.

D. Microservices share a database to authenticate users directly.

Solution

1. Step 1: Identify gateway's role in token validation

   The gateway should validate user tokens to confirm identity before forwarding requests.

2. Step 2: Understand forwarding with user info

   After validation, the gateway forwards requests including user identity details for downstream services.

3. Final Answer:

   The gateway validates user tokens and forwards requests with user info. -> Option A

4. Quick Check:

   Gateway validates tokens = The gateway validates user tokens and forwards requests with user info. [OK]

Hint: Gateway validates tokens, then forwards requests with user info [OK]

Common Mistakes:

• Letting microservices validate tokens independently
• Not validating tokens at the gateway
• Using shared database for authentication in microservices

3. Consider this simplified request flow code snippet at the gateway:

function handleRequest(request) {
  const token = request.headers['Authorization'];
  if (!validateToken(token)) {
    return { status: 401, message: 'Unauthorized' };
  }
  return forwardRequest(request);
}

What will happen if validateToken always returns false?

medium

A. All requests will be forwarded to microservices.

B. Requests without tokens will be forwarded, others rejected.

C. All requests will be rejected with 401 Unauthorized.

D. Gateway will crash due to invalid token handling.

Solution

1. Step 1: Analyze the token validation condition

   If validateToken(token) returns false, the code returns 401 Unauthorized immediately.

2. Step 2: Determine effect on all requests

   Since it always returns false, no requests pass validation, so all are rejected with 401.

3. Final Answer:

   All requests will be rejected with 401 Unauthorized. -> Option C

4. Quick Check:

   Always false validation = 401 rejection [OK]

Hint: False validation means all requests rejected [OK]

Common Mistakes:

• Assuming requests are forwarded despite failed validation
• Thinking gateway crashes on invalid token
• Ignoring the immediate return on failed validation

4. A gateway is designed to authenticate requests but sometimes forwards unauthorized requests to microservices. What is the most likely cause?

medium

A. The gateway does not check the token before forwarding.

B. The gateway caches old valid tokens and skips validation.

C. The gateway uses synchronous token validation.

D. Microservices override the gateway authentication.

Solution

1. Step 1: Identify why unauthorized requests pass

   If the gateway caches tokens and skips validation, expired or revoked tokens may be accepted.

2. Step 2: Understand caching impact on authentication

   Cached tokens can cause stale validation results, allowing unauthorized requests through.

3. Final Answer:

   The gateway caches old valid tokens and skips validation. -> Option B

4. Quick Check:

   Token caching causes stale auth = The gateway caches old valid tokens and skips validation. [OK]

Hint: Stale token cache causes unauthorized forwarding [OK]

Common Mistakes:

• Assuming microservices override gateway auth
• Ignoring token caching effects
• Confusing synchronous validation with forwarding issues

5. You are designing a microservices system with authentication at the gateway level. To ensure high availability and avoid a single point of failure, which design approach is best?

hard

A. Deploy multiple gateway instances behind a load balancer with shared session storage.

B. Use a single gateway instance with a backup database for tokens.

C. Let each microservice authenticate independently to avoid gateway failure.

D. Disable authentication at the gateway and rely on microservices.

Solution

1. Step 1: Identify high availability needs for gateway

   Multiple gateway instances prevent downtime if one fails, improving reliability.

2. Step 2: Understand role of load balancer and shared session storage

   Load balancer distributes requests; shared session storage keeps authentication state consistent across gateways.

3. Final Answer:

   Deploy multiple gateway instances behind a load balancer with shared session storage. -> Option A

4. Quick Check:

   Multiple gateways + load balancer = high availability [OK]

Hint: Use multiple gateways with load balancer for reliability [OK]

Common Mistakes:

• Relying on single gateway instance only
• Ignoring session consistency across gateways
• Disabling gateway authentication entirely