Encryption and Keystore Configuration

Encryption protects data within Mobiliser from unauthorized access using methods and a key or keys to encode plain text into a unreadable ciphertext. A key is required to decrypt the encrypted information and make it human-readable again. Keystores securely store and manage encryption keys.

• Encryption in MOB_PREFERENCES
  Preference configuration values are stored encrypted in the MOB_PREFERENCES table.
• Keystore Configuration
  Keys are used in Mobiliser to secure communication between hosts (HTTPS) and to encrypt sensitive information, for example, credit card data. By default, Mobiliser does not contain any keys; you must create them as part of the overall installation process.
• Creating the Keystore for Data Encryption
  For credit card payments, the default Mobiliser configuration uses asymmetric encryption to secure credit card and bank account information in the front end, and a dummy payment handler implementation in the back end to decrypt credit card payments.
• Encrypting Preferences Using Operations Dashboard
  After installation, you might need to change some application configurations, such as entering an encrypted value for passwords.