How to secure the password when calling SACmd from a tidal job?

Question

I'm attempting to use the SACmd command line from a Tidal job.   I have the job configured and is working correctly. 
My quesion, is how do i secure the password?  Currently, it is in the clear in the job parameters.   Is there a system variable i can set, which then isn't displayed?

Answer 1

This has been answered by others in older posts (which was where I got some tips from) and I believe the reference guide or the command line PDF guides may have this info. Essentially this involves using the -persist command option from the server (where sacmd is installed - usually the master)  which then saves the particular credentials within users local home on the server so that you don't have to add password in the tidal job you create after that.
1. Prior to running sacmd on the server as a job in TES61, you will need to verify that it can run via command line outside of TES GUI.
[serveradmin@masterserv bin]$ pwd
/opt/tidal/TIDAL/TESCmdline/bin
[serveradmin@masterserv bin]$ ./sacmd.sh
TES SA Command Console (Version 6.1.0.267).
JRE Version : 1.7.0_25
Style       : table
DSP URL     : https://server.company.com/api/TesDevCM
Username    : domain\interactiveuser
Password    :
SACmd>quit
2. So that you don’t have to append login credentials required by TES 61 in your command parameters in the job definition, you will have to run the command below.  This uses the –persist parm, which stores the interactive user credential in the users local home one time.  You will need to run this again for another user and for when passwords change.
[serveradmin@masterserv bin]$ ./sacmd.sh -cmdspurl https://server.company.com/api/TesDevCM1 -user 'domain\serveradmin' -pass
'********' -persist
TES SA Command Console (Version 6.1.0.267).
JRE Version : 1.7.0_25
Style       : table
DSP URL     : https://server.company.com/api/TesDevCM1
User        : domain\interactiveuser
Connection info saved successfully
[serveradmin@masterserv bin]$ ./sacmd.sh -help
NOTE: the User has to be an interactive user in TIDAL in order for this to work.  In this particular case the Tidal job will use masterserv as the agent, and UNIX\serveradmin as the runtime user (since that is the user that owns the executable binaries).  But it is actually going to use the domain\interactiveuserTIDAL interactive user security to run sacmd.  If domain\interactiveuser doesn’t have security policy rights to perform something in sacmd, command will fail.
This will save your credentials in this location:
[serveradmin@masterserv tescmd]$ pwd
/home/serveradmin/tescmd
[serveradmin@masterserv tescmd]$ ls -lat
total 12
-rw-rw-r-- 1 serveradmin serveradmin   76 Aug 23 14:13 .connection
drwxrwxr-x 2 serveradmin serveradmin 4096 Aug 23 14:12 .
drwx------ 4 serveradmin serveradmin 4096 Aug 23 14:12 ..
[serveradmin@masterserv tescmd]$ vi .connection
https://server.company.com/api/TesDevCM
Y8Rod7qhMMtHKx0W+Dx+F7FsdfsslQTr
That's it, so when you run your sacmd , you don't have to pass any credentials from the command parameter.