IBM Support

PI78596: FEDERATED NODE MIGRATION USING THE WRONG SSL PROPERTIES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When migrating a federated node with client authentication
    enabled, it is possible for the unconfigured target node's ssl
    properties to be used to connect to the dmgr instead of the
    correct ssl properties from the old source node. This results
    in various SSLHandshakeException errors when the file transfer
    client code is attempting to connect to the dmgr.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server migration tools that have client     *
    *                  authentication enabled, and are migrating   *
    *                  a federated node.                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: The migration post upgrade process      *
    *                      doesn't use the correct SSL properties  *
    *                      when setting up a connection used for   *
    *                      file transfers                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When migrating a federated node with client authentication
    enabled, the un-configured target node's SSL properties are
    used to connect to the dmgr instead of the correct SSL
    properties from the old source node. This results in various
    SSLHandshakeException errors coming from the file transfer
    client code.
    

Problem conclusion

  • Updated the WASPostUpgrade process to add the SSL properties
    onto the thread so that the file transfer code picks them up,
    instead of loading defaults from the yet to be migrated
    ssl.client.props file in the target profile
    .
    The fix for this APAR is currently targeted for inclusion in
    fix pack 9.0.0.4.  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

    PI78596

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-03-22

  • Closed date

    2017-05-18

  • Last modified date

    2017-05-18

  • 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

  • R900 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":"9.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022