A set of utilities that allow to autonomously build a Visual Studio SSIS project (dtproj) into a deployment package (ispac), and deploy the package to an SSIS catalog
Apache License 2.0
52
stars
39
forks
source link
Project level sensitive passwords exposed during build #36
How do I make sure that the passwords that have been marked as sensitive in the ETL during development at project level, are not exposed during build?
When we build a SSIS package through "SSISBuild" in PowerShell through it's PowerShell module New-SsisDeploymentPackage, we see that the project level sensitive passwords are exposed into plain text during the build, thereby rendering the password secrecy useless.
The ETL is protected with EncryptSensitiveWithPassword.
How do I make sure that the passwords that have been marked as sensitive in the ETL during development at project level, are not exposed during build?
When we build a SSIS package through "SSISBuild" in PowerShell through it's PowerShell module New-SsisDeploymentPackage, we see that the project level sensitive passwords are exposed into plain text during the build, thereby rendering the password secrecy useless. The ETL is protected with EncryptSensitiveWithPassword.
Comment please!! @rtumaykin @fmms