Table of Contents

Search

  1. Preface
  2. Introduction to Dynamic Data Masking Administration
  3. Authentication
  4. Security
  5. Connection Management
  6. JDBC Client Configuration
  7. ODBC Client Configuration
  8. Configuration for MicroStrategy
  9. Access Control
  10. Logs
  11. High Availability
  12. Server Control
  13. Performance Tuning
  14. Troubleshooting
  15. Appendix A: Database Keywords

Administrator Guide

Administrator Guide

Generic Database Connection Parameters

Generic Database Connection Parameters

Define the following connection parameters for a database that uses an ODBC or JDBC connection:
DDM Database Name
Name for the database in the Management Console tree.
Driver Class Name
Fully qualified class name of the target database driver.
For example, you might enter the following text:
org.netezza.Driver
Connect String (URL)
JDBC connection string used to connect to the database.
For example, you might enter the following text:
jdbc:netezza://hostname:port/database_name
Optional Parameters
Optional parameters for the Informatica driver for the database.
DSN Name
Logical data source name used to connect to the database.
Unary Table
Name of the unary table for the database.
Bind Argument Representation
Representation of the bind argument for a PL/SQL stored function.
Supports ANSI Join
Select if the database supports ANSI join syntax.
Are Function Calls Allowed in Select
Select if the database allows a function call to be included in a SELECT statement.
Are Parentheses Allowed for Function Call with No Arguments
Select if the database allows parentheses in a function call that does not have any arguments.
Command to Get Data for Impersonation
The SQL command that Dynamic Data Masking uses to retrieve the data required for impersonation.
For example, you might enter the following command to retrieve the search_path for a Greenplum database:
SELECT COALESCE(substring( useconfig[1] from '%=#"%#"' for '#' ), substring( datconfig[1] from '%=#"%#"' for '#'), 'PUBLIC') as AUTH_CURRENT_SCHEMA from pg_user pguser, pg_database pgdatabase where pguser.usename= '\(AUTH_USERNAME)' and pgdatabase.datname= '\(AUTH_CATALOG)'
Execute Command to get Impersonation Data for Every Request
Select to indicate that Dynamic Data Masking must retrieve the data for impersonation for each request. If the check box is unchecked, Dynamic Data Masking retrieves the data once per session.
Impersonation Commands
Impersonation commands for the database, separated by a semicolon (;) and a line break. Words that are preceded by a backslash and left parenthesis and followed by a right parenthesis are Dynamic Data Masking symbols that Dynamic Data Masking replaces with symbol values. For example, \(SYMBOL).
For a Greenplum database, you must set the AUTH_CURRENT_SCHEMA symbol. You can use the following command to set the symbol:
SET SEARCH_PATH = \(AUTH_CURRENT_SCHEMA)
Cleanup Commands
Cleanup commands for the database, separated by a semicolon (;) and a line break.
Sanity Check Script
Sanity check script to verify that the Dynamic Data Masking connection to the database is valid.
Keystore
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.
DBA Username
Username for the database user account to log in to the 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.
DBA Password
Password for the database user.
Key Store Name
Name of the custom keystore, defined in the
ddm.security
file. This parameter is valid for custom keystores.
Alias
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.

0 COMMENTS

We’d like to hear from you!