PK85043: WSEC5403E OCCURS WHEN USING DEFAULT BINDINGS, BUT SIGNING ISN'T CONFIGURED

Fixes are available

APAR status

Closed as program error.

Error description

WSEC5403E occurs when a WS-Security enabled JAX-RPC
application uses default WS-Security bindings, but signing isn't
configured

Local fix

Specifying binding information within application, not using
default binding from Administrative Console.

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server users of   *
*                  WS-Security enabled JAX-RPC applications    *
*                  utilizing the default WS-Security           *
*                  bindings                                    *
****************************************************************
* PROBLEM DESCRIPTION: A WSEC5403E exception occurs when a     *
*                      JAX-RPC application uses default        *
*                      WS-Security bindings, but signing       *
*                      isn't configured                        *
****************************************************************
* RECOMMENDATION:  Install a fix pack that contains this APAR. *
****************************************************************
When a WS-Security enabled JAX-RPC web services application
uses out-of-the-box default bindings, but the application does
not include XML Digital Signature configuration with the
gen_signpart and con_signpart signing part definitions, an
exception like the following will occur in the trace.log,
SystemOut.log, and FFDC:

com.ibm.wsspi.wssecurity.SoapSecurityException: WSEC5403E:
PartReference in SigningInfo: referenced message part is
required:
com.ibm.ws.webservices.wssecurity.confimpl.PrivateCommonConfig$S
igningReferenceConfImpl(reference=[null],
digestMethod=[com.ibm.ws.webservices.wssecurity.confimpl.Private
CommonConfig$AlgorithmConfImpl(algorithm=[http://www.w3.org/2000
/09/xmldsig#sha1], type=[null], properties=[{}])],
transforms=[[com.ibm.ws.webservices.wssecurity.confimpl.PrivateC
ommonConfig$AlgorithmConfImpl(algorithm=[http://www.w3.org/2001/
10/xml-exc-c14n#], type=[null], properties=[{}])]],
properties=[{}]).

Problem conclusion

The WS-Security JAX-RPC runtime was updated to skip validation
of the use of the XML Digital Signature signing parts when an
application is configured to use the WS-Security default
bindings.

The signing parts defined in the WS-Security default
configuration are available for use by an application, but are
not required to be used by an application.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.29 and 7.0.0.7.  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
PK85043
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-04-21
Closed date
2009-07-15
Last modified date
2009-07-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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"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:
29 December 2021

Tips

PK85043: WSEC5403E OCCURS WHEN USING DEFAULT BINDINGS, BUT SIGNING ISN'T CONFIGURED

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?