Fix (APAR): PK16492 Status: Fix Release: 5.0.2.12 Operating System: AIX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: PK16492 Byte size of APAR: 12744 Date: 2006-03-10 Abstract: In Network Deployment environment, while adding the base node into dmgr the user password information is written into addNode.log file in plain text. Description/symptom of problem: PK16492 resolves the following problem: ERROR DESCRIPTION: Problem: Customer is at WSAS V5.0.2.12 .When client is trying to add base node into dmgr the user password information written into addNode.log file in a plain text . [11/4/05 9:44:19:444 EST] 4513463a AbstractNodeC > fixSetupCmdLine nodenameNetwork {fileTransferConfig=[securityEnabled=true (secure_port,9043), (port,9090), (host,lwpdev3.lotus.com),serverStagingLocation=/opt1/WebSphere/D eploymen tManager/config/temp/], cellName=nodenameNetwork, port=8879, user.install.root=/opt1/WebSphere/AppServer, username=uid=wcsadmin,cn=users,l=Westford,st=Massachusetts,c=US, ou=Lotus ,o=Software Group,dc=ibm,dc=com, type=SOAP, was.install.root=/opt1/WebSphere/AppServer, nodeName=lwpdev2, location=remote, password=Pa88w0rd, host=lwpdev3.lotus.com, was.repository.root=/opt1/WebSphere/AppServer/config} LOCAL FIX: No work-around. PROBLEM SUMMARY USERS AFFECTED: Websphere Application Server version 5.0.2, 5.1.1 and 6.0.2 users who try to add the Base node to the Deployment manager. PROBLEM DESCRIPTION: In Network Deployment environment, while adding the base node into dmgr the user password information is written into addNode.log file in plain text. RECOMMENDATION: None The trace in the addNode.log file is shown below which shows the password in the clear text while adding the base node to the deployment manager: {fileTransferConfig=[securityEnabled=true (secure_port,9043), (port,9090),(host,lwpdev3.lotus.com),serverStagingLocation= /opt1/WebSphere/DeploymentManager/config/temp/], cellName= nodenameNetwork, port=8879,user.install.root= /opt1/WebSphere/AppServer,username=uid=wcsadmin,cn=users, l=Westford,st=Massachusetts,c=US,ou=Lotus,o=Software Group, dc=ibm,dc=com, type=SOAP,was.install.root= /opt1/WebSphere/AppServer, nodeName=lwpdev2,location=remote, password=Pa88w0rd, host=lwpdev3.lotus.com,was.repository.root= /opt1/WebSphere/AppServer/config} Since the password is not encrypted it is shown in this manner. PROBLEM CONCLUSION: The fix provided will encrypt the Password parameter before writing it to addNode.log The fix for this APAR is currently targeted for inclusion in cumulative fixes 5.02.16 and 5.1.1.9 and fixpack 6.0.2.7. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Directions to apply fix: NOTE: Choose the: 1) Release the fix applies to 2) The Editions that apply 3) Delete the Editions & Methods that do not apply and this Note Fix applies to Editions: Release: 5.0.2.12 Application Server (Express or BASE) Install Fix to: Method: 5.0.2.12 Application Server Nodes NOTE: The user must: * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * Be logged in with the same authority level when unpacking a fix, fix pack or refresh pack. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 The Update Installer for V5.0 does not have a maintenance directory. It uses fixpacks and fixes as the location of the unpacked files. 1) Copy PKxxxxx.jar file directly to the maintenance directory 2) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to. 3) Launch Update Installer 4) Enter the installation location of the WebSphere product you want to update. 5) Select the "Install maintenance package" operation. 6) Enter the file name of the maintenance package to install (PKxxxxx.jar file which was copied in the maintenance directory). The V5.0 and V5.1 fix packs and fixes are unpacked as .jar files and should be unpacked into fixpacks or fixes directory. 7) Install the maintenance package. 8) Restart WebSphere Directions to remove fix: NOTE: * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED * DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED * YOU MAY REAPPLY ANY REMOVED FIX Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied. 1) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against. 2) Start Update Installer 3) Enter the installation location of the WebSphere product you want to remove the fix. 4) Select "Uninstall maintenance package" operation. 5) Enter the file name of the maintenance package to uninstall (PKxxxxx.jar). 6) UnInstall maintenance package. 7) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere. Additional Information: After applying the fix node needs to be federated to dmgr for and verify the log files for proper log messages