Post reply

Running and SSIS package in VS using senstive parameters and ProtectionLevel = DontSaveSensitive

  • January 16, 2019 at 4:34 am

    #382591

    I have a package which I have set up with a set of package parameters that are configured from environment variables on a deployed server

    A couple of the parameters contain passwords.  So I have set these package parameters to be "Sensitive" parameters.  The related server SSIS Environment Variables that contain the passwords on the Server and which are configured to populate these variables are also set as "sensitive".

    Since we do not want the package to permanently contain sensitive data, the package protection level is set to "Do not save sensitive data".   

    When I deploy this package to the server Integration Services Catalog and run it, the package configures it's sensitive parameters from the sensitive environment variables and runs fine.

    All good so far....

    However if when I am designing the package inside Visual Studio and I populate the sensitive package parameters in the Visual Studio SSIS designer:
      
    ...and run the package; at run-time the package seems to lose the values; although when stopping the package and looking at the parameters tab in Visual Studio the populated parameter is still there with the value I stored.

    The only way I can see around this is to temporarily set the package to encrypt with a user key or encrypt with a password when running and testing the package locally in Visual Studio. 

    How do others run packages inside Visual Studio with Sensitive Variables or Parameters?

  • January 18, 2019 at 3:53 pm

    #2019430

    You may have better luck posting this under Data Warehousing...

    But that's a good question, i just tested it and getting the same result. You could change the parm to Not sensitive while in development but that does leave the pw exposed on the dev machine and in source control for any commits. 
    We use dont save sensitive for 2008 packages but those just prompt for a pw then it seems to stick as long as the project is open in VS. 

    Another option to try is to setup local configs with the pw and see if that works. From the Parms screen click the "Add Parameters to Configuration" button and enter the sensitive data there and see what it does.

  • July 9, 2021 at 9:54 am

    #3906018

    TangoVictor wrote:

    Another option to try is to setup local configs with the pw and see if that works. From the Parms screen click the "Add Parameters to Configuration" button and enter the sensitive data there and see what it does.

    I know that this is an old post, but I'm working on something similar right now, so I tried this. Unfortunately (assuming everything is set as DontSaveSensitive) it does not help.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply