I have read several posts and articles regarding connection manager
password security in SSIS and how to go about this using configuration
files, changing ProtectionLevel and supplying package passwords, but I
believe my issue is different:

I've designed a package using a configuration file. This all works fine
using Windows authentication. I then change package ProtectionLevel to
"EncryptAllWithPassword", and change the OLEDB connection to SQL Server
authentication, type in the username and password, check "Save my
password" and then OK. Without going a step further I go and recheck
the password that I've just typed, and it is gone!

Assistance greatly appreciated, I'm losing my nut!

Have a look at
http://www.nigelrivett.net/DTS/SSISC...ationFile.html

You can edit the config file to add the password.

www.nigelrivett.net


*** Sent via Developersdex http://www.developersdex.com ***

Thanks, that works, but now I have an unencrypted SQL password lying on
the user's machine. Why is the password not saved (& encrypted) to the
config file with "EncryptAllWithPassword" or
"EncryptSensitiveWithPassword" as expected?

I just created a package - it just copies the contents iof a table to
itself.
Connected as sql server login.

set package properties to encrypt sensitive with password
set the package password to hello
saved the package as g:\text.dtsx
ran using
master..xp_cmdshell 'dtexec /F "G:\text.dtsx" /De "hello"'
The package ran happily, copied the data and I verified using the
profiler that it was connecting as my sql server login.




www.nigelrivett.net


*** Sent via Developersdex http://www.developersdex.com ***