Global - SSH Keys
SSH keys are used for public key authentication. A key pair is a private key, which stays with the client that logs on, and a public key, which you place on the remote server.
VisualCron stores SSH keys centrally on the Server. You can then select them in the SFTP, SCP and SSH Connections (see Connection - SFTP, Connection - SCP and Connection - SSH), which Tasks such as the FTP Task use (see Task Net - FTP/FTPS/SFTP/SCP). You create or import a key once, instead of pointing every Connection to a key file. This page describes the Manage SSH Keys window.
To open the window, click the main menu Server -> Global objects -> SSH keys. You need the SSH keys permission with Read (see Permissions below).

The grid has these columns:
- Name: the name that identifies the key inside VisualCron
- Algorithm: "RSA", "DSS", "ECDSA" or "EDDSA"
- Bits: the key length
- Public Key: "True" for a public key, "False" for a private key
- SHA256 Fingerprint: the SHA256 fingerprint of the key, to check its identity
The toolbar has these buttons, from left to right: Import public SSH key, Import private SSH key, Export SSH key, Create SSH key pair, Delete SSH key and Audit log. Each is described below.
Right-click a row for these commands:
- Set name: change the key's name, in the Set SSH key name window
- Copy SSH key Id: copy the key's identifier to the clipboard
- Change SSH key Id: enter a new identifier in Enter new SSH key Id. The new identifier must be in GUID format, and no other SSH key 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. Currently, the change does not take effect on the Server: the key, and the objects that use it, keep the old identifier, and after a while VisualCron shows an error. The Clients that are logged on show the new identifier until they reconnect
- Audit log: the audit log entries of this key
- Versions..: the version history of the key
- Object relations: the objects that use the key
- Export ...: export the selected keys (see Import/Export - Export Settings)
- Send to connection ... and Send to server connection ...: copy the key 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 key, or Ctrl+A to select every row.
Create SSH key pair
Click Create SSH key pair. In the SSH key pair generation window, under Key properties:
- Name: sets the name that identifies the key inside VisualCron. It starts as "NewKey"
- Protocol type: sets the algorithm: "RSA" (the default), "DSS", "ECDSA" or "EDDSA"
- Key length (bits): offers lengths that depend on the protocol type: "2048" (the default) or "4096" for "RSA" and "DSS", and "256" (the default) or "384" for "ECDSA"
- Passphrase: sets the passphrase that protects the private key. It may be left empty
Enter a passphrase. A key created without one is stored, and later exported, without protection.
Click Generate. The Server creates the key pair and adds two rows to the grid: the private key under the name you entered, and the public key under the same name followed by ".pub". A message tells you when the new key has been generated. Export the public key to place it on the remote server.
To close the window without creating a key, click Cancel and confirm.
Import public SSH key
Click Import public SSH key and select a public key file (".pub"). The key is stored under the file's name, extension included.
Import private SSH key
Click Import private SSH key and select a private key file. VisualCron first tries to import the key without a passphrase. If that fails, for example because the key is protected, it asks for the passphrase in the Enter password window and tries again. The key is stored under the file's name.
The VisualCron Server, not the Client, reads the key file. Select a file on the Server computer, or on a share that the account the VisualCron Server service runs as can read. When the Client is connected to a Server on another computer, the file window shows the Server's folders. If the Server can't read the file, the import fails after the passphrase prompt, and the error says that the file does not exist or that access was denied.
Export SSH key
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. Export keys from a Client running on the Server computer.
Select a key and click Export SSH key, then choose where to save the file. A private key is saved protected with the passphrase stored with the key. A key that has no passphrase is saved without protection. A public key is saved in a ".pub" file. VisualCron says Key exported. when the file is written.
Delete SSH key
Select a key and click Delete SSH key, or press Delete. VisualCron asks you to confirm. If other objects use the key, the question says how many, and you can open Object relations first to see where the key is used.
Permissions
SSH keys are governed by the SSH keys permission (see Main - User Permissions and Supported Permissions):
- Read: open the Manage SSH Keys window and see the keys, and also export a key, private keys included
- Add: Create SSH key pair, Import public SSH key and Import private SSH key
- Edit: Set name and Change SSH key Id. Without Edit, a new name is not saved, and no message is shown
- Delete: Delete SSH key
The file windows for import and export also need the Remote file explorer permission with Read.
Read alone lets a user export a key together with its private key.
The built-in Viewers group has Read, Add, Edit and Delete on SSH keys, so its members can export, add, change and delete keys. Clear these permissions in the Viewers group, and give them only to users you trust with the private keys.