Fixes are available
9.0.0.1: WebSphere Application Server traditional V9.0 Fix Pack 1
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
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
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
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
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
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
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
The SAML Web SSO AdminTask command importSAMLIdpMetadata fails when trying to import configuration information from an ADFS IdP metadata file. Below is wsadmin interaction session code to demonstrate the defect: wsadmin>metadataFile = 'FederationMetadata_PROD_ORIGINAL.xml' wsadmin>attrs = ['-securityDomainName', 'testBuild_ADFS', '- idpMetadataFileName', '/tmp/%s' % metadataFile, '-signingCertAlias', 'ADFS signer'] wsadmin>importSuccess = AdminTask.importSAMLIdpMetadata( attrs ) WASX7015E: Exception running command: "importSuccess = AdminTask. importSAMLIdpMetadata( attrs )"; exception information: com.ibm.bsf.BSFException: exception from Jython: Traceback (innermost last): File "<input>", line 1, in ? com.ibm.ws.scripting.ScriptingException: java.lang.InstantiationError: java.lang.InstantiationError: oasis.names.tc.saml._2_0.metadata. RoleDescriptorType at com.ibm.ws.scripting.adminCommand.AdminCmdController. executeCmd(AdminCmdController.java:1914) at com.ibm.ws.scripting.adminCommand.AdminCmdController. processCmd(AdminCmdController.java:318)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server users of * * SAML Web Single sign-on feature * **************************************************************** * PROBLEM DESCRIPTION: The SAML wsadmin command * * importSAMLIdpMetadata fails when * * importing metadata from ADFS Identity * * Provider. * **************************************************************** * RECOMMENDATION: Install a fix pack that includes this APAR * * * **************************************************************** The wsadmin command importSAMLIdpMetadata failed when importing metadata from ADFS Identity Provider because it could not process some WS-Federation elements like <RoleDescriptorType>. The importSAMLIdpMetadata command failed with the following exception: com.ibm.ws.scripting.ScriptingException: java.lang.InstantiationError: java.lang.InstantiationError: oasis.names.tc.saml._2_0.metadata.RoleDescriptorType
Problem conclusion
Ths problem occurred because the IdP metadata file contained WS-Federation metadata that was not processed by the importSAMLIdpMetadata command. The problem was fixed by updating the SAML importSAMLIdpMetadata command to correctly process all the WS-Federaqtion metadata in the IdP metadata file. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.43, 8.0.0.13, 8.5.5.11 and 9.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
Comments
APAR Information
APAR number
PI62619
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-05-17
Closed date
2016-06-17
Last modified date
2019-01-15
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
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP
R900 PSY
UP
Document Information
Modified date:
04 May 2022