Starting from 5.4.26 version stored on terminal local disk terminals' configurations can be edited only by https and it's password protected. For now it concerns only terminal configuration and config.txt for Raspberry, but it's not the end.
There's one problem: https is made for real servers. And these servers have previously known names. Needed for https encryption certificated are bound to server name or IP address. But we don't know neither names nor addresses of your WTware terminals.
It's impossible to release https certificate to arbitrary IP. Browsers do not understand it.
It's impossible to release https certificate to any name. The best thing that browsers agree to acccept is arbitrary part of domain name at the third level.
There are three ways:
Our root certificate is available from any terminal. Open by http (not https) terminal IP in browser and open "About HTTPS" section. When you install certificate in Firefox select this item:
Internet Explorer and Chrome:
Certificate is released for *.wtware.local. Configure DNS so that terminals' names were in this zone.
Then in browser you will enter names, not terminal IPs. Easy and boring way: in Notepad manually add to
C:\Windows\System32\drivers\etc\hosts file several lines for needed terminals:
192.168.5.25 term1.wtware.local 192.168.5.26 term2.wtware.local 192.168.5.33 buh.wtware.local
More interesting way is to configure DNS. WTware is able to send DNS updates during configuration by DHCP. Manual for configurating DNS updates from DHCP in Windows is available in Google.
If you don't want to install our root certificate. Or if you want to use other names, not from *.wtware.local.
certreq.exe -new https.inf https.reqShould be like that:
This certificate is also released for *.wtware.local names. DNS is to be configured anyway. But you can bound certificate to other names by editing https.inf.
When root certificate is successfully installed and DNS terminal name is specified, you should see such result: