Set Up a Transient Credential Store | Teradata Query Service - Setting Up Transient Credential Store - Teradata Query Service

Teradata® Query Service Installation, Configuration, and Usage Guide for Customers - 4.01.03.01, 4.01.07.00

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Teradata Query Service
Release Number
4.01.03.01, 4.01.07.00
Published
September 2023
Language
English (United States)
Last Update
2024-02-16
dita:mapPath
qla1666844235399.ditamap
dita:ditavalPath
ft:empty
dita:id
enn1467244092237
Product Category
Analytical Ecosystem
For improved security, the application can optionally use a token-based authentication instead of basic authentication. The token is sent with each request over a two hour period without you having to supply your credentials with each request.

No administrative actions are necessary to enable this feature if you are running a single instance of the Query Service.

Do the following when running multiple instances of the Teradata Query Service behind a load balancer:

  1. Switch the key store key strategy from random to hash on each server by adding credential.key.store.random=false to the /opt/teradata/rest/tdrest/application.properties file.
  2. Keep the credential store keys synchronized on all servers by manually copying the file /etc/opt/teradata/rest/credentials.jks from one server to the remaining servers.