Password Encryption


openLooKeng manages configuration details in properties files of catalogs. These files may need to include values such as usernames, passwords and other strings, the password often required to be kept secret, that can’t be stored as plaintext. Here is a typical configuration file of a MySQL connector:

openLooKeng can be configured to enable password encryption, these passwords will be encrypted.


The asymmetric encryption algorithm (RSA) is used for encrypting password.


  • Private Key: for encryption, client can use private key to encrypt plaintext.
  • Public Key: for decryption, server store the public key as a keystore file in filesystem, and server can use public key to decrypt the ciphertext.

The user saves the secret key and gives the public key to openLooKeng to decrypt the encrypted ciphertext.

The key suggested size of RSA is 3072 bits, the minimum is 2048 bits.


To enable password encryption, you need add these properties in the etc/

Property Description
security.password.decryption-type The type of password decryption. Should be set to NONE or RSA.
security.key.manager-type=keystore The type of password encryption key storage. Should be set to keystore.
security.key.keystore-password The password of keystore. The filesystem path of keystore file.

Use Case

Case 1. Dynamic Catalog

A http request has the following shape (MySQL connector as an example):

request: POST/PUT
header: 'X-Presto-User: admin'
form: '
  • securityKey: The public key.
  • connection-password: The ciphertext encrypted with private key.
  • encrypted-properties: The encrypted property names.

Check dynamic catalog for more information.