Centralized vs distributed auth in Microservices - When to Use Which

The Big Idea

Discover how one smart change can save hours of frustration and keep your system safe!

The Scenario

Imagine a company with many small shops, each with its own lock and key. Every time an employee moves between shops, they need a new key. Managing all these keys manually is confusing and slow.

The Problem

Manually handling authentication for each service means repeating work, risking mistakes, and making it hard to keep track of who has access where. It slows down the system and frustrates users.

The Solution

Centralized or distributed authentication systems organize access smartly. Centralized auth uses one main lock everyone trusts, while distributed auth shares trust across shops. Both make access smoother and safer.

Before vs After

✗ Before

if user in serviceA_users:
    allow_access()
elif user in serviceB_users:
    allow_access()
else:
    deny_access()

✓ After

token = get_auth_token()
if validate_token(token):
    allow_access()
else:
    deny_access()

What It Enables

It enables seamless, secure access across many services without juggling multiple credentials or risking security gaps.

Real Life Example

Think of logging into your phone once and then using many apps without signing in again each time--that's centralized auth in action.

Key Takeaways

Manual auth across services is slow and error-prone.

Centralized and distributed auth simplify and secure access.

They improve user experience and system reliability.

Practice

1. What is the main characteristic of centralized authentication in microservices?

easy

A. No authentication is required between services

B. Each microservice verifies user identity independently

C. Authentication is done by the client application only

D. A single service handles all user login and identity verification

Solution

1. Step 1: Understand centralized authentication

   Centralized authentication means one dedicated service manages all login and identity checks for the system.

2. Step 2: Compare with other options

   Distributed auth where each service verifies independently, client-only auth, or no auth are not centralized.

3. Final Answer:

   A single service handles all user login and identity verification -> Option D

4. Quick Check:

   Centralized auth = single service [OK]

Hint: Centralized means one place handles all auth [OK]

Common Mistakes:

• Confusing centralized with distributed auth
• Thinking each service handles login in centralized auth
• Assuming client-only authentication is centralized

2. Which of the following is a typical token used in distributed authentication?

easy

A. OAuth 2.0 access token

B. SQL query string

C. HTML cookie without signature

D. Plain text password

Solution

1. Step 1: Identify token types in distributed auth

   Distributed authentication commonly uses tokens like OAuth 2.0 access tokens to verify identity without contacting a central service each time.

2. Step 2: Eliminate incorrect options

   SQL queries, unsigned cookies, and plain text passwords are not secure tokens used for distributed auth.

3. Final Answer:

   OAuth 2.0 access token -> Option A

4. Quick Check:

   Distributed auth token = OAuth 2.0 token [OK]

Hint: OAuth tokens are standard for distributed auth [OK]

Common Mistakes:

• Confusing SQL queries with tokens
• Using unsigned cookies as secure tokens
• Thinking plain text passwords are tokens

3. Consider a microservice system where each service validates JWT tokens locally without contacting a central auth server. What is the main advantage of this approach?

medium

A. Reduced latency and less dependency on a central service

B. Simpler token revocation management

C. Centralized control over user sessions

D. No need for token expiration

Solution

1. Step 1: Understand local JWT validation

   When services validate JWT tokens locally, they avoid network calls to a central auth server, reducing latency and dependency.

2. Step 2: Analyze other options

   Token revocation is harder locally, centralized control over user sessions is lost, and tokens still need expiration.

3. Final Answer:

   Reduced latency and less dependency on a central service -> Option A

4. Quick Check:

   Distributed auth local validation = less latency [OK]

Hint: Local token checks speed up requests [OK]

Common Mistakes:

• Assuming token revocation is easier locally
• Thinking local validation means centralized control
• Ignoring token expiration needs

4. A microservice system uses centralized authentication but experiences frequent downtime of the auth service. What is the best way to fix this issue?

medium

A. Use plain text passwords for faster login

B. Remove authentication completely

C. Implement caching of authentication tokens in services

D. Make each service validate tokens independently without central auth

Solution

1. Step 1: Identify problem with centralized auth downtime

   Downtime of the central auth service causes failures in login or token validation.

2. Step 2: Choose a solution to reduce dependency

   Caching tokens locally in services reduces calls to the central auth, improving availability without removing auth or security.

3. Final Answer:

   Implement caching of authentication tokens in services -> Option C

4. Quick Check:

   Fix downtime by caching tokens [OK]

Hint: Cache tokens to reduce auth service calls [OK]

Common Mistakes:

• Removing authentication entirely
• Switching to insecure plain text passwords
• Switching to distributed auth without planning

5. You are designing a large microservices system that requires high security and low latency. Which authentication approach best balances these needs?

hard

A. Centralized authentication with synchronous calls for every request

B. Distributed authentication using signed tokens validated locally with periodic revocation checks

C. No authentication to maximize speed

D. Centralized authentication with no token expiration

Solution

1. Step 1: Analyze security and latency needs

   High security requires token validation and revocation; low latency requires avoiding frequent central calls.

2. Step 2: Evaluate options

   Distributed authentication using signed tokens validated locally with periodic revocation checks uses signed tokens validated locally to reduce latency and periodic revocation checks to maintain security. Centralized authentication with synchronous calls for every request causes latency, no authentication is insecure, and centralized authentication with no token expiration risks stale sessions.

3. Final Answer:

   Distributed authentication using signed tokens validated locally with periodic revocation checks -> Option B

4. Quick Check:

   Balance security and speed with distributed tokens [OK]

Hint: Use local token checks plus revocation for security and speed [OK]

Common Mistakes:

• Choosing no authentication for speed
• Ignoring token expiration and revocation
• Relying on central auth for every request causing latency