---
title: Improving iovation accessibility using a reverse proxy
description: Use Postman to configure a PingAccess gateway deployment as a reverse proxy for iovation. Using PingAccess as a reverse proxy can improve accessibility to iovation even if end users are blocking third-party content.
component: pingaccess
version: 9.0
page_id: pingaccess:agents_and_integrations:pa_improving_iovation_accessibility
canonical_url: https://docs.pingidentity.com/pingaccess/9.0/agents_and_integrations/pa_improving_iovation_accessibility.html
revdate: August 8, 2025
section_ids:
  about-this-task: About this task
  steps: Steps
  result: Result
---

# Improving iovation accessibility using a reverse proxy

Use Postman to configure a PingAccess gateway deployment as a reverse proxy for iovation. Using PingAccess as a reverse proxy can improve accessibility to iovation even if end users are blocking third-party content.

## About this task

|   |                                                                                                                                                                                                  |
| - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|   | Only use this procedure for PingAccess [gateway deployments](../introduction_to_pingaccess/pa_choose_a_deployment_model.html). This procedures assumes that you already have Postman configured. |

The PingAccess iovation Integration Kit `.zip` archive contains a Postman collection that can automate most of the process of configuring a reverse proxy to connect with iovation.

In this procedure, you'll use the Postman collection to create a PingAccess application with settings that allow it to act as the reverse proxy for the provided virtual hosts. You can add additional virtual hosts to this application as necessary.

## Steps

1. Go to the `<iovation_integration_home>/setup` directory.

2. Import the `iovation First Party Dynamic JavaScript Reverse Proxy.postman_collection.json` file into Postman.

3. Set the environment variables as described by the collection documentation.

4. Run the collection.

## Result

You now have a PingAccess gateway deployment acting as a reverse proxy.

|   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| - | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | For PingAccess agent deployments, iovation recommends using either the reverse proxy model or the web device print server model. You can find more information about these models in [Retrieving and Serving Dynamic iovation JavaScript](https://help.iovation.com/001_FraudForce/04_Integrating_FraudForce/02_Integrating_with_Websites/02_Retrieving_First-Party_Dynamic_JavaScript) in the iovation Help Center (requires authentication to access), but remember that the iovation First Party Dynamic Javascript Reverse Proxy Postman collection doesn't work with agent deployments. |