DWS: Local Access

local access to the dws is disabled by default as of brightsignos 9 0 218 (on the 9 0 branch) and brightsignos 9 1 75 (on the 9 1 branch) in brightsignos versions prior to these, local access to the dws was enabled by default this page describes how to enable local access to the dws note that some specially configured players have the external microsd card port and usb storage disabled at the factory (sku svc internal storage only) for these players, local access to the dws remains on by default local access to the dws can be enabled over the local network with a web browser it can also be enabled by connecting to the player with a serial connection and using the brightsign shell several access methods exist as described below enable local access local access to the dws can be enabled using one of the methods described below brightauthor\ connected the easiest way to enable local access to the dws is to use the brightauthor\ connected app to create a setup that enables and configures the dws go to the admin tab and select docid\ xnnxywmv09iegziit7rwa under player settings > player configuration , click the checkbox next to enable local diagnostic web server for players that are already set up and connected to a bsn cloud network, the dws can also be turned on or off under docid\ uba8sfkmsajsibrbv4a6n enter a password for the dws password must be at least 8 characters long and include at least one uppercase letter, one lowercase letter, one number, and one special character the username will always be “admin” specify other player settings as desired and either save the setup to a file location or add the setup to the docid\ hzy2w0meeeryiforz9xfr the player must then be provisioned which applies the setup to the desired player for instructions, see this page docid\ cyl9kpm02co5rgcb9wqqv advanced methods local access to the dws can also be enabled using brightscript, the javascript api, or the brightsign serial command prompt these methods require more technical expertise than using the brightauthor\ connected app the full instructions and scripts to enable local access to the dws can be found https //github com/brightsign/dev cookbook/blob/main/examples/enable ldws example/readme md#running the examples brightscript a custom script containing the docid\ u6zceyqddlz9xdakttmjs object can be used to enable local access to the dws include the following lines in a autorun brs script to enable access to the dws on ethernet port 80 this example script also sets the password (replace "your password here" with a strong password) brightscript sub main() 	' create network configuration object (0 = eth0, 1 = wlan0, 2 = ppp0, usb0 and usb1 can be input as well) 	nc = createobject("ronetworkconfiguration", 0) 	dwsconfig = { port 80, open "your password here" } 	rebootrequired = nc setupdws(dwsconfig) 	nc apply() end sub javascript api local access to the dws can be enabled through the javascript api by using the script below this example script also sets the password (replace "your password here" with a strong password) const dwsconfiguration = require("@brightsign/dwsconfiguration"); const systemclass = require("@brightsign/system"); async function configureldws() { 	const system = new systemclass(); 	const dwsconfig = new dwsconfiguration(); 	const config = { 	 port 80, // http port for web interface 	 password { 	 value "your password here", 	 obfuscated false // password stored as plain text 	 }, 	 authenticationlist \["digest"] // use digest http authentication 	}; 	try { 	 dwsconfig applyconfig(config); 	 system reboot(); 	} catch (error) { 	 console error("configuration failed ", error message); 	} } configureldws(); serial prompt local access to the dws can be enabled through the player's serial port using the docid\ fxxyu9jmocutc6xe2p7l2 the following commands enable local access to the dws by writing to the player's registry this is the least preferred method of enabling local access to the dws as it does not set a strong password; it sets the player's serial number as the password registry write networking http server 80 registry flush a registry flush is necessary if you plan to power cycle the unit after executing the registry command registry writes will buffer for a few seconds because the eeprom and nand have a limited number of writes (and thus need to protect against carrying out too many writes too quickly) access the dws once local access to the dws has been enabled using one of the methods outlined above, you can access dws by entering the player's local ip address into your web browser note that there will be a redirect to a secure web connection (i e , https //{player ip}) if the player's ip address is not known, brightsign ${serial} local can be entered into the browser's address bar where {serial} is the serial number of the player as with entering the ip address, there will be a redirect to a secure web connection your browser may display a security warning to the effect of "your connection is not private" or "this connection is not secure" this occurs because the player is using a self signed ssl certificate which browsers do not automatically recognize as trusted this warning is expected and safe to bypass self signed certificates, while lacking third party validation, provide the same encryption protection as trusted certificates example see https //github com/brightsign/dev cookbook/tree/main/examples/enable ldws which demonstrates three different methods to enable and configure the dws on your player