Reverse Proxies

iProov allows all traffic from the internet to iProov servers to use a reverse proxy in your network. This topic describes how to setup:

• A reverse proxy
• The client SDKs

The fully qualified domain name (FQDN) iproov.customer.com is used as an example.

Native SDKs

Please refernece the corresponding sections regarding base_url configuration in the Android and iOS Github readmes.

• Android
• iOS

Web SDKs

To control the streaming location, set the base_url attribute on the <iproov-me> component:

<iproov-me token="***YOUR_TOKEN_HERE***"
base_url="https://iproov.customer.com"/>

In the Web SDK, additional assets are imported that cannot be part of the main bundle:

• WebAssembly files
• Web worker scripts
• Face detection models

To make it easier for you to reverse proxy to a single domain, we mirror these on our own CDN at: (https://cdn.iproov.app/assets)

In addition to the base_url you can also set assets_url.

Assets CDN

The default CDN is: https://cdn.iproov.app/assets

To override the default, set assets_url, see the example below and the use of the /assets suffix:

<iproov-metoken="***YOUR_TOKEN_HERE***"
assets_url="https://iproov-assets.customer.com/assets"/>

Important:

• The host cdn.iproov.app must be set for routing to work.
• The suffix /assets is not used by the main streaming platform. If the path suffix is maintained, the host name can be the same for both assets_url and base_url.

Firewall rules

Configure reverse proxies

1. All traffic sent to iproov.customer.com should reverse proxy to eu.rp.secure.iproov.me (for claims being processed in the EU region).
2. You must maintain the URI parameters.
3. No further modifications or load distributions are required as the FQDN eu.rp.secure.iproov.me will resolve to multiple iProov reverse proxies to provide resilience. These handle load distribution across the available iProov infrastructure.

Responsibilities

Example flow