Search

Variable.GetSensitiveValue doesn't work with DontSaveSensitive ProtectionLevel by Philipp Avanade

Active

5
0
Sign in
to vote
Type: Bug
ID: 766500
Opened: 10/7/2012 8:09:19 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
In SSIS 2012 when using sensitive project parameters, their value cannot be retrieved using Dts.Variables["VariableName"].GetSenstitiveValue() when the package/project ProtectionLevel is set to DontSaveSenstitive.
Details (expand)

Product Language

English

Version

SQL Server 2012 - Enterprise Edition

Category

Integration Services (DTS)

Operating System

Windows Server 2008 Standard

Operating System Language

US English

Steps to Reproduce

1. Create new SSIS 2012 project in project deployment mode with ProtectionLevel EncryptSensitiveWithUserKey.
2. Add project parameter "t" as string and senstivie. Enter a sensitive string.
3. Add a script task and add $Project:t to ReadOnlyVariables
4. Add the following code to Main(): MessageBox.Show(Dts.Variables["$Project::t"].GetSensitiveValue().ToString());
6. Execute package.
-> MessageBox should show parameter value.
7. Now change project and package ProtectionLevel to DontSaveSensitive
8. Execute package.
-> MessageBox shows empty string.

Actual Results

Empty string is shown when accessing sensitive parameter using GetSensitiveValue method.

Expected Results

Expect to see value specified in parameter.

Platform

X64

Virtualization

Hyper-V (On-Premise)
File Attachments
0 attachments
Sign in to post a comment.
Sign in to post a workaround.