Password Issues with S3 embedded software

The major web browsers have recently changed the, default, way that they handle “cookies”, or more specifically third-party cookies. The S3 SATSIO, the S3 De-Ice controller, and the S3 Waveguide Switch controller all use cookies to manage password tokens and so when the web browser is updated passwords will fail to work.

This is specifically related to using dotted IP addresses for the SATSIO in the browser, when the browser treats all cookies as “third party” cookies.
A software update is available for the S3 products which fixes this problem – please contact the factory to obtain it using the options on the contact page. Note that S3 Satcom will need to know which product you need the update for and the current software versions (found on the About tab on the web browser interface – which will still work).

Updating the software will result in a permanent resolution of this issue but for an immediate fix, there are several work-arounds that will restore functionality. Each work-around has its own advantages and disadvantages and these are set out below - you should only need to apply one of these:

Add the equipment host name/address to the networks DNS server

Advantages:
• Fixes the problem for all browsers

Disadvantages:
• Not many sites run a DNS server!

Add a fake hostname to the Windows hosts file

Advantages:
• Fixes the problem for that PC

Disadvantages:
• Since the hosts file is a Hidden System file it is not easy for a casual user to change
• Has to be done on each PC used to access the S3 product

Procedure:
• Run Notepad.exe as an administrator (type Notepad.exe into the start menu, right click the entry that appears “notepad.exe” and select “Run as administrator”)
• Go to the “File” “Open” menu
• In the Filename box type “C:\Windows\System32\drivers\etc\hosts”
• Click “Open”
• Add a line similar to the following – replacing the IP address with the actual address, and replacing “mysatsio.com” with the domain name you want to use (NOTE that this must be a syntactically correct URL, for example it must end .com, or .co.uk etc)
  "192.168.0.157   mysatsio.com"
• Save the file
• In the web browser navigate to mysatsio.com (instead of 192.168.0.157)

Totally disable all passwords in the S3 product

(This is still possible, as it uses a direct password check instead of a token stored in a cookie).

Advantages:
• Fixes the problem for all browsers

Disadvantages:
• Anyone with browser access can make changes to the unit

Procedure:
• In the S3 Web interface go to “Maintenance” and “Password Config”
• Tick both “Disabled” boxes
• Enter the current Admin password
• Click “OK”

Enable third party cookies in the browser

Advantages:
• Fixes the problem
• Allows password control over the equipment

Disadvantages:
• It is applied universally and not just for the S3 product
• Has to be done on each PC used to access the S3 product

Go to top