|
Problem IC84130
|
Status: Closed |
WHEN USING TRUSTED CONTEXT, SECADM AND DBADM AUTHORITIES WERE NOT TAKEN INTO ACCOUNT AT DATABASE CONNECTION TIME |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Roles inherited through trusted contexts were not taken into
account when checking for DBADM/SECADM authority at database
connection time. DBADM and SECADM have implicit connect
privilege, and because they were not considered at database
connection time, users that inherit DBADM/SECADM authorities
through trusted context might not be able to connect to the
database. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 LUW Version 10.1 fixpack 1 *
**************************************************************** |
| Local Fix: |
grant direct CONNECT privilege to the trusted context role |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem is first fixed in DB2 LUW Version 10.1 fixpack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.06.2012
22.11.2012
22.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
