IBM Support

PM21088: WS-SECURITY EMITS SOAP 1.1 FAULT CODES IN RESPONSE TO SOAP 1.2 MESSAGES

Fixes are available

7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When implementing a SOAP 1.2 WebService, problems with the
    SOAP Fault Codes that the WebService delivers can be found.
    The Faults follow the SOAP 1.2 syntax and use the SOAP 1.2
    namespace.  However, the value in the node soapenv:Value
    follow the SOAP 1.1 specification.  The soapenv:Value
    delivered by WS-Security is not on the list of SOAP 1.2
    allowed codes.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server V7.0 users *
    *                  of WS-Security enabled web services         *
    *                  applications and SOAP 1.2                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: WS-Security SOAP 1.2 fault codes are    *
    *                      incorrectly emitted with SOAP 1.1       *
    *                      fault codes                             *
    ****************************************************************
    * RECOMMENDATION:  Install a fix pack that contains this APAR. *
    ****************************************************************
    When the WS-Security runtime emits a SOAP Fault in response to
    a SOAP 1.2 message, instead of returning a valid SOAP 1.2
    fault code, it returns a SOAP 1.1 fault code.  For example:
    
    <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope
    xmlns:soapenv="
    http://www.w3.org/2003/05/soap-envelope">
    <soapenv:Body>
    <soapenv:Fault xmlns:axis2ns71="http://schemas.xmlsoap.
    org/soap/envelope/">
    <soapenv:Code>
    <soapenv:Value>axis2ns71:Server.
    securityException</soapenv:Value>
    </soapenv:Code>
    <soapenv:Reason>
    <soapenv:Text xml:lang="en-US">CWWSS6521E: The
    Login failed because of an exception: javax.security.auth.login.
    LoginException: CWWSS7062E: Failed to check username
    [BITS_was_00] and password in the UserRegsitry:
    WSSUserRegistryProcessor.checkRegistry()
    =false</soapenv:Text>
    </soapenv:Reason>
    <soapenv:Detail/>
    </soapenv:Fault>
    </soapenv:Body>
    </soapenv:Envelope>
    
    Using the above example, the SOAP 1.2 fault code that should
    be returned by the WS-Security runtime should be
    "soapenv:Sender".
    

Problem conclusion

  • The WS-Security runtime is updated to emit the proper SOAP 1.2
    fault code when a fault is returned in response to a SOAP 1.2
    message.  In order to enable this behavior, the following
    WS-Security general custom property must be set to true:
    
    com.ibm.wsspi.wssecurity.login.useSoap12FaultCodes
    
    Valid values for this property are true and false; the default
    is false.
    
    This property should be set in the WS-Secrutiy "Inbound" or
    "Inbound and Outbound" custom properties:
    
    (bindingName)->WS-Security->Custom Properties
    
    Following is an example of a valid SOAP 1.2 fault that will be
    returned when the property is set to true:
    
    <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope
    xmlns:soapenv="
    http://www.w3.org/2003/05/soap-envelope">
    <soapenv:Body>
    <soapenv:Fault>
    <soapenv:Code>
    <soapenv:Value>soapenv:Sender</soapenv:Value>
    <soapenv:Subcode>
    <soapenv:Value
    xmlns:axis2ns1="http://docs.oasis-open.org/wss/2004/01/oasis-
    200401-wss-wssecurity-secext-1.0.xsd">
    axis2ns1:FailedAuthentication</soapenv:Value>
    </soapenv:Subcode>
    </soapenv:Code>
    <soapenv:Reason>
    <soapenv:Text>CWWSS6521E: The Login failed because
    of an exception: javax.security.auth.login.LoginException:
    CWWSS7062E: Failed to check username [user1] and password in
    the UserRegsitry: WSSUserRegistryProcessor.checkRegistry()=false
    </soapenv:Text>
    </soapenv:Reason>
    <soapenv:Detail></soapenv:Detail>
    </soapenv:Fault>
    </soapenv:Body>
    </soapenv:Envelope>
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.15.  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

    PM21088

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-08-23

  • Closed date

    2010-09-28

  • Last modified date

    2010-09-28

  • APAR is sysrouted FROM one or more of the following:

    PM19639

  • 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

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021