Setting Up Transient Credential Store - Teradata Query Service

Teradata® Query Service Installation, Configuration, and Upgrade Guide for Customers

Product
Teradata Query Service
Release Number
2.08
Published
October 2018
Language
English (United States)
Last Update
2018-10-25
dita:mapPath
deq1519325809568.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-2700
lifecycle
previous
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 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.