DB2 FOR LUW / DB2FORLUW / B50 - DB2

For SSL connections only, authentication cache does not perform
User or Group lookup and thus does not cache user and group
information.

This will not cause authentication errors for SSL Connections,
but the potential performance gain of the Authentication Cache
is not realized.

****************************************************************
* USERS AFFECTED:                                              *
* All DB2 systems on all Linux, Unix and Windows platforms at  *
* service levels Version 11.5 GA to 11.5.6                     *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* The complete fix for this problem first appears in DB2       *
* Version 11.5.7 and all the subsequent Fix Packs.             *
****************************************************************

****************************************************************
* USERS AFFECTED:                                              *
* All DB2 systems on all Linux, Unix and Windows platforms at  *
* service levels Version 11.5 GA to 11.5.6                     *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* The complete fix for this problem first appears in DB2       *
* Version 11.5.7 and all the subsequent Fix Packs.             *
****************************************************************

Due to the way SSL connections were handled in prior releases of
Db2, the authentication code was not able to access structures
necessary to authenticate users against the cache.

This issue was resolved in Db2 11.5.7. After upgrading, use
"db2pd -authenticationcache" to verify that users are being
cached:

db2pd -authenticationcache -db

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

19.05.2021
23.11.2021
23.11.2021