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

Client Configuration

Client Configuration

After you configure the
ddm.security
file, configure the client.

JDBC Client Configuration

The Dynamic Data Masking host and port in the client JDBC URL must point to the Dynamic Data Masking Hive service host and port. The principal in the client JDBC URL must be the Dynamic Data Masking Server principal name.
You can connect to the client using a direct connection or you can connect to the client through Dynamic Data Masking. In the client connection URL, add the property
SaslQOP
using one of the following formats:
JDBC URL (Direct Connection)
If you are connecting to the client directly, use the following format:
jdbc:hive2://<HiveServer2 Host>:<HiveServer2 Port>/;principal=<Server Principal of Hive >;SaslQOP=auth-conf;
JDBC URL (Connection through Dynamic Data Masking)
If you are connecting to the client through Dynamic Data Masking, use the following format:
jdbc:hive2://<DDM Server Host>:<DDM Service Port configured in ddm.secuirty>/;principal=<Server Principal of DDM>;SaslQOP=auth-conf;

ODBC Client Configuration

Configure the ODBC client through the Windows ODBC Data Source Administrator and create the ODBC data source. When you create the ODBC Data Source, select
Thrift Transport
SASL
.

0 COMMENTS

We’d like to hear from you!