I have a user name and a password that are used in a HTTP Post in a script task that I would like to store as an encrypted value when I check the package into our Source Control system. I would like to see if it is possible to set the ProtectionLevel to EncryptSensitivewithPassword and then mark either a variable that stores the password or a script task as sensitive. Which brings me to the question: Is there a way to mark either a variable or script task as sensitive in a SSIS package? This would satisfy my business need since the rest of the package would be searchable in a Find in Files operation.
Please note I am not willing to:
Set the ProtectionLevel to EncryptAllWithPassword. Doing this limits my ability to complete a dependency analysis by searching files for text strings.
Use any solutions that involve storing a password in either a database table or some object outside of a SSIS package. There are too many sysadmins outside of my department who can access our databases and they should not have access to the passwords.