Global - Certificates
A certificate binds a public key to an identity, such as a person, a company or a server, and is signed so that others can check that binding. VisualCron stores standard X.509 certificates centrally on the Server, so that the Email Task (see Task Messaging - Email) and Connections that authenticate with a certificate can reuse them. This page describes the Manage certificates window, where you import, export, create and delete certificates.
To open the window, click the main menu Server -> Global objects -> Certificates. You need the Certificates permission with Read (see Permissions below).

The grid has these columns:
- VCName: the name that identifies the certificate inside VisualCron. Change it with Set name
- Common Name: the common name in the certificate's subject
- Email: the email address in the certificate's subject
- Issuer Name: currently stays empty in this window
- Self signed: "Yes" when the certificate is self-signed
- Private key: "Yes" when the certificate includes its private key
- Can encrypt: "Yes" when the certificate can be used for encryption
- Can sign: "Yes" when the certificate can be used for signing
- Key valid: "Yes" when the certificate's key is valid
The toolbar has these buttons, from left to right: Import certificate, Export certificate, Create certificate, Delete certificate, Audit log and Get from Windows. Each is described below.
Right-click a row for these commands:
- Set name: change the name in VCName, in the Set certificate name window
- Copy Certificate Id: copy the certificate's identifier to the clipboard
- Change Certificate Id: enter a new identifier in Enter new Certificate Id. The new identifier must be in GUID format, and no other certificate may already use it. VisualCron tells you how many objects will change with it. Click Yes to continue, or No to see the list first. The objects that use the certificate are updated to the new identifier
- Audit log: the audit log entries of this certificate
- Versions..: the version history of the certificate
- Object relations: the objects that use the certificate
- Export ...: export the selected certificates (see Import/Export - Export Settings)
- Send to connection ... and Send to server connection ...: copy the certificate to the Server that a VisualCron Connection points to, or to another Server this Client is connected to
In the grid, press Delete to delete the selected certificate, or Ctrl+A to select every row.
Import certificate
The file is read by the Client, on the computer it runs on. When the Client is connected to a Server on another computer, the file window shows the Server's folders. The file is then usually not found, or a file with the same path on the Client computer is read instead. In that case, the file type you select is also ignored: every file is read as a binary ".cer" or ".der" certificate, so a ".pem", ".pfx" or ".p12" file can't be imported. Import certificate files from a Client running on the Server computer.
Click Import certificate and select a certificate file. Select the file type in the file window to see your files:
- Binary Encoded Certificate (*.cer;*.der)
- PKCS7 SPC (*.spc)
- PEM Encoded Certificate (*.pem)
- PKCS12 Certificate (*.pfx;*.p12)
- Binary Encoded Certificate - Public key only (*.pub;)
To import a private key together with a ".cer", ".der" or ".spc" certificate, place the key in the same folder, under the same name with the extension ".key" or ".pvk". VisualCron then asks Do you want to load the private key file ...?. For a ".pvk" file, it also asks for the key's password in the Enter password window. You can't select a ".key" or ".pvk" file directly.
For a ".pem", ".pfx" or ".p12" file, VisualCron asks for the file's password in the Enter password window.
Export certificate
If you leave the password empty, or cancel the Enter password window, the private key is saved without a password, and anyone who gets the file can use the key. Always enter a password.
The ".key" file of a ".cer" export holds the private key without a password. Keep it in a protected place.
The file is written by the Client, on the computer it runs on. When the Client is connected to a Server on another computer, the save window shows the Server's folders, but the file is written to that path on the Client computer. In that case, the file type you select is also ignored: the certificate is always saved as a binary ".cer" file, and if you click Yes for Save private key?, the private key is saved without a password. Export certificate files from a Client running on the Server computer.
Select a certificate and click Export certificate. Select the file type in the save window:
- Binary Encoded Certificate (*.cer): if the certificate has a private key, VisualCron asks Save private key?. If you click Yes, the key is saved in a ".key" file with the same name
- PEM Encoded Certificate (*.pem): if the certificate has a private key, VisualCron asks for a password in the Enter password window, and saves the key protected with it
- PKCS12 Certificate (*.pfx): if the certificate has a private key, VisualCron asks for a password in the same way
Get from Windows
To import certificates from a Windows certificate store, complete the following steps:
- Click Get from Windows. The Import certificates window opens.
- In Certificates store type:, select the store: "My", "Root", "AuthRoot", "Address book", "Certificate authority", "Trusted people" or "Trusted publisher".
- Select Local machine (the default) or Current user. On the Server computer, Current user is the store of the account that the VisualCron Server service runs as.
- Choose the computer whose store is read. Check the box to read the store on the computer running the Client, or leave it cleared to read the store on the Server computer. When the window opens, the cleared box reads From client machine. After you change it, its label shows the current choice: From client machine or From server machine.
- Click Get. The certificates in the store are listed. Double-click a row to see its details.
- Check the certificates you want, or use the checkbox in the column header to check them all, and click Import.
The certificates you checked are added to the grid of the Manage certificates window. Only the certificate is imported, not its private key. To import a private key, export the certificate with its private key from Windows as a ".pfx" file, and use Import certificate.
Create certificate
The wizard preselects md2 / RSA and a public key strength of "512" bits. Both are too weak for current use, and certificates made with them are not secure. Select sha256 / RSA and "2048" or "4096" bits for every certificate you create.
Click Create certificate to open the Certificate generation wizard. VisualCron creates self-signed certificates.
Step 1: name and type
Enter a name in Name:. The name identifies the certificate inside VisualCron, is shown in the VCName column, and is required. Under Type of Certificate, Self-signed certificate is the only option.

