Whitelist Inforiver IPs

Inforiver's outbound IP address must be whitelisted in the customer's network or database firewalls to access Inforiver services.

1. Whitelisting Inforiver for On-Prem Writeback

Inforiver writeback may be unable to connect to on-prem databases hosted in data centers or office networks. This happens because the network firewall between your database and Inforiver blocks the inbound communication initiated for writeback.

For writeback to work with on-prem databases, the admin must whitelist the below 5 Inforiver outbound IPs in the network firewall.

Inforiver IP addresses to be whitelisted:

For addons.inforiver.com:

i) 20.80.81.140 - 20.80.81.143

ii) 172.170.162.240

For euw.addons.inforiver.com:

i) 20.229.172.84 - 20.229.172.87

ii) 57.153.117.230

2. Whitelisting for Azure SQL

Azure SQL destinations have firewall rules that block connections originating from non-whitelisted IPs.

firewall blocking the inbound communication to Azure

To connect to Azure SQL databases from Inforiver, you must create a firewall rule to open the firewall for a specific range of IP addresses. Learn more about creating firewall rules.

Inforiver IP addresses to be whitelisted:

For addons.inforiver.com:

i) 20.80.81.140 - 20.80.81.143

ii) 172.170.162.240

For euw.addons.inforiver.com:

i) 20.229.172.84 - 20.229.172.87

ii) 57.153.117.230

Follow the steps in the image below to whitelist the Inforiver outbound IP addresses.

Creating firewall rules

The screengrab below shows the firewall rules configured for Inforiver.

Firewall rules configured for Inforiver