PM21308; Messaging engine to messaging engine link fails with SECJ9314E

Download Description

PM21308 resolves the following problem:

ERROR DESCRIPTION:
The following exception is recorded in the SystemOut.log, causing a messaging engine to messaging engine communications link to fail, within a service integration bus.
CWSIT0034E and CWSIT0110E errors are also logged.
[8/13/10 17:21:54:879 CST] 0000003a Krb5LoginModu E
SECJ9314E: An unexpected exception occurred when trying to run
acceptSecContext()
method : GSSException: org.ietf.jgss.GSSException, major code:
10, minor code: 0
ext() method : GSSException: org.ietf.jgss.GSSException, major
code: 10, minor
code: 0
major string: Defective token
minor string: Bad token tag: -27
at com.ibm.security.jgss.i18n.I18NException.throwGSSException
(I18NException.java:1)
at com.ibm.security.jgss.TokenHeader.b(TokenHeader.java:63)
at com.ibm.security.jgss.TokenHeader.b(TokenHeader.java:49)

at com.ibm.security.jgss.GSSContextImpl.acceptSecContext
(GSSContextImpl.java:513)
at com.ibm.security.jgss.GSSContextImpl.acceptSecContext
(GSSContextImpl.java:427)
...

LOCAL FIX:

PROBLEM SUMMARY

USERS AFFECTED:
Users of the default messaging provider for IBM WebSphere Application Server Version 7,
with multiple messaging engines in secure service integration bus

PROBLEM DESCRIPTION:
CWSIT0034E and CWSIT0110E before SECJ9314E when using secure messaging

RECOMMENDATION:
None

The application server's security layer might not be able to accurately determine the type of the security token which the messaging engines use to authenticate with each other. When authentication fails due to incorrect detection of the token type, the messaging engines within the bus are unable to communicate with each other.

PROBLEM CONCLUSION:
The fix for this APAR updates the service integration bus code to explicitly state the security token type when authenticating a remote messaging engine within the bus. This avoids the need for the auto-detection code to run, which in turn prevents the security layer from misidentifying the token type being used.

The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.15. Please refer to the Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?uid=swg27004980