This page explains "Configure SyncOffice Runtime Settings" menu operations and concept of runtime configuration.
On Login menu, select and press the third menu item will go into runtime setting configuration GUI, a Java dialogue window as follow.
If there is already an existing configuration ini file used in the last session, it will automatically select that last used configuration ini file. If it's the first time to run and no ini file used before, it will create a new configuration ini file using default settings. The configuration file name is in a format of sosession-yyyyMMddHHmm.ini, such as sosession-202105281023.ini.
Runtime Settings feature is applied in two different situations. One situation is SyncOffice freeware application. Freeware customer don't need certificate, don't need to login and do authorization. Under this freeware mode, SyncOffice only apply an extra password salt key upon ordinary password protection mechanism. When apply salt key on password, working PC's footprint hash is also applied if its option has been selected.
Runtime Settings another typical use situation is that a corporate user wants to switch work between his corporate realm and his own individual realm of documentation.
Corporate administrator can grant the Runtime Settings feature to an end-user. Its attribute flag is a remote controlled attribute, and can be changed or uploaded at any time by the administrator.
If the "Allow Runtime Config at SyncOffice Suite" attribute flag is set with the certificate, end-user can switch between the company realm and his own private one during a work session. Freeware customer can always switch between enabling runtime settings or disable it.
By default, the Runtime Settings is set to disable runtime settings, and use certificate settings if authorized. Click the "Use Runtime" button to enable runtime settings and disable certificate settings. After switch action done, GUI title shows "Currently Use Runtime Settings".
If you have chosen "Use Runtime" and close the Java configuration GUI, you are working in a runtime-setting session. This session will expire in 12 hours. Before it expires, if you reopen the configuration GUI, it will shows as "Currently Use Runtime Settings".
Once entering using runtime settings, "Set Option Data" button is enabled. All related option edit fields are also enabled. You can then configure all the option data, then press "Set Option Data" to make them effective. Each time you "Set Option Data" button to change the settings, 12 hours session counting restarts.
If you work in a runtime-setting session and close SyncOffice suite application, the runtime-setting status will keep a short period of time of several dozens of seconds, maximum 2 minutes. Within this short period of time, if you re-launch SyncOffice suite application and reopen runtime configuration GUI, it will shown up as "Currently Use Runtime Settings", and restart a new 12 hours session.
If you don't need to use runtime settings, click "Use Cert" button to disable runtime settings.
Among the options, the "Set Private Key" edit field is the most important configuration item. The shown content is an encrypted form of previous set private salt key. When you set a new private key, enter a 2 - 30 char length alpha-numeric string. Once it's saved into its storage ini file by pressing "Set Option Data" button, it will be encrypted and then shown as such encrypted form.
Once you chose "Use Private Key", you have an option of "Use Device Footprint" or not. Using device footprint is safer, as it will protect your document that it can only be opened from the PC where it is created. This feature relies on PC hardware feature, and not all PC have set their hardware id right. So it may not apply to the PC on your hand. That is why Teleon set this feature as an option to let you have flexibility of selection.