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

Database name for the Hive database.

Classpath of the Hive 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. For example, you might enter the following location for Windows:

C:\JDBC_Drivers\Hive\hive\*;C:\JDBC_Drivers\Hive\hadoop\*

Fully qualified class name of the Impala driver specified in the

Driver Classpath

property.

JDBC connection URL based on the driver.

When you connect to a Hive database with Kerberos authentication enabled, specify the server principal of Hive, 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 preconfigured for use with Dynamic Data Masking.

Optional user name for the database user account to log in to the Hive database. The database user must be a privileged user that has SELECT access to all the tables that the client user has SELECT access to. This parameter is valid for the default keystore.

Leave this parameter blank if the Hive 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 Hive database has Kerberos authentication enabled.

Name of the custom keystore, 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 during creation of the CyberArk account. This parameter is valid for custom keystores.