All Classes and Interfaces

Class
Description
 
 
When native-lambda is used for external clients and all external requests go through the Akamai cloud proxy, the real client IP can be retrieved from the header as True-Client-IP
 
 
This middleware is responsible for auditing the request and response.
 
 
 
 
 
This is the cache manager that can survive the cold start of the lambda function.
This class is used to handle exceptions and return the response to the client.
 
 
 
 
When the rate limit handler is located after the JwtVerifierHandler in the request/response chain, we can get the client_id claim from the JWT token from the auditInfo object from the exchange attachment.
This is a customized KeyResolver for one of our customers on the external gateway in the DMZ.
When user is selected as the key, we can get the user_id from the JWT claim.
 
When rate limit is used, we need to define a key to identify a unique client or a unique IP address.
This is the entry point for the middleware Lambda function that is responsible for cross-cutting concerns for the business Lambda function which is called from the is Lambda function once all cross-cutting concerns are addressed.
 
 
 
 
 
 
 
 
This middleware is responsible for routing the incoming request to the external microservices.
This is the entry point for the stream lambda function that is responsible for cross-cutting concerns for the business Lambda function which is called from the is Lambda function once all cross-cutting concerns are addressed.
Shared object among middleware threads containing information on the request/response event.
Attachment key class to attach data to the exchange.
 
 
 
 
 
 
 
Rate limit logic for native lambda.
When address is used as the key, we can get the IP address from the header of the request.
This middleware is responsible for adding CORS headers to the response and return it if the request is a CORS preflight request.
 
 
This middleware is responsible for adding CORS headers to the response if the request is a CORS request.
 
 
 
 
 
This middleware is used to get the jwt token for the client credential grant type and put it into the Authorization header when the backend lambda function is invoking another service.