|
Problem IT19549
|
Status: Closed |
SECURITY MECHANISM NOT SUPPORTED EXCEPTION WHEN AUTHENTICATION=CLIENT AND PASSWORD AND USER ARE PROVIDED. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
When there are following setting on the remote server:
Database manager authentication (AUTHENTICATION) = CLIENT
Alternate authentication (ALTERNATE_AUTH_ENC) =
NOT_SPECIFIED
Cataloging allowed without authority (CATALOG_NOAUTH) = YES
Trust all clients (TRUST_ALLCLNTS) = YES
Trusted client authentication (TRUST_CLNTAUTH) = SERVER
Bypass federated authentication (FED_NOAUTH) = NO
in that case when the user and password is provided then
authentication should take place on the server side.
When no credentials are provided then client authentication
should take place.
However instead the following exceptions are raised:
com.ibm.db2.jcc.am.SqlWarning: Origination unknown:
[10228][11541][4.18.60] Security exceptions occurred while
loading driver. ERRORCODE=4223, SQLSTATE=null
and:
[jcc][t4][201][11237][4.18.60] Connection authorization failure
occurred. Reason: Security mechanism not supported.
ERRORCODE=-4214, SQLSTATE=28000 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 10.5 Fix Pack 9 or higher *
**************************************************************** |
| Local Fix: |
|
| Solution |
First fixed in Db2 10.5 Fix Pack 9 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.03.2017
29.09.2017
29.09.2017 |
| Problem solved at the following versions (IBM BugInfos) |
9.0.
|
| Problem solved according to the fixlist(s) of the following version(s) |