Step 2: hash algorithm and key strength

- Hash algorithm offers md2 / RSA (preselected), md5 / RSA, sha1 / RSA, sha1 / DSA, sha256 / RSA and sha256 / DSA
- Public key strength (bits) offers "256", "512" (preselected), "768", "1024", "2048" and "4096"
Step 3: subject information
Under Subject info for new certificate, fill in Country:, State/Province:, Locality:, Organization:, Organization unit: and Common name:. These are required. Email: is optional.
Fill in Email: if you will use the certificate in the Email Task (see Task Messaging - Email).
Step 4: validity period
Under Validity period for certificate, From: starts at today's date and To: starts at one year from today. Change them as needed.
Click Next > to create the certificate. The request is sent to the Server, and the wizard closes. The Generation started message tells you that the certificate appears when it has been created. This can take up to five minutes, depending on the key size and the Server's speed. When the certificate is ready, it appears in the grid, and a message says that it was generated successfully.
To leave the wizard without creating a certificate, click Cancel and confirm.
Delete certificate
Select a certificate and click Delete certificate, or press Delete. VisualCron asks you to confirm. If other objects use the certificate, the question says how many, and you can open Object relations first to see them.
Permissions
Certificates are governed by the Certificates permission (see Main - User Permissions and Supported Permissions):
- Read: open the Manage certificates window and see the certificates, and also export a certificate with its private key
- Add: Import certificate, Create certificate and importing with Get from Windows
- Edit: Set name and Change Certificate Id. Without Edit, a new name is not saved, and no message is shown
- Delete: Delete certificate
The file windows for import and export also need the Remote file explorer permission with Read.
Read alone lets a user export a certificate together with its private key. The built-in Viewers group has Read on Certificates. Clear it in the Viewers group, and give Read on Certificates only to users you trust with the private keys.
Certificate file formats
| Format | Import | Export | Private key |
|---|---|---|---|
| PFX or P12 (PKCS #12) | Yes. VisualCron asks for the file's password | Yes, as .pfx. VisualCron asks for a password | In the same file, protected with the password |
| PEM | Yes. VisualCron asks for the file's password | Yes, as .pem. VisualCron asks for a password | In the same file, protected with the password |
| CER or DER | Yes | Yes, as .cer | In a separate .key file. On import, a .pvk file is also accepted |
| SPC (PKCS #7) | Yes | No | In a separate .key or .pvk file |
| PUB | Yes, public key only | No | None |