Security Settings | Teradata QueryGrid - Teradata QueryGrid Security - Teradata QueryGrid

Teradata® QueryGrid™ Installation and User Guide

Teradata QueryGrid
Release Number
July 2022
English (United States)
Last Update
Product Category
Analytical Ecosystem

QueryGrid Manager Root Certificate Authority

A QueryGrid Manager instance can be installed on one or more TMSs, VMs, or servers. When the first QueryGrid Manager instance is installed, QueryGrid Manager generates a root certificate authority (CA). If additional QueryGrid Manager instances are installed and all instances are clustered, the root CA generated by the first QueryGrid Manager instance is used throughout the cluster.

The root CA must be registered in Viewpoint during Teradata QueryGrid installation.

The root CA signs SSL certificates for each QueryGrid Manager instance.

QueryGrid Manager SSL Certificates

Each QueryGrid Manager instance generates an SSL certificate for secured communication between itself and all other clients such as:
  • Additional QueryGrid Manager instances in the same cluster
  • Data source nodes in a system
  • Viewpoint
  • Browser to QueryGrid Manager REST API documentation
  • REST clients
External access to port 9443 is allowed for Viewpoint, Swagger UI access, and REST clients. The SSL certificate for port 9443 is customizable. Certificates used by ports other than 9443 are intended for internal QueryGrid traffic only and cannot be customized. These certificates are generated during QueryGrid installation and are provided to each QueryGrid component during deployment to authenticate that communication is with a trusted QueryGrid service. Rotation of the certificates can be performed on a periodic basis, see Certificate Authority Rotation. For more information, see Installing/Uninstalling a Custom Server Certificate.

When a data source node is added to a data source system in QueryGrid, a QueryGrid Manager instance gives the node an SSL certificate during node software installation. The SSL certificate, which is signed by the root CA, allows the data source node to verify that communication is with a trusted QueryGrid Manager instance.

All communication between the QueryGrid Manager instances and data source nodes within the fabric use HTTPS over port 9444.

QueryGrid Manager Service Accounts

QueryGrid Manager service accounts provide the access to call QueryGrid Manager APIs. These accounts are internal to QueryGrid Manager and do not correspond to any database or operating system user accounts. The service accounts only provide access to QueryGrid configuration and monitor data.

Service accounts named viewpoint and support are automatically created using default passwords when QueryGrid Manager is initially started. Teradata strongly recommends changing the default password for these accounts. For more information about changing passwords, see Changing a Service Account Password or Resetting a Service Account Password if the password is forgotten.

Authentication and Registration of Data Source Nodes

When a data source node is added to a data source in QueryGrid, node software is installed on the node, and a node service registers the node with a QueryGrid Manager instance. The node service provides the following:
Item Description
UUID Acts as the node username when the node authenticates itself to a QueryGrid Manager instance.
Time-limited access token Authenticates the node before the node can be added to a data source for the first time.
Generated password for authentication Allows the node to authenticate itself to a QueryGrid Manager instance after the node joins a data source for the first time.

IP Addresses and Hostname Verification

When the first Teradata QueryGrid Manager instance starts, the generated SSL certificate contains the IP address for the QueryGrid Manager TMS, VM, or server and the hostnames known to Teradata QueryGrid Manager so that clients can perform host verification.

If the Teradata QueryGrid Manager is accessed by unknown hostnames or IP addresses, you can add them to the SSL certificate by setting an alias property, which can contain a comma-separated list of hostnames or IP addresses. Procedures for adding aliases are included in the installation procedures in this guide.

Data Transfer

QueryGrid connectors use the QueryGrid fabric to transfer data between source and target systems. Data transfer is performed using the following processes:
  • A fabric process runs on each attached node running QueryGrid.
  • The connector establishes a channel with the local fabric node to send and receive data.
  • The fabric only allows connections from local connector processes in the allowed OS user list defined on the connector.
  • As of QueryGrid 2.15, fabric processes communicate using TLS 1.2+.
    • All data is encrypted by default and each fabric process generates a public/private key pair used for mutual authentication with other fabric processes.
    • The private key is maintained in memory and the public key is sent and distributed by QueryGrid Manager.
    • Keys are rotated once a week.

OS Users

Security also depends on the OS user the connector software uses. You can specify the OS user for each connector. The user is typically the same user as the data source user.

Data Source User
Teradata system teradata user
Presto starburst user
Hive user executing the query (which may be hive), yarn user, and Kerberos principal or other authorized user
Spark SQL user executing the query (which may be hive), yarn user, and Kerberos principal or other authorized user

LDAP and Kerberos

Supported security mechanisms for a target connector are different for Teradata, Presto, and Hive connectors. For information about security mechanisms specific to a data source, see the appropriate connector security sections.

General Security Guidelines for Teradata QueryGrid

The following guidelines represent best practices for maintaining security for Teradata QueryGrid.
  • Change Teradata QueryGrid Manager service account default passwords during installation. Procedures are provided in this guide.
  • Set appropriate permissions in Viewpoint to limit the users who can edit the Teradata QueryGrid configuration.
  • Create links using only initiator data sources running in secure environments.
  • Use the security option appropriate to the environment when specifying communication policies for links.