|
Problem IC63032
|
Status: Closed |
"PERSIST SECURITY INFO=TRUE" WITH OLEDB CONNECTION IS ENCRYPTING THE PASSWORD IN THE CONNECTION STRING. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Persist Security Info if enabled allows applications to view
sensitive information that was passed in the connection string
like the password. The password is encrypted. This APAR will
ensure the connection string password is not encrypted |
| Problem Summary: |
"PERSIST SECURITY INFO=TRUE" WITH OLEDB CONNECTION IS ENCRYPTING
THE PASSWORD IN THE CONNECTION STRING. |
| Local Fix: |
A possible workaround is to use a string variable to store the
OLE DB connection string and pass this string variable while
opening OLE DB connection and use the string variable for
further processing in application code instead of using the
OLE DB connection object string property. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 LUW v9.7 Fixpak 1 |
| Workaround |
A possible workaround is to use a string variable to store the
OLE DB connection string and pass this string variable while
opening OLE DB connection and use the string variable for
further processing in application code instead of using the
OLE DB connection object string property. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.09.2009
29.12.2009
29.12.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
