DB2 - Problem description
| Problem IC73750 | Status: Closed |
CONNECTIONS WITH KERBEROS AUTHENTICATION ARE IMPOSSIBLE FROM A DB2 CLIENT THAT DOESN'T USE A DB2 DATABASE CATALOGS. | |
| product: | |
DB2 CONNECT / DB2CONNCT / 950 - DB2 | |
| Problem description: | |
If you are trying to connect to a DB2 server, using the Kerberos
authentication, from a DB2 Client that doesn't use DB2 database
catalogs, you will receive an error message because CLI doesn't
have a ini/cfg keyword for passing the principal name.
The following test demonstrates the problem :
With the following db2cli.ini :
[ODBCKB]
Database=DB2KB
Trusted_Connection=Yes
Protocol=TCPIP
Hostname=LOCALHOST
Authentication=KERBEROS
KRBPlugin=IBMkrb5
;principal=service/host@REALM
Port=port1
AutoCommit=0
The following connection fails with this error : SQL30082N
Security processing failed with reason "36" ("UNEXPECTED CLIENT
ERROR").
more test.cli :
opt callerror on
opt echo on
sqlallocenv 1
sqlallocconnect 1 1
sqldriverconnect 1 0 "DSN=ODBCKB" -3 255 SQL_DRIVER_NOPROMPT
quit
db2cli < test.cli
...
> sqldriverconnect 1 0 "DSN=ODBCKB" -3 255 SQL_DRIVER_NOPROMPT
SQLDriverConnect: rc = -1 (SQL_ERROR)
SQLError: rc = 0 (SQL_SUCCESS)
SQLError: SQLState : 08001
fNativeError : -30082
szErrorMsg : [IBM][CLI Driver] SQL30082N Security
processing failed with reason "36" ("UNEXPECTED CLIENT ERROR").
SQLSTATE=08001
... | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Kerberos Authentication via a DB2 Gateway * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 9.5 FP8 * **************************************************************** | |
| Local Fix: | |
| available fix packs: | |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows | |
| Solution | |
Problem was first fixed in DB2 9.5 FP8 | |
| Workaround | |
not known / see Local fix | |
| BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC73754 follow-up : | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 10.01.2011 27.06.2011 27.06.2011 |
| Problem solved at the following versions (IBM BugInfos) | |
9.5.FP8 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.5.0.8 |
|