This document provides endpoint information needed to allow Silo connections from behind a firewall. If your environment utilizes a firewall to manage network traffic, you may need to implement an exception for ALL applicable entries.
Domain names can be broadly whitelisted using a wildcard entry as shown in the following examples:
Silo uses a TLS connection over port 443 (HTTPS) with the Web Client, while the Installed Client uses a custom network protocol over port 443. We recommend creating a full exception in order to prevent connection issues with various Silo client types.
SSL inspection (e.g. SPI/DPI) will need to be disabled for Silo connections.
NOTE: This rule does not apply to Silo Windows Client version 2.9.13 and newer. Please see this article:
https://authentic8.freshdesk.com/a/solutions/articles/16000100713 for additional information.
Some customers may need to whitelist our External API endpoint in order to use other Silo services.
An exception for the following domain will be needed: extapi.authentic8.com
Please make sure to allow access to TCP port 443 for the following entries:
Web Client IP (a8silo.com):
Authentic8 registered IP address space:
Third Party Provider:
Additional Third Party Provider IPs in service December 6, 2023
Legacy IP addresses:
* If you are using the legacy load balancers, you may need to create an exception for the following entries:
Please contact Support if you have any additional questions and/or require further information.