Fixes are available
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
In WSRR following instructions from the topic Configuring outbound identity mapping to a different target realm http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/index.jsp?topic=/ com.ibm.websphere.nd.multiplatform.doc/ae/tsec_outbdiffrealm.htm l, The second and third bullet points of the above article - call an EJB in a different cell, using a different user registry. WSRR detects that a user has specified a realm in the configuration and attempts to use "the Java Authentication and Authorization Service (JAAS) WSLogin application login configuration to create a basic authentication Subject that contains the credentials of the new target realm." Transaction coordination authorization on both servers was disabled. The following CORBA error is thrown: [11/14/13 14:25:51:364 GMT] 00000130 CSIClientRI 3 The following exception was received from the server: >> SERVER (id=4773e3aa, host=myHostName.myHost.myDomain.com) TRACE START: >> org.omg.CORBA.NO_PERMISSION: Validation of LTPA token failed due to invalid keys or token type. vmcid: 0x49424000 minor code: 300 completed: No >> at com.ibm.ISecurityLocalObjectBaseL13Impl.PrincipalAuthFailReason. map_auth_fail_to_minor_code(PrincipalAuthFailReason.java:88) >> at com.ibm.ISecurityLocalObjectBaseL13Impl.CSIServerRIBase.authenti cateSecurityTokens(CSIServerRIBase.java:4571) >> at com.ibm.ISecurityLocalObjectBaseL13Impl.CSIServerRI.receive_requ est(CSIServerRI.java:585) >> at com.ibm.rmi.pi.InterceptorManager.invokeInterceptor(InterceptorM anager.java:624) >> at com.ibm.rmi.pi.InterceptorManager.iterateServerInterceptors(Inte rceptorManager.java:528) >> at com.ibm.rmi.pi.InterceptorManager.iterateReceiveRequest(Intercep torManager.java:770) >> at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDe legate.java:667) >> at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:5 25) >> at com.ibm.rmi.iiop.ORB.process(ORB.java:576) >> at com.ibm.CORBA.iiop.ORB.process(ORB.java:1578) >> at com.ibm.rmi.iiop.Connection.doRequestWork(Connection.java:3076) >> at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2946) >> at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:64) >> at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118) >> at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1862) >> SERVER (id=4773e3aa, host=myHostName.myHost.myDomain.com) TRACE END.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0 and V8.5 * **************************************************************** * PROBLEM DESCRIPTION: During cross-cell or cross-realm RMI * * communications a subject could be * * incorrectly be sent to a foreign * * realm. * **************************************************************** * RECOMMENDATION: * **************************************************************** When the Application Server attempts to communicate with a target server that has a different realm a subject should only be sent if that target host is considered trusted. Under some circumstances a subject could be sent. This results in failures on the target side to decrypt LtpaTokens.
Problem conclusion
Code was changed to not send a subject to the target if target is not considered trusted. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.3 and 8.0.0.10 Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI07671
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-12-09
Closed date
2014-04-15
Last modified date
2014-07-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
27 April 2022