|
Problem IC75514
|
Status: Closed |
DB2 DOES NOT CALL PAM_SETCRED() TO RESET THE COUNTER AFTER A SUCCESSFUL LOGIN ON LINUX |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Linux can be configured to lock out a user after a set number of
unsuccessful logins using the pam_tally modules. DB2 supports
this but the counter is never decremented. This means that the
user will get locked out even though all the connections were
successful. DB2 needs to be modified to call pam_setcred() after
a successful connection to reset the counter. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 Users on Linux *
****************************************************************
* PROBLEM DESCRIPTION: *
* DB2 Users on Linux can have their IDs locked out even though *
* there have been no failed connection attempts. *
* *
* This is because Linux can be configured to lock out a user *
* after a set number of unsuccessful logins using the *
* pam_tally modules. DB2 supports this but the counter is *
* never decremented. This means that the user will get locked *
* out even though all the connections were successful. DB2 *
* needs to be modified to call pam_setcred() after a *
* successful connection to reset the counter. *
****************************************************************
* RECOMMENDATION: *
* Updrate to DB2 v9.7 FP5 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem fixed in DB2 v9.7 FP5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.04.2011
02.01.2012
02.01.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
