SSIS2008 无法解密受保护的xml节点 解决方法
2011-08-24 11:11
323 查看
设置包属性 ProtectionLevel ,设置参照下文
Members
Remarks
When using the value DontSaveSensitive, if sensitive information is contained in a package, this sensitive information is not saved. This is the default value.
For all values, sensitive information is defined as:
The password portion of a connection string. However, if you choose an option that encrypts everything, the entire connection string will be considered sensitive.
The task-generated XML nodes that are tagged with the Sensitive attribute.
Any variable marked with the Sensitive attribute.
If you have sensitive information in a configuration file, you should save it to Microsoft SQL Server, or use an access control list (ACL) to secure the location or folder. For more information, see Creating Package Configurations.
For more information on setting package protection levels, see Setting the Protection Level of Packages.
Encryption is done by using two methods. The Microsoft Data Protection API (DPAPI), which is part of the Cryptography API (Crypto API), is used for the protection levels of EncryptAllWithUserKey and EncryptSensitiveWithUserKey. The TripleDES class is used for the protection levels of EncryptAllWithPassword and EncryptSensitiveWithPassword.
For more information, see TripleDES Class in the .NET Framework Class Library.
Members
Member name | Description |
DontSaveSensitive | Sensitive information is not saved in the package. The sensitive information is removed and replaced with blanks. |
EncryptAllWithPassword | Encrypts the entire package by using a password. |
EncryptAllWithUserKey | Encrypts the entire package by using keys based on the user profile. Only the same user using the same profile can load the package. |
EncryptSensitiveWithPassword | Encrypts only sensitive information contained in the package by using a password. DPAPI is used for this encryption. |
EncryptSensitiveWithUserKey | Encrypts the entire package by using keys based on the current user. Only the same user using the same profile can load the package. If a different user opens the package, the sensitive information is replaced with blanks. DPAPI is used for this encryption. |
ServerStorage | Encrypts the package within a SQL Servermsdb database. This option is supported only when a package is saved to SQL Server. It is not supported when a package is saved to the File System. The access control of who can decrypt the package is controlled by SQL Server database roles. For more information, see Database-Level Roles and sysssispackages (Transact-SQL). |
When using the value DontSaveSensitive, if sensitive information is contained in a package, this sensitive information is not saved. This is the default value.
For all values, sensitive information is defined as:
The password portion of a connection string. However, if you choose an option that encrypts everything, the entire connection string will be considered sensitive.
The task-generated XML nodes that are tagged with the Sensitive attribute.
Any variable marked with the Sensitive attribute.
If you have sensitive information in a configuration file, you should save it to Microsoft SQL Server, or use an access control list (ACL) to secure the location or folder. For more information, see Creating Package Configurations.
For more information on setting package protection levels, see Setting the Protection Level of Packages.
Encryption is done by using two methods. The Microsoft Data Protection API (DPAPI), which is part of the Cryptography API (Crypto API), is used for the protection levels of EncryptAllWithUserKey and EncryptSensitiveWithUserKey. The TripleDES class is used for the protection levels of EncryptAllWithPassword and EncryptSensitiveWithPassword.
For more information, see TripleDES Class in the .NET Framework Class Library.
相关文章推荐
- SQL SERVER MaintanencePlan 失败 无法解密受保护的 XML 节点“DTS:Password”,错误为 0x8009000B解决
- 《BI项目笔记》无法解密受保护的 XML 节点“DTS:Password” 解决办法
- 《BI项目笔记》无法解密受保护的 XML 节点“DTS:Password” 解决办法
- 无法解密受保护的XML节点“DTS:Password”
- 无法解密受保护的XML节点“DTS:Password”
- sql 2005数据库升级到2008后,无法打开数据库关系图的正确解决方法
- 关于“无法从传输连接中读取数据: 尝试读取或写入受保护的内存。这通常指示其他内存已损坏。”错误的解决方法之一
- 无法卸载VISTUAL STUDIO 2008 的解决方法
- VS2008提示无法读取项目文件 无法识别工具版本4.0 的解决方法
- 解决sql 2008 事务日志收缩与截断无法减小日志物理文件的方法
- tomcat启动提示server.xml的context节点中不支持source属性警告的解决方法
- XML节点位置不能是变量解决方法
- 总结:Windows Server 2003/2008远程桌面无法连接的解决方法
- windows server 2008/2012 无法安装AD域解决方法记录
- SQL SERVER 2008 无法启动T-SQL调试的解决方法
- sql server 2008附加不上数据库,报物理位置无法打开错误的解决方法
- eclipse:xml-apis jar包冲突导致的getTextContent()方法无法找到解决
- 解决NSXmlParser无法解析非utf-8编码的XML问题的方法
- tomcat启动提示server.xml的context节点中不支持source属性警告的解决方法
- Visual Studio 2008无法创建智能设备项目的解决方法