Name for the database that appears in the Management Console tree.

Database name for the Impala database.

Classpath of the Impala database driver files on the Dynamic Data Masking Server. Use semicolons to separate multiple classpaths.

You can use an asterisk (*) to indicate all the jar files in a directory. Dynamic Data Masking ignores files in the directory that are not jar files.

Example for Windows:

C:\JDBC_Drivers\impala\*

Example for Linux:

/root/cloudera/impala/*

JDBC connection URL based on the driver.

When you connect to an Impala database with Kerberos authentication enabled, specify the server principal of Impala, even though it is included in the JDBC URL. Otherwise, leave this parameter blank.

Select custom if you have configured a custom keystore. Select default if you want to use the default keystore that is preconfigured for use with Dynamic Data Masking.

Name of the custom keystore that you defined in the

ddm.security

file. This parameter is valid for custom keystores.

Alias name for the custom keystore. For CyberArk accounts, the alias name was defined when the CyberArk account was created. This parameter is valid for custom keystores.

Optional user name for the database user account to log in to the Impala database. The database user must have SELECT access privileges for all the tables to which the client user has SELECT access privileges. This parameter is valid for the default keystore.

Leave this parameter blank if the Impala database has Kerberos authentication enabled.

Optional password for the database user. This parameter is valid for the default keystore.

Leave this parameter blank if the Impala database has Kerberos authentication enabled.