|
Problem IC95654
|
Status: Geschlossen |
SQL30082N RC=24 ERROR MAY OCCUR USING PAM_KRB5.SO WITH TRANSPARENT LDAP |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
An application may fail with SQL30082N RC=24 when Transparent
LDAP is configured with pam_krb5.so.
In the db2diag.log an error such as the following may be seen:
2013-02-28-16.26.07.671971-300 I26210374A441 LEVEL: Error
PID : 550 TID : 2 PROC :
db2ckpwd 0
INSTANCE: xxxxxxxx NODE : 000
EDUID : 2 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, oper system services, sqloPamAuthentication,
probe:6565
MESSAGE : Failure setting user credentials
DATA #1 : Hexdump, 8 bytes
0xFFFFFFFF613F7468 : 6E79 6374 7263 6462
xxxxxx
This error occurs because the pam_krb5.so module conflicts with
the pam_setcred API used by DB2 to support pam_tally.
DB2 only officially supports PAM configurations with pam_ldap.so
and pam_unix_auth.so when using Transparent LDAP. However, this
APAR will resolve the error described above when using the
unsupported pam_krb5.so module with Transparent LDAP. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* Unix/Linux platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 10.1 Fixpack 4 *
**************************************************************** |
| Local-Fix: |
As DB2 only officially supports pam_ldap.so and
pam_unix_auth.so, it is recommended to avoid using pam_krb5.so
in Transparent LDAP configurations. |
| verfügbare FixPacks: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Lösung |
First fixed in DB2 10.1 Fixpack 4 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 02.09.2013
09.06.2014
09.06.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.4
|
 |
