Hello,

I wanted to add something that works very well for us regarding secured, or I would say prohibited, access to logins and passwords, encrypt keys, etc.

Another way of doing things is to put you connection credentials or encrypt keys in a file that is stored in a limited access location, for example only to system administrators. Then when these parameters are necessary for your customers you can simply tell them to include the file in their script, but this is only completely secured if the information are not shown in the log files. To avoid that you enclose your parameter file with the statements.

For example you can :

1. create a connection file "mysql.sas" to access a MySQL Database :

/* ======================================== */
options nonotes nosource nosource2 ;

%let my_server=myServerName ;
%let my_port=9999 ;
%let my_database=myDB ;
%let my_user=myUser ;
%let my_password=myPwd ;

libname my1139 mysql server=&my_server port=&my_port database=&my_database user=&my_user password=&my_password ;
options notes source source2 ;
/* ======================================== */

2. Save this file in a secure place that is only accessible the system admins only

3. In the script that need to access the Database you just add the following statement :
include (path-to-my-secure-connections/mysql.sas) /* this is for a UNIX environment */

Best Regards,
Vincent M.