Forum Discussion
Thank you RRaghavani and Hassan.
I will surely keep this in my learning record. In our structure, the user with access to the tool and the pipeline has no 365 account, which means I cant use the above structure.
Customer care team gave me the solution to Decrypt at the end of calling parameter. Parameter.DecryptValue. This way I can store the details in password format and retrieve it as required for the connection string.
Do you guys have any suggestions on this approach ?
A while back, I provided a possible solution, see Encrypt/Decrypt Base64 string in TestComplete | SmartBear Community - I didn't have dotNet extension installed or the appropriate license, so I was unable to provide the full code. However, the snippet of code was able to help. You could implement something similar.
If the automation scripts is being used by a team, would it not be best to have a dedicated user account to access the database?