My connectivity with TD is almost from third party ETL tool. ETL tool can create encrypted password to logon teradata.
I am wondering that how is it possible to connect with teradata without exposing password for example through bteq script. I have ever seen a possible solution is invoking .LOGON bteq command through external file by using .RUN FILE=C:\... That external file is set with specific privilege to avoid exposing password.
Is there any other way to use encrypted password for logon teradata? Because most of the company policy restricts to keep plain password in a flat file.
use some creative scripting, you can get around such issue. Basically, the idea is simple, since .run command requires a file, you can provide the command with a named pipe, and the script will feed the name pipe with password by calling decrypting program to get the password from somewhere.
@emilwu @vador Hmm... going with encryption/decryption program may bring up another layer. I just wanted to see any ready made program available with Teradata for password encryption. However I am going to explore both the option named pipe and CLI external routine.