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. 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
-
Go to the
<iovation_integration_home>/setupdirectory. -
Import the
iovation First Party Dynamic JavaScript Reverse Proxy.postman_collection.jsonfile into Postman. -
Set the environment variables as described by the collection documentation.
-
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 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. |