API gateway integrations enable you to use PingAuthorize for attribute-based
access control and policy decisions with your
The following diagram outlines how API requests flow through your API gateway and PingAuthorize.
- The client sends a request to the API gateway.
- The API gateway-specific integration kit processes the client's request and sends it to the PingAuthorize Server for policy processing.
- The PingAuthorize Server determines whether to permit or deny the API request based on policies defined in the PingAuthorize Policy Editor.
- The API gateway analyzes the response from the PingAuthorize Server to determine whether the request should be forwarded to the upstream API and, if so, whether any modifications should be made to the request.
- The API gateway passes the original or modified request to the API target.
- The API resource server sends a response to the gateway with the requested resources.
- The API gateway integration kit processes the resource server's response and forwards it to the PingAuthorize Server for policy processing.
- The PingAuthorize Server determines whether to forward the API response to the client based on policies defined in the PingAuthorize Policy Editor.
- The PingAuthorize Server sends a final response to the API gateway.
- The API gateway processes the response and forwards the requested API resource to the client.
PingAuthorize provides the following API gateway integrations: