Hosting Environment
Operating System
Task Type
Draft Beta

PingIntelligence for APIs PingAccess Integration

Updated 78

Add to MyDocs | Hide Show Table of Contents

PingIntelligence – PingAccess Integration

This guide describes the installation of PingIntelligence for APIs 3.2.1 with PingAccess 5.2.

This diagram depicts the architecture of PingIntelligence for APIs components along with PingAccess:

Here is the traffic flow through the PingAccess and PingIntelligence for APIs components.

  1. Incoming request to PingAccess
  2. PingAccess makes an API call to send the request information to ASE
  3. ASE checks the request against a registered set of APIs and checks the origin IP, cookie or OAuth2 token against the AI generated Blacklist. If all checks pass, ASE returns a 200-OK response to the PingAccess. If not, a different response code is sent to PingAccess. The request information is also logged by ASE and sent to the AI Engine for processing.
  4. If PingAccess receives a 200-OK response from ASE, then it forwards the request to the backend server. Otherwise, the Gateway optionally blocks the client.
  5. The response from the backend server is received by PingAccess.
  6. PingAccess makes a second API call to pass the response information to ASE which sends the information to the AI engine for processing.
  7. ASE receives the response information and sends a 200-OK to PingAccess.
  8. PingAccess sends the response received from the backend server to the client.

Tags Product > PingIntelligence; Product > PingIntelligence > PingIntelligence 3.2