What do I have to whitelist to use Bridge?

Document created by Scott Wasilewski Employee on Dec 17, 2018Last modified by Scott Wasilewski Employee on Jan 24, 2019
Version 3Show Document
  • View in full screen mode



This list represents the current URLs that Bridge uses to provide service to clients. Since Bridge supports embedded videos and images, this list will only support uploaded multimedia. Meaning, media that has been uploaded from a local location like a server or desktop computer. The locations of any embedded multimedia that is used in a Bridge course from around the web needs to be whitelisted as well. If possible, in cases where a wildcard can be used (such as *.bridgeapp.com) that method is preferred so that any subaccounts that are created can be automatically whitelisted as well without having to update proxy or firewall settings.


  • *.bridgeapp.com
    • If wildcards are not allowed:
      • [client_domain].bridgeapp.com,
      • [sub]-[client_domain].bridgeapp.com (and with all of the subs)
      • help.bridgeapp.com
      • community.bridgeapp.com


Any URLs from any LTI or other integrations like Bright Cove, Lynda and OpenSesame have URLs that need to be whitelisted that can be provided by any of those services. Clients will have to whitelist additional sites if they are planning to use external embedding for sources like Wistia, YouTube, Vimeo or web-hosted images.



Upon request, we can provide a list that represents the current IP addresses that Bridge uses to provide service to clients. At any time to meet demand or improve service, Bridge may leverage new IP addresses. With this in mind, the best practice is to whitelist a domain (*.bridgeapp.com) and not individual IP addresses if possible. Should you experience any access issues like email, network access, SFTP access, etc., please contact your CSM to ensure that your version of the IP addresses is up-to-date.