When editing an SSIS package there is an option EncryptSensitiveWithUserKey Where is this user key used by VS to encrypt the packages? I have two computers that I use for work. I like to copy the same user key to both computers to allow me to edit the same package on either computer. Aparently is none of the keys in my certificates store.

the UserKey is not just username, there are some factors which relates to User Key in protection, this is complete article for describing method: http://msdn.microsoft.com/library/ms995355.aspx for your case I think it is better to use EncryptSensitiveWithPassword, and then use password on every computer you want to work with the packagehttp://www.rad.pasfu.com

If I remember correctly, you can define your domain profile as a roaming profile. In such case Domain Controller will store your DPAPI configuration.

Reza, I know is not a username. I never said it was. I was trying to identify the location of the key used to encrypt the package. You do not address my question directly so I can only asume you intended to say is: - Visual Studio uses the Data Protection API provided by the OS to encrypt the package. The DPAPI created a key with the user logon password to generate a key that can only be backedup with a Password Reset Disk utility from the OS. So, no. You can not copy the key to a different PC. Visual Studio makes the SSIS package to be dependant on the specific PC is was edited when chosing EncryptSensitiveWithUserKey.

Piotr, That does not solves the problem. It would only create more problems by changing my profile to roaming. Reza, In my case using EncryptSensitiveWithPassword is not better. I don't need to add another password to the many dozens I already have. And that creates yet another problem; sharing the password to other developers. ------- The package has no sensitive data. All connections use Windows Authentication. No connection string will ever have a username and password. It is a problem having to reset all the connections everytime someone else edits the package or if i use a different computer. It is really frustrating that Visual Studio forces these options on us. I guess I will have to find another workaround. Thank you guys for the try.

To be able to open the same package on two computers using the same user name/log in you do not need to do anything special, just go ahead and open the package on the other machine and it will be editable right away.Arthur My Blog

It is editable indeed. And also all the connection strings are lost. I know you can edit the package. But I dont want to lose the connection settings every time I use a different computer.

Then your options are either 1) EncryptSensitiveWithPassword or 2) EncryptAllWithPasswordArthur My Blog

Piotr, That does not solves the problem. It would only create more problems by changing my profile to roaming. Reza, In my case using EncryptSensitiveWithPassword is not better. I don't need to add another password to the many dozens I already have. And that creates yet another problem; sharing the password to other developers. ------- The package has no sensitive data. All connections use Windows Authentication. No connection string will ever have a username and password. It is a problem having to reset all the connections everytime someone else edits the package or if i use a different computer. It is really frustrating that Visual Studio forces these options on us. I guess I will have to find another workaround. Thank you guys for the try. Ricardo, I'm wondering, if you use Windows Authentication for your connections why is the package protection level an issue for you? When you use Windows Authentication or also known as "Integrated Authentication" there is no password stored or used. My question is what happens when you select "DontSaveSensitive" option ?SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

Hi Ricardo Corral, It seems that you would like to save connection string in your package, right? Please feel free to correct me if my understanding is wrong. In that case, I suggest you can use Package Configurations to save the connection string, then edit the configuration file in Notepad, and add the password back into the connection string. For more information about it, please see: http://blogs.msdn.com/b/runeetv/archive/2009/12/22/ssis-package-using-sql-authentication-and-dontsavesensitive-as-protectionlevel.aspx Thanks, Eileen

Aileen, Thata is the more viable solution. It addresses the main issue and allows me to work on the package from multiple locations. A compromise. I could use alternative methods to keep the package secured. [edit] - In the case of Windows Authentication no password will be save in the connection string but the connection itself will, which is what I needed. Thank you,