Archives of the TeradataForum

Message Posted: Fri, 27 Oct 2006 @ 08:20:42 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

I assume you are not using any single sign on technologies, otherwise this would not be a problem.

One approach I have used on Unix is to put the bteq logon script in a file which is readable only by the owner (and system administrator).

Thus I might have a file "logon.txt" that contains the following:

     .logon uid,pwd;

The unix permissions would be 600 or in ls -l

     -rw-------   ... logon.txt
     400 or -r-------- also can work.

For this to work, the bteq jobs must run as the same userID as the owner of the file.

To use this file in bteq, you use the .run command as in:

     .run file=logon.txt

You could probably do something similar on windows using windows security attributes.

Obviously this does not "mask" the password which is still in clear text but it restricts access to the password based upon operating system access controls.

I hope this helps.

Glenn Mc

	<Prev	Next>		<<First	<Prev	Next>	Last>>