Background
This article details a couple of basic network and email related configurations that you will want to perform as part of onboarding the 4U Platform application. These changes will ensure that your users have a seamless experience.
Email Servers
Please update your email security rules to allow emails from the @4uplatform.com domain to ensure that users receive emails from the platform.
Additionally, if you have rules that automatically rewrite links in emails to go through a proxy server, we ask that you disable this functionality for emails from the @4uplatform.com domain.
Network Firewalls
Domain Allow Listing
If your organization maintains a corporate firewall or other network security features that restricts employee access to approved websites only, you'll need to allow https traffic with the following domains:
*.4uplatform.com(note the wildcard)*.sd.4uplatform.com(note the wildcard)cdn-4u-prod-us-east-1.s3.amazonaws.comcdn-4u-prod-us-west-2.s3.amazonaws.comapi-storage-4u-us-east-1.s3.amazonaws.comapi-storage-4u-us-west-2.s3.amazonaws.comsecure-docs-storage-4u-prod-us-east-1.s3.amazonaws.comsecure-docs-storage-4u-prod-us-west-2.s3.amazonaws.com*.split.io
* Please note that we utilize dynamic pools of servers and so it's not possible to perform IP-based allow listing; it must be done by domain name.
HTTP Response Headers
If your organization maintains a firewall and/or network devices that re-write or remove http response headers, you'll need to disable this functionality for all domains listed in the previous section.
This issue is less common but we occasionally see this problem with certain types of firewalls that strip out access-control-* headers (for example, access-control-allow-origin). When this happens critical functionality on the site will break due to CORS-related errors.
Browsers
4U supports current versions of the following browsers:
Microsoft Edge
Chrome
Firefox