Connecting to external SQL server - secure string

Question

Hi Experts, 
 I'm new to using One Identity. I'm using v6.1.4 
 I need to connect to an external SQL database to read some information from their tables. An account login exists for the one identity service account in the external SQL database already with full read rights. 
 I would like to find out what is the most "secure" way to define the connection string? I was thinking of using the data importer but I don't want to hardcode the connection string in the generated script. I thought of using configuration paramater to store the connection string but then too it is in plain text. 
 What is the recommended approach here, both to secure the connection string as well as the actual connection itself? (SSL?) 
 Thanks 
 Kin

Barry Jackson · Accepted Answer

Hi, 
 
Please take a look at this post: www.quest.com/.../connectionstring-for-sql-based-custom-target-system 
 
Also, in the case of data importer there is a 'free' parameter called 'Options' .... set this to hidden and encrypted in the process step ...... pass into it the value of your encrypted config parm ..... and in your script set the connection string variable to dfImport.Options instead of the hard coded connection string. 
 
Of course you have to have enabled encryption on the database beforehand. 
 
HTH, Barry.

zippa68 · Answer

Try to use Windows Authentication for JobServer service account and Trusted_Connection=Yes parameter in connection string.

Connecting to external SQL server - secure string

Top Replies