ความปลอดภัยของไมโครเซอร์วิสและเกตเวย์ API

Modern applications often use microservices: small, independent services communicating over a network. This approach offers flexibility and scalability.

An API Gateway acts as a single entry point for all client requests, routing them to the correct microservice. It's like a traffic cop for your APIs.

In a microservices architecture, you might have dozens or hundreds of services. Securing each one individually can be complex and error-prone.

An API Gateway provides a perfect place to centralize common security concerns, such as authentication and initial authorization. This is often called "security at the edge."

OAuth2 is ideal for microservices because it provides a standardized way to issue and validate access tokens. These tokens are credentials that represent a user's permission to access resources.

When a client requests a resource, it first obtains an access token from an Authorization Server. This token is then presented to the API Gateway.

The API Gateway acts as a Policy Enforcement Point (PEP). It intercepts incoming requests and performs critical security checks before forwarding them to the backend microservices.

Its primary security role is to validate the incoming OAuth2 access token. If the token is invalid, expired, or missing, the gateway rejects the request.

When a request hits the API Gateway with an access token, here's a typical validation sequence:

• Check Token Presence: Is there an Authorization: Bearer header?
• Validate Format: Is it a well-formed JWT?
• Verify Signature: Is the token signed by the trusted Authorization Server?
• Check Expiry: Is the token still active (not expired)?
• Validate Issuer & Audience: Is it from the correct issuer and intended for this resource?
• Scope Check: Does the token have the necessary permissions (scopes) for the requested operation?

Here's a conceptual look at how an API Gateway might validate an incoming JWT access token. This logic runs before any request reaches your microservices.

After the API Gateway validates an access token, it often needs to pass the user's identity and authorization context to the downstream microservices.

This is typically done by injecting relevant claims from the validated token (e.g., user ID, roles, specific permissions) into custom HTTP headers or a new internal token before forwarding the request.

What about when microservices need to communicate with each other directly, without a user in the loop? This is known as service-to-service authorization.

• Client Credentials Flow: Services can use their own client ID and client secret to obtain an access token from the Authorization Server.
• mTLS (Mutual TLS): Another option is to use mutual Transport Layer Security, where both the client and server present certificates to authenticate each other.

While the API Gateway handles initial authorization, individual microservices might need to perform more granular checks based on the specific resource being accessed.

For example, a "user profile" service might check if the authenticated user is requesting their own profile or if they have an "admin" role to view any profile. This uses the claims propagated from the gateway.

The API Gateway plays a crucial role in securing microservices.

In this lesson, we explored how to secure microservices using OAuth2 and an API Gateway.

• The API Gateway acts as a central Policy Enforcement Point for initial token validation.
• It propagates validated identity claims to downstream services.
• We also touched upon service-to-service authorization and fine-grained authorization within individual microservices.