BSN.cloud - ports and URLs for the BrightSign players

BrightAuthor:connected and players will require ports 80 and 443 to be open in order to communicate with BSN.cloud. 

For non-connected scenarios such as Local File Networking, the port requirements are similar to the current requirements for BrightAuthor.

In addition to those requirements, the initial player provisioning process and BSN.cloud Control Cloud requires access to these servers (by DNS):

  • certs.bsn.cloud
  • provision.bsn.cloud
  • ws.bsn.cloud
  • handlers.bsn.cloud
  • analytics.bsn.cloud
  • *.brightsignnetwork.com
  • *.amazonaws.com
  • *.netsuite.com

Note for customers using TLS-terminating proxies

Requests to the following https URLs are authenticated using a client certificate. If the TLS session is terminated in the proxy to allow for payload filtering, the client certificate will not match and the request will fail with a 401 status code. The proxy must be configured such that requests to any URL in the list below are handled transparently without TLS termination.

Requests to the following URLs use the WebSockets protocol. These do not require the client certificate but, if the proxy supports only HTTPS, it may be necessary to configure these URLs to bypass the proxy as well.

  • wss://ws.bsn.cloud/

Requests to the following URLs must be permitted by the ACL but do not otherwise require special handling:

 

The default value for the setup time server is http://time.brightsignnetwork.com. However, BrightAuthor and BrightAuthor:connected let the user enter a value for the time server. The associated scripts then set the time server to the value entered by the user. 

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Can't find what you're looking for? Try to
Powered by Zendesk