16.20 - Allowing Passwords to be Saved to History - Teradata SQL Assistant

Teradata® SQL Assistant for Windows User Guide

Product
Teradata SQL Assistant
Release Number
16.20
Published
October 2018
Language
English (United States)
Last Update
2020-01-03
dita:mapPath
gfk1537201040714.ditamap
dita:ditavalPath
ft:empty
  1. Create the registry key:
    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Teradata\Client\Security
  2. Create a DWORD value with the name MaskPasswordInHistory within this key.

A value of 0 prevents the password from being masked in both the history file and the Query window. Any other value causes passwords to be masked. If the Key or Value is missing, then passwords will be masked.

If you allow passwords to be stored in history, apply security restrictions to your history file so that others can’t read those passwords.

To fully enforce this rule. set up a security policy to prevent any user from modifying or deleting this registry key.

To retrieve standard scripts used for creating users, a better option is to create an SQLSet using Query Builder. SQL Set files are always stored under the user's AppData branch and are therefore already restricted by the OS.