Fixes are available
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
Symptom: On dmgr side following error is seen: SystemOut.log and Trace.log [1/28/11 20:52:12:482 CET] 00000023 LTPAServerObj W SECJ0371W: Validation of the LTPA token failed because the token expired with the following info: Token expiration Date: Fri Jan 28 20:43:37 CET 2011, current Date: Fri Jan 28 20:52:12 CET 2011. FFDC: ------Start of DE processing------ = [1/28/11 20:52:12:505 CET] , key = com.ibm.websphere.security.auth.TokenExpiredException com.ibm.ws.security.ltpa.LTPAServerObject.validate 1018 Exception = com.ibm.websphere.security.auth.TokenExpiredException Source = com.ibm.ws.security.ltpa.LTPAServerObject.validate probeid = 1018 Stack Dump = com.ibm.websphere.security.auth.TokenExpiredException: Token expiration Date: Fri Jan 28 20:43:37 CET 2011, current Date: Fri Jan 28 20:52:12 CET 2011 at com.ibm.ws.security.ltpa.AuthzPropToken.isValid(AuthzPropToken .java:201) at com.ibm.ws.security.ltpa.AuthzPropToken.<init>(AuthzPropToken.ja va:71) at com.ibm.ws.security.ltpa.AuthzPropTokenFactory.validateTokenByte s(AuthzPropTokenFactory.java:55) at com.ibm.ws.security.ltpa.LTPAServerObject.validateToken(LTPAServ erObject.java:982) at com.ibm.ws.security.ltpa.LTPAServerObject.validateToken(LTPAServ erObject.java:891) On NodeAgent side, following error is seen: ------Start of DE processing------ = [1/28/11 20:52:12:905 CET] key = java.io.FileNotFoundException com.ibm.websphere.management.filetransfer.client.FileDownloadInp utStream.read 244 Exception = java.io.FileNotFoundException Source = com.ibm.websphere.management.filetransfer.client.FileDownloadInp utStream.read probeid = 244 Stack Dump = java.io.FileNotFoundException: File download failed: java.io.IOException: Can not authorize https://abc.com/FileTransfer/transfer/download%2F cells%2Fas61627.was-v61.1%2Fnodes%2Fas61128node.2%2Fserverindex. xml65773 31504100069691.tmp?compress=true&deleteOnCompletion=true.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: Node Synchronization fails due to * * TokenExpiredException * **************************************************************** * RECOMMENDATION: * **************************************************************** When Node Synchronization request comes as a HTTP request, WebSphere validates LTPAToken cookie that came with the request to make sure the request has the right credential. In addition, WebSphere also validates PropagationTokens retrieved from DynaCache. There was program defect that allowed expired PropagationToken to stay in the DynaCache. Due to this expired PropagationToken, Node Synchronization request failed. This is intermittent issue that may happen when two different requests are handled by one thread in short time period.
Problem conclusion
With this fix, cached Subject, of which PropagationToken is expired, is evicted from DynaCache to avoid TokenExpiredException. The fix for this APAR is currently targeted for inclusion in fix pack 6.1.0.41, 7.0.0.21, and 8.0.0.1. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Turn off web inbound security attribute propagation option so that invalid Token is not retrieved and validated. The issue can be worked around in v6.1 by doing the following: From Admin console Secure administration, applications, and infrastructure (on this panel in the "Authentication section", expand "Web Security") > single sign-on (SSO) and uncheck "Web inbound security attribute propagation" The issue can be worked around in v7 by doing the following: From Admin console Click Security > Global security. Under Web security, click Single sign-on (SSO). Uncheck "Web inbound security attribute propagation option"
Comments
APAR Information
APAR number
PM34191
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-03-07
Closed date
2011-06-30
Last modified date
2011-11-28
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
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
R800 PSY
UP
Document Information
Modified date:
27 October 2021