|
Problem IT25879
|
Status: Closed |
GATEWAY CONCENTRATOR CAN CAUSE JDBC DES CLIENTS TO FAIL TO AUTHENTICATE WHEN JDBC AES CLIENTS ARE ALSO BEING USED.
|
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
JDBC applications that connect through a DB2 Connect gateway to
a DB2 for z/OS server can fail with authentication failures when
the DB2 Connect gateway is using connection concentrator
(MAX_CONNECTIONS > MAX_AGENTS) and if the JDBC applications are
using a mix of DES and AES connection requests. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 10.5 Fix Pack 11 or higher *
**************************************************************** |
| Local Fix: |
a) Disable Connection concentrator on the gateway
or
b) Use a direct connection from JDBC to DB2 for z/OS without a
gateway. Connection concentrator can still be enabled at the
JDBC driver using the enableConnectionConcentrator property. |
| Solution |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner :
follow-up : IT25880 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.08.2018
25.02.2020
25.02.2020 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
