IBM Support

IT36114: SOAPASYNCRESPONSE NODE THOWS BIP3701 WHEN RESPONSE HAS WS-SECURITY HEADERS.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • SOAPAsyncResponse node, with its default configurations, throws
    BIP3701 error while receiving response message that has
    ws-security headers. The BIP3701 exception and stderr file will
    report the following error.
    
    
      org.apache.axis2.AxisFault: MustUnderstand Header-Check Failed
    for Header:
    {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecur
    ity-secext-1.0.xsd}Security
    
    
    When SOAPAsyncResponse node has not configured with policy set
    and binding, it should not validate the ws-security headers. The
    SOAPRequest node behaves correctly and doesnt report the error.
    

Local fix

  • -
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All Users of IBM Integration Bus V10.0 and IBM App Connect
    Enterprise V11.0 using SOAPAsyncRequest -  SOAPAsyncResponse
    flow.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    SOAPAsyncResponse node, with its default configurations, throws
    BIP3701 error while receiving response message that has
    ws-security headers. Along with the BIP3701 exception, the
    stderr file will report the following error.
    
    
      org.apache.axis2.AxisFault: MustUnderstand Header-Check Failed
    for
    Header:{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-
    wssecurity-secext-1.0.xsd}Security
    
    
    When SOAPAsyncResponse node has not configured with policy set
    and binding, it should not validate the ws-security headers. The
    SOAPRequest node behaves correctly and doesnt report the error.
    

Problem conclusion

  • The SOAPAsyncResponse node no longer validates the ws-security
    headers when no policyset or bindings provided and thus avoids
    throwing <span style="background-color:rgb(255, 255,
    255)">BIP3701 </span>exception.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.24
    v11.0      11.0.0.13
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT36114

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-03-30

  • Closed date

    2021-06-07

  • Last modified date

    2021-09-16

  • 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

    APP CONNECT ENT

  • Fixed component ID

    5724J0550

Applicable component levels

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00"}]

Document Information

Modified date:
17 September 2021