2 of 2 people found this helpful
Hi Dave - check out a wiki I wrote about an AD Sync process we automate on Tableau server. That runs tabcmd with a username & password but we too didn't want the password in plain text, so make use of another script to generate a text file with the encrypted password stored, which is subsequently then referenced http://community.tableau.com/docs/DOC-6181
Hi Donna Coles -
I know this topic is a bit old, but I'd like to see if you had run into any issues like this. It appears that the PowerShell script will not work when being scheduled from a scheduling system (ZENA, in our case) because the account that was used to encrypt the password is not the same account that is being used to attempt to decrypt the password. Any thoughts on that?
Sorry no - someone else originally developed all the stuff we use and we must have used the same account to generate the encrypted password that is then used in our daily processing.
The password only needs to be encrypted once and isn't part of the daily processing, so is there any way you can regenerate it as a one off using the same credentials?
Hi Tracy, a couple of thoughts about this. Perhaps you could generate the password using the account used by the scheduling system -- take a look at the Windows runas command. Or perhaps you can use the Windows scheduler, which allows you to specify the runas account.
I tried going this route at first and was denied by the Schedulers :/ Since I am working with a non-production environment, they eventually agreed to hand over the password. I logged into the server with that account, generated the password, and now I am able to refresh the extract through our scheduling system.