Web Viewer – Start parameters

All possible parameters for the web browser are listed below.

Direct page view

To display a specific page in the web browser, only the page name needs to be added to the link. For example, if the page “Page2” is to be displayed in the current project, this can be accessed via the following link:

https://localhost:6070/Page2

Language

The syntax of the call is different for switching the language; in this case, the language with the following syntax can be selected:

https://localhost:6070/?lang=nl

On-screen keyboard

The activation of an on-screen keyboard can be achieved via the following link:

https://localhost:6070/?onscreenkeyboard=qwertz

Automatic login

ℹ️ Available from QuickHMI 10.1.2

If the security system is active, the login can be performed directly with the call, so the login dialog is skipped. To do this, the user name and password hash are passed in the auth parameter, separated by a colon:

https://localhost:6070/?auth=<user name>:<password hash>

The password hash is not the password itself but its SHA-256 hash as a hexadecimal value in lowercase letters (64 characters). For the user “Operator” with the password “secret”, the call is:

https://localhost:6070/?auth=Operator:2bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b

You can create the hash on Windows in PowerShell, for example:

-join ([Security.Cryptography.SHA256]::Create().ComputeHash([Text.Encoding]::UTF8.GetBytes('secret')) | ForEach-Object { $_.ToString('x2') })

On Linux:

printf '%s' 'secret' | sha256sum
  • Further parameters are appended with &, e.g. ?auth=Operator:<password hash>&lang=en.
  • The user name must not contain a colon. Special characters in the user name must be URL-encoded, e.g. a space as %20.
  • If the login fails, the usual login dialog appears. An incorrect hash counts as a failed attempt and can lock the user.
  • After a password change, the call must be updated with the new hash.

⚠️ Security note: Anyone who knows the call can log in with it. The hash fully replaces the password and must be protected just as carefully. In addition, a simple password can be recovered from its hash. The call is stored in the browser history, in bookmarks and possibly in proxy logs. Therefore only use automatic login on permanently installed, trusted devices such as operator panels, create a dedicated user with only the required permissions for this purpose, use HTTPS and do not pass the call on.