Q.1) In case of encryption of the personal data like user name, ID’s and other fields in database, how the database level integration is possible for third party integration?
For DB level integration, we are going to update the explanations how we encrypt and decrypt. But it will take time and we should check further. We will make the technical guidance.
Q.2) What TLS versions are supported by the new biostar version?
Currently, TLS v1.1 and TLS v1.2.
Q.3) Will the new encryption method applied to all field of user information? Including CUSTOM FIELD? Also, can we control which specific field to be encrypted?
Good question, the custom field will be encrypted.
But, we do not have the option for the specific field to be encrypted.
Q.4) When we change the Java to Open JDK , what about the existing 2.7 with Java ? can we do the upgrade easily?
Open JDK will be included into BioStar 2 v2.8.7. Once it is ready, we will announce how to handle current JAVA also. It will be easily upgraded.
Q.5) When we get a device for RMA from a customer where he can't remember the admin device pw / fp, and TLS is activated, is there a way to factory reset the device from some network SW tool?
Unfortunately, we do not have the tool to release the status for the repair purpose. We will check if there is an easy way to handle such case.
Q.6) The TLS for devices is available from which firmware versions?
You can find the information to the link.
Q.7) If TLS is in action and BioStar 2 Server got crashed how we will add the devices with other server?
We recommend making a backup for TLS certificate before the server is crashed. For the progress of backup, please refer to the link here.
Note : If you enable the "Secure Communication with device" option, you will have to back up the cert folder in the path below.
C:\Program Files\BioStar 2(x64)\cert