Encrpytion keys for single modules are created in the JRSETTINGS table during the installation of JobRouter or the update to JobRouter version 5.1.
Please note: Please perform the update to JobRouter version 5.1 on the main instance first, otherwise errors may occur.
The Encryption codes are used for the encryption data worthy of protection (e.g. for passwords) of different JobRouter modules.
Please note: To avoid data loss we recommend to perform an additional Backup of the keys. In the optimum case, this is part of the regular Backup of your JobRouter web application.
The keys are additionally encrypted with the Instance key.
Please note: In case of an Instance key loss it is not possible to retrieve the data that has been encrypted with it. We recommend a complete Backup of your JobRouter web application.
Key |
Intended use |
|---|---|
database.key |
Is used for the encryption of passwords of external database connections. These are Global Connections and Database Connections in the processes. |
general.key |
We use the following data for encryption: •JobRouter Passphrase in the Security Settings •Database password in the JobSync configuration •Database password in the JobData configuration •SMTP Authentification password in the JobMail configuration •Password of the RabbitMQ configuration |
jobarchive.key |
Is used for the encryption of Memory keys and passphrases for the JobArchive Result lists. |
jobselect.key |
Is used for the encryption of passwords in the JobSelect configuration. If a Global Connection is selected, the respective password is used, which will not be saved in the JobSelect configuration. |
jobshift.key |
Is used for the encryption of passwords of JobShift archive connections. |
jobstart.key |
Is used for the encryption of passwords of JobStart e-mail inboxes. |
ldap.key |
Is used for the encryption of passwords of the LDAP directories. |
Please note: Further keys are listed in the chapter Key backup. Solely their location is different.
