Ping Identity provides a custom Mulesoft policy to enable this configuration.


A diagram of the traffic flow for Mulesoft integration.

The custom Mulesoft policy acts as the sideband adapter, allowing Mulesoft to be used as the API gateway as follows:

  1. The client sends an incoming request to Mulesoft.
  2. The custom Mulesoft policy passes the incoming request to PingAuthorize Server.
  3. PingAuthorize Server determines whether to permit or deny the request based on policies defined in the PingAuthorize Policy Editor (not to be confused with Mulesoft policies). The server also performs any desired request modifications.
  4. If the request is permitted, Mulesoft makes the request to the backend resource.
  5. Mulesoft receives a response from the backend resource.
  6. The custom Mulesoft policy makes a second API call to pass response information to PingAuthorize Server.
  7. PingAuthorize Server determines whether to permit or deny based on the backend response. Before the server returns the request to Mulesoft, it also modifies the request based on policies defined in PingAuthorize.
  8. Mulesoft sends the response to the client.