BSN.cloud - ports and URLs for the BrightSign players and software

 

Below is the list of ports and URLs that our products use to communicate with BSN.cloud services.  All services are used in both BSN.Cloud Control Cloud and BSN.Cloud Content Cloud modes, except Device Snapshots, which requires 'bsncloud-dssp.s3.amazonaws.com' and 'sqs.us-east-1.amazonaws.com'.

Player Access Requirements

Domain Port(s) Control Cloud Content Cloud
provision.brightsignnetwork.com 443 X X
provision.bsn.cloud 443 X X
handlers.bsn.cloud 443 X X
ws.bsn.cloud 443 X X
api.bsn.cloud 443 X X
certs.bsn.cloud 443 X X
analytics.bsn.cloud 443 X X
certs.brightsignnetwork.com 443 X X
time.brightsignnetwork.com 80, 123 X X
crashes.brightsignnetwork.com 80, 443 X X
services.brightsignnetwork.com 80, 443 X X
api.brightsignnetwork.com 80, 443 X X
bsncloud-dssp.s3.amazonaws.com 80, 443 X X
bsncloud.s3.amazonaws.com 80, 443 Optional Optional
sqs.us-east-1.amazonaws.com 443 X X
bsnm.s3.amazonaws.com 80, 443 X X
brightsign.biz 80, 443 X X
api.qrserver.com 80, 443 X X
api.twitter.com  80, 443 Optional Optional

 

BrightAuthor:connected Desktop Client Access Requirements

Domain Port(s) Control Cloud Content Cloud
provision.brightsignnetwork.com 443 X X
provision.bsn.cloud 443 X X
handlers.bsn.cloud 443 X X
ws.bsn.cloud 443 X X
api.bsn.cloud 443 X X
certs.bsn.cloud 443 X X
analytics.bsn.cloud 443 X X
certs.brightsignnetwork.com 443 X X
time.brightsignnetwork.com 80, 123 X X
crashes.brightsignnetwork.com 80, 443 X X
services.brightsignnetwork.com 80, 443 X X
api.brightsignnetwork.com 80, 443 X X
bsncloud-dssp.s3.amazonaws.com 80, 443 X X
bsncloud.s3.amazonaws.com 80, 443 Optional Optional
sqs.us-east-1.amazonaws.com 443 X X
bsnm.s3.amazonaws.com 80, 443 X X
brightsign.biz 80, 443 X X
api.qrserver.com 80, 443 X X
api.twitter.com  80, 443 Optional Optional
*.netsuite.com 443 X X

 

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