IBM Support

PK65059: THE WS-SECURITY WIZARD NEEDS A DEFAULT NAME IN SIGNINGINFO - NOT BLANK.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The JAX-RPC Web services created by the Web services
    security wizards in WebSphere Application Server
    Toolkit v6.1 do not place default names in the bindings
    generated for signingInfo and other elements
    such as Transform.  Instead, they are generated
    with blank names in violation of the
    DTDs for ibm-webservices-bnd.xmi and
    ibm-webservicesclient-bnd.xmi.
    
    The wizards will be corrected to generate default names
    for these fields.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of WebSphere Application Server   *
    *                  Toolkit v6.1.1 and Rational Application     *
    *                  Developer v7                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: The Web Services Security Wizard does   *
    *                      not provide name for signingInfo in     *
    *                      webservice.xml                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using Web Service Security Wizard to add signature,
    encryption, or authorization for a web service/client, the
    correspondent entry in the xml metadata misses the "name"
    attribute. This does not comply with the DTD file.  As a
    result, the WebSphere Application Server administrative console
    cannot be used to edit these security features, once the
    project is published to the server.
    

Problem conclusion

  • With the fix of this APAR, a default name will be given to
    these elements in the xml file, and these security features
    can be edited via the WebSphere Application Server
    administrative console.
    
    The fix for this APAR is currently targeted for inclusion in
    the WebSphere Application Server Toolkit fixpack 7.1.1.7 and
    Rational Application Developer fixpack 7.0.0.7.  Please refer
    to the following Recommended Updates page for WebSphere
    Application Server Toolkit delivery information:
    http://www.ibm.com/support/docview.wss?uid=swg27004980
    and the following Recommended Updates page for Rational
    Application Developer delivery information:
    http://www.ibm.com/support/docview.wss?uid=swg27007823
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK65059

  • Reported component name

    WEBAPP SERVER A

  • Reported component ID

    5724J0820

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-04-25

  • Closed date

    2008-05-30

  • Last modified date

    2008-05-30

  • 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

    WEBAPP SERVER A

  • Fixed component ID

    5724J0820

Applicable component levels

  • R610 PSY

       UP

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

Document Information

Modified date:
23 October 2021