Fixes are available
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
I can't login to Bluemix with tWAS wsadmin, using bluemiUtility object: root@nest-twas-dt7-dmgr:/opt/DayTrader/WAS/profiles/dmgr/bin# ./wsadmin.sh -username xxx -password xxx -lang jython WASX7209I: Connected to process "dmgr" on node dmgr using SOAP connector; The type of process is: DeploymentManager WASX7031I: For help, enter: "print Help.help()" wsadmin>BluemixUtility.login("user=xxxxxxxxx", "password=******", "api=xxxxx", "org=xxxxxxxxxx", "space=dev") WASX7015E: Exception running command: "BluemixUtility.login("user=xxxxxx", "password=*****, "api=xxxxx", "org=xxxxxxxxx", "space=dev")"; exception information: com.ibm.bsf.BSFException: exception from Jython: Traceback (most recent call last): File "<input>", line 1, in <module> File "/opt/DayTrader/WAS/scriptLibraries/bluemixutility/BluemixUtilit y.py", line 228, in login raise Exception(val) Exception: <type 'java.lang.Exception'> java.lang.Exception: com.ibm.ws.bluemix.utility.cloudfoundry.CloudFoundryException: BMUX0012E: An unexpected error occurred when performing an IBM Bluemix operation. Error: com.ibm.jsse2.util.h: PKIX path building failed: java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause is: java.security.cert.CertPathValidatorException: The certificate issued by CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US is not trusted; internal cause is: java.security.cert.CertPathValidatorException: Certificate chaining error
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server bluemixUtility command * **************************************************************** * PROBLEM DESCRIPTION: bluemixUtility login fails with * * CertPathValidatorException * **************************************************************** * RECOMMENDATION: * **************************************************************** IBM Bluemix updated the certificate requirements for login and the certificates provided by WebSphere Application Server are no longer valid.
Problem conclusion
The certificate file provided by WebSphere Application Server for logging in to IBM Bluemix has been updated to comply with the new requirements. The bluemixUtility command will successfully connect to IBM Bluemix. The fix for this APAR is currently targeted for inclusion in fix pack 9.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
PI85666
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-08-10
Closed date
2017-09-14
Last modified date
2017-09-14
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
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R900 PSY
UP
Document Information
Modified date:
04 May 2022