PK73552: PROBLEMS WITH NODE SYNCHRONIZATION AFTER LTPA KEYS ARE GENERATED VIA SCRIPT.

Fixes are available

APAR status

Closed as program error.

Error description

Problems with node synchronization after LTPA keys are generated
via script.

Local fix

Disabling the dynamic ssl update function.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application          *
*                  Server's $AdminTask                         *
*                  generateKeyForKeySetGroup command           *
****************************************************************
* PROBLEM DESCRIPTION: When generating LTPA keys manually      *
*                      with the wsadmin command using the      *
*                      $AdminTask generateKeyForKeySetGroup    *
*                      command, customers may experience       *
*                      synchronization errors when             *
*                      attempting to synchronize a             *
*                      running cell with Dynamic SSL Update    *
*                      enabled.                                *
*                      The failing sequence of commands look   *
*                      similar to the following:               *
*                                                              *
*                      wsadmin>$AdminTask                      *
*                      generateKeyForKeySetGroup               *
*                      {-keySetGroupName CellLTPAKeySetGroup}  *
*                      wsadmin>$AdminConfig save               *
*                      wsadmin>set sync [$AdminControl         *
*                      completeObjectName type=NodeSync,*]     *
*                      wsadmin>$AdminControl invoke $sync sync *
*                                                              *
*                      executing these commands may result     *
*                      in a "false" result being returned      *
*                      (meaning the cell failed to             *
*                      synchronize), or this error:            *
*                                                              *
*                      WASX7017E: Exception received while     *
*                      running file "xxxxx"; exception         *
*                      information:                            *
*                      javax.management.JMRuntimeException:    *
*                      A                                       *
*                      DMN0022E: Access is denied for the      *
*                      sync operation on NodeSync MBean        *
*                      because of insufficient or empty        *
*                      credentials.                            *
*                                                              *
*                      FFDC logs may show something similar    *
*                      to the following:                       *
*                                                              *
*                      Stack Dump =                            *
*                      com.ibm.websphere.security.auth.WSLogin *
*                      FailedException: Validation of LTPA     *
*                      token failed due to invalid keys or     *
*                      token type.                             *
*                       at                                     *
*                      com.ibm.ws.security.ltpa.LTPAServerObje *
*                      ct.validateToken(LTPAServerObject.java: *
*                      942)                                    *
*                       at                                     *
*                      com.ibm.ws.security.token.WSCredentialT *
*                      okenMapper.validateLTPAToken(WSCredenti *
*                      alTokenMapper.java:1300)                *
*                       at                                     *
*                      com.ibm.ws.security.auth.ContextManager *
*                      Impl.getOpaqueTokenFromCacheOrOriginati *
*                      ngServer(ContextManagerImpl.java:1324)  *
*                       at                                     *
*                      com.ibm.ws.security.auth.ContextManager *
*                      Impl.login(ContextManagerImpl.java:2796 *
*                      )                                       *
*                       at                                     *
*                      com.ibm.ws.security.auth.ContextManager *
*                      Impl.login(ContextManagerImpl.java:2735 *
*                      )                                       *
*                       at                                     *
*                      com.ibm.ws.security.web.WebAuthenticato *
*                      r.validate(WebAuthenticator.java:1627)  *
*                       at                                     *
*                      com.ibm.ws.security.web.WebAuthenticato *
*                      r.validateCookie(WebAuthenticator.java: *
*                      598)                                    *
*                       at                                     *
*                      com.ibm.ws.security.web.WebAuthenticato *
*                      r.handleSSO(WebAuthenticator.java:519)  *
*                       at                                     *
*                      com.ibm.ws.security.web.WebAuthenticato *
*                      r.authenticate(WebAuthenticator.java:14 *
*                      22)                                     *
*                       at                                     *
*                      com.ibm.ws.security.web.WebCollaborator *
*                      .authorize(WebCollaborator.java:657)    *
*                       at                                     *
*                      com.ibm.ws.security.web.EJSWebCollabora *
*                      tor.preInvoke(EJSWebCollaborator.java:3 *
*                      18)                                     *
*                                                              *
*                                                              *
*                                                              *
*                                                              *
*                                                              *
*                                                              *
*                                                              *
*                                                              *
*                                                              *
*                                                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
WebSphere Application Server was failing to properly refresh
the runtime LTPA keys.

Problem conclusion

WebSphere Application Server has been modified to properly
refresh the runtime LTPA keys during a dynamic SSL update.
In addition, refreshing the runtime LTPA keys using this
sequence of commands requires the -keySetGroupUpdateRuntime
flag, with a setting of true, to be passed as an option to the
$AdminTask generateKeyForKeySetGroup command task. This option
is not currently documented. An example wsadmin command
task looks like this:

$AdminTask generateKeyForKeySetGroup {-keySetGroupName
CellLTPAKeySetGroup -keySetGroupUpdateRuntime true}

The fix for this APAR is currently targeted for inclusion in
fixpack 6.1.0.25 and 7.0.0.5.  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
PK73552
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
2008-10-09
Closed date
2009-03-02
Last modified date
2009-03-02

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
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK73552: PROBLEMS WITH NODE SYNCHRONIZATION AFTER LTPA KEYS ARE GENERATED VIA SCRIPT.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?