Connect Players & Servers via VPN

openvpn (brightsign currently uses openvpn 2 4 7) can be used to create a connection to your servers the openvpn "configuration" interface is a path to a complete configuration file and (optionally) the passphrase needed to decrypt the private key the process is limited by —script security=1 for the entire duration of that process the configuration is extracted to flash, meaning that it will persist across device reboots and/or if the microsd card is reformatted if the device is configured for openvpn, it will automatically run on startup of the brightsign application when configuring output files, you should use the applicable attached storage device (for example, /storage/sd/ ) note that archive file (for brightscript) or archivefile (for javascript) must point to a zip archive containing a valid openvpn configuration file named client conf in the top level directory (see the appendix for an example client conf file) all paths configured in client conf are assumed to be absolute in order to refer to files extracted on the player after running installandrun , the following directory path should be assumed /var/lib/brightsign/openvpn/ to establish the connection, reference the roopenvpn docid\ h5yukxl66nblm7kmrdhrk brightscript api or the openvpn docid 448gct3taonga5e0ltx6 javascript api absolute path format in addition to other configuration information, client conf should contain the absolute path format of the configured artifacts for example ca /var/lib/brightsign/openvpn/ca crt cert /var/lib/brightsign/openvpn/client1 crt key /var/lib/brightsign/openvpn/client1 key log /storage/sd/openvpn log