Certificate tab's home sub-tab page is shown as follow.
When an instance of SyncOffice Manager launched, it will copy default-group's template attributes data into certificate work place cache. The default-group is typically group-1, but administrator can change it in global level template's Group Assignment sub-tab.
After launch phase initialization, and then open a CSR, administrator can export the certificate cache into a new certificate file as "Create Certificate" operation.
Administrator can modify, manipulate the certificate cache data in many ways. One typical practice is to import an existing certificate into cache place and then update based on it, instead of using default-group data as template.
Similar to CSR, a certificate can be imported from its certificate repository directory, or from MySQL database.
The top section of the certificate tab is the GUI for searching a existing certificate and open it to cache.
The left side of top section is a FilelistView, showing the certificate files in \repository_certificate directory.
The right side of top section is a StringGrid which cell contents are from MySQL database's table_cert_list table.
Different from opening a CSR, opening a certificate takes a bit more resources and time. So administrator can use "Preview Header" to check if selected certificate is the right one, if true, then use "Open Cert File" for real open and import it.
As a common sense, administrator can establish a user level template database. Each end-user has own template of various rights. Once a CSR received from an end-user, administrator can import his user level template into certificate cache, do a few adjustments, and then create a new certificate file for his new CSR. The administrator can use "Import From User Template" button for such import work.
If administrator opens a CSR in CSR tab, then in certificate tab imported a certificate of another CSR, he goes into a situation that, he needs to specify if the certificate cache should use the CSR tab's CSR, or uses the certificate's owner CSR. This situation is in fact quite common. For example, if an end-user add a new laptop, administrator can import this end-user's existing notebook's certificate as template and apply his new laptop's CSR, since his attributes/rights on both PC should be the same.
The left bottom of top section is a GroupBox to let administrator choose "Use New CSR" or "Keep Cert's Existing CSR".
Some certificates are used for SyncOS OS, and some are for SyncOffice suite. If a certificate is used for SyncOS case, the certificate should feed the SyncOS Linux user's password. This Linux password is defined here in the bottom GroupBox of certificate home tab. If a certificate is only for SyncOffice suite application, no need to specify this password.
Once you changed SyncOS Linux password, you need to press "Set Data" button to save changed value into certificate cache.