B-Deploy/Provisioning APIs

the b deploy service allows for automated provisioning of brightsign players over the internet this page outlines how to develop an application and file server (fs) that will integrate with b deploy authentication all b deploy calls require a valid authentication token authentication is carried out using the same oauth endpoint as other bsn cloud services see step 8 on postman collections docid\ hmkkvvtaul2u2x8p6byb0 for more details required components to integrate with the b deploy server, you will need to create two components application the application registers player serial numbers and setup files with the b deploy server file server the http file server hosts presentation packages for distribution to players each presentation package is a zip file named autorun zip , which contains presentation files along with an autozip brs boilerplate script (see robrightpackage docid 1dr98 7il7gyneownx2cr for more information) in most cases, the boilerplate script will not need to be modified workflow overview b deploy the user uploads one or more presentation packages to the file server (fs) and records the download url for each package the user creates a player setup by posting a json payload containing player setup parameters to the b deploy server the player setup contains the download url for the presentation package via the b deploy api, the user registers player serial numbers that should be associated with the player setup brightsign player the user inserts a blank storage device (e g a microsd card) into the player and powers it on the player boots up and, lacking an autorun brs or autorun zip file on the storage device, launches on screen player setup the user must avoid activating the player using the activation screen (or setting up the player with the player setup screen) these actions may prevent automated provisioning when on screen player setup times out, the player queries the b deploy server (unless the local network infrastructure is configured for provisioning via dhcp option 43) the b deploy server responds with a provisioning script url if the player serial number in the request matches a serial number in the database if the b deploy server does not recognize the serial number, it will return status code 204 the player reboots, downloads the provisioning script, and runs it the provisioning script directs the player to download the player setup package from b deploy the player reboots and runs player setup, which sets the recovery url to a handler on b deploy the player reboots, downloads a recovery script from the recovery url, and runs it the recovery script instructs the player to download the presentation package from the file server the player reboots and runs the presentation vlan network setup via b deploy using b deploy with vlan(s) has a few components to consider while configuring the network controller and the b deploy setup package in order to download and apply a setup package from b deploy on your player, an internet connection must first be connected without any manual setup needed this internet connection could be established through various methods; either through a physical ethernet connection (or brightsign usb c ethernet adapter) possibly using dhcp to avoid a manual configuration needed; or wifi configured through the player's on device setup wifi access point mode (see url com https //url com/ ); or connecting a brightsign mobile cellular modem keep in mind that the setup package may configure this current network interface by adjusting, removing, or leaving it as is once the b deploy setup package has been applied if the setup package download has vlans configured, your network controller interface must be configured to maintain internet connectivity for example, if you download a setup package via ethernet that prioritizes wifi, and wifi is expected to have an internet connection, the network controller must have wifi configured with an internet connection then, although ethernet was used to download the setup package, wifi will be the only interface used for network traffic since it is a higher priority the same is true for brightsign mobile and usb ethernet interfaces that are downloaded via ethernet if the setup package does change the current configuration of the physical ethernet, the ethernet port in the network controller must support the vlan configuration in the setup package if the current settings use ethernet to download the setup package, then the network controller must allow the default/native vlan (untagged) connectivity to support tagged vlans