Kong API gateway integration

This guide describes the deployment of the PingIntelligence plugin for Kong 1.5.0 community version API gateway. Install the plugin on all the Kong nodes that you want to integrate with PingIntelligence. You can apply the plugin at the global level or a per-service level for both db-less and database mode of Kong API gateway. For more information on Kong’s db-less and database mode, see Kong documentation.

The following is a high-level list of features of the PingIntelligence plugin:

You can apply the plugin at the global or per-service level for both database and db-less mode.
The plugin supports keepalive connections.
You can configure ASE primary and secondary nodes for failover. If both the primary and secondary nodes are not available, the plugin routes the connection to the backend servers.

The following diagram shows the logical setup of PingIntelligence and Kong API gateway:

teb1582694344833

The traffic flows through Kong API gateway and PingIntelligence for APIs components using the following process:

Client sends an incoming request to Kong.
Kong makes an API call to send the request metadata to ASE.
ASE checks the request against a registered set of APIs and looks up the client identifier on the PingIntelligence AI engine generated Blacklist. If all checks pass, ASE returns a 200-OK response to Kong. If not, a different response code is sent to Kong. The request information is also logged by ASE and sent to the AI Engine for processing.
If Kong receives a 200-OK response from ASE, then it forwards the request to the backend server. A request is blocked only when ASE sends a 403 error code to Kong.
The response from the backend server is received by Kong.
Kong makes a second API call to pass the response information to ASE which sends the information to the AI engine for processing.
ASE receives the response information and sends a 200-OK to Kong.
Kong sends the response received from the backend server to the client.