suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT37891 Status: Closed

WHEN TRUSTED CONTEXT IS DROPPED, SETSESSIONUSER PRIVILEGES ARE ALSO
DELETED

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
When you drop trusted context, it will remove all rows in
syscat.surrogateauthids where trustedid is the "context name"
created. It doesn't check the trustedidtype.
It means that if you give grant to a user with the same context
name (setsessionuser privilege has nothing to do with a trusted
context), when you drop the TC, all rows are removed, and only
should be the rows with trustedidtype='C'.

ie.-e:

db2  "CREATE TRUSTED CONTEXT TEST1 BASED UPON CONNECTION USING
SYSTEM AUTHID TEST1 ENABLE ATTRIBUTES (ADDRESS 'X.XX.XXXX.XXXX')
WITH USE FOR PUBLIC WITHOUT AUTHENTICATION"
db2 grant setsessionuser on user XXXX to user TEST1
db2 "select TRUSTEDIDTYPE, SURROGATEAUTHID from
syscat.surrogateauthids where trustedid='TEST1'"
TRUSTEDIDTYPE SURROGATEAUTHID

-------------
----------------------------------------------------------------
----------------------------------------------------------------
C             PUBLIC

U             XXXX



db2 drop trusted context TEST1

db2 "select TRUSTEDIDTYPE, SURROGATEAUTHID from
syscat.surrogateauthids where trustedid='TEST1'"
TRUSTEDIDTYPE SURROGATEAUTHID

-------------
----------------------------------------------------------------
----------------------------------------------------------------

  0 record(s) selected.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to 11.1.4.7                                          *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to 11.1.4.7                                          *
****************************************************************
Comment
Upgrade to 11.1.4.7
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.08.2021
17.04.2022
17.04.2022
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)