I'm a bit confused about "Protect Sensitive With Password" ssis package
protection level. If I try to open the .dtsx in bids and hit cancel when it
prompts me for the password, the package opens just fine. Same if I try to
execute it on the server and just hit cancel when it asks for the password,
runs just fine. What is the "sensitive" material that is being protected with
the password?

In BOL it says this

Encrypts only the sensitive information in the package by using a password.
DPAPI is used for this encryption. Sensitive data is saved as a part of the
package, but that data is encrypted by using a password that the current
user supplies when the package is created or exported. To open the package
in SSIS Designer, the user must provide the package password. If the
password is not provided, the package opens without the sensitive data and
the current user must provide new values for sensitive data. If the user
tries to execute the package without providing the password, package
execution fails. For more information about passwords and command line
execution


Look at properties on Components called Sensitive. You will see it in the
XML for the Password property of the ExecutePackage task.

--


Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com



"sqlboy2000" <sqlboy2000 (AT) discussions (DOT) microsoft.com> wrote

Right and that's not correct. The package opens just fine and executes just
fine without providing the password.
That's why I'm trying to find out what microsoft considers "Sensitive".
Perhaps I'm not using anything "Sensitive".



"Allan Mitchell" wrote: