How does BSN.cloud notify the player of new BrightAuthor:connected content?
...
| Expand | ||
|---|---|---|
| ||
No. BrightSign does not initiate any contact with BrightAuthor:connected or players. Users initiate . BrightSign software (BrightAuthor:connected, BOS, Autoruns, plugins, etc.) initiates connections, send requests, or subscribe to events, and the server replies. There are no cases when a server sends a request to a player, which would be impossible in most cases anyway since players are behind firewalls/gateways. The BSN.cloud Ports and URLs for Players and Software page lists the services and ports which BrightAuthor:connected and players access in outbound connections. |
...
Do I need to allow outbound connections from Players to TCP port 80? If so, why?
| Expand | ||
|---|---|---|
| ||
Yes, at least one service requires this, but there nothing sensitive in that traffic. Only two server endpoints listen on TCP port 80 and do not require transport-level encryption (as described on this page):
The first is an NTP server and has other endpoints as well, and the second is used only to check the connection with the cloud at the early stages of the BOS boot. In both cases, it is impossible to use TLS because the handshake and certificate validation are possible only when boot is finished and the player's clock is initialized correctly. |
How does the server know if a player is active/inactive?
| Expand | ||
|---|---|---|
| ||
The BSN.cloud server expects each player to report its status every five minutes. If it does not, then player status is unhealthy (inactive?). The server does not talk to players to check how they are doing. |