You can set up encryption of sensitive data in the configurator so that they are AES encrypted. The AES key can be created or selected during configuration (see Configuration at Setting the encryption). The key should saved be on the server and can only be read by eBissService. You should backup the key file, in case all encrypted data is lost and cannot be restored. Note: You can activate crypting on existing systems but you must check and safe the passwords in the communication channels after activation of the crypting.

Note: It is possible to activate the encryption for systems that have already been created, but this can lead to passwords from existing communication channels having to be re-entered. Also, existing passwords are not encrypted until they are saved, which is why the communication channel has to be saved.

Following values encrypted:

• The db connection string in the config files (eBiss.Service.exe.config, eBiss.Service.exe32.config, etc.).
• Variable values of variables configured in the variable definition
• The passwords of following communication channels: FtpSendChannel, FtpReceiveChannel, FtpServerSendChannel, FtpServerReceiveChannel, Pop3ReceiveChannel, sFtpReceiveChannel, sFtpSendChannel, SmtpSendChannel, WebDavSendChannel, WebDavReceiveChannel.

The icon shows, if the value is encrypted (number lock) or just hidden (normal lock) (s. Encryption of sensitive data).

To use encrypted values in the job-step BackendObjectRetrieverEx using the variables of the standard system partner.You can also use encrypted values in the Job-Step BackendObjectRetrieverEx using the variables of the standard system partner. To do this, encrypt the variable of the default system partner and reference it using the prefix “$” in the variables of the BackendObjectRetrieverEx

For example, the value for the eBiss.DbAdapter.ConnectionString1. ConnectionString refers to the encrypted variable value eBiss.DbAdapter. ConnectionString1 of the default system partner in the following screen: