PK42833: WEB SERVICE CLIENT INVOKING WEB SERVICE USING WS-SECURITY RECEIVES EXCEPTION WHEN GLOBAL SECURITY IS DISABLED.

Fixes are available

APAR status

Closed as program error.

Error description

A web service is configured for Authentication
using UsernameToken or LTPAToken.  It is deployed to an
application server where global security is DISABLED.

When the web service is invoked by a web service client which
correctly provides the required UsernameToken or LTPAToken, the
web service invocation fails.  The following fault is
returned back to the web service client:

<soapenv:Fault>
<faultcode
xmlns:p55="http://docs.oasis-open.org/wss/2004/01/oasis-
200401-wss-wssecurity-secext-1.0.xsd">p55:
FailedAuthentication</faultcode>
<faultstring>
<![CDATA[com.ibm.wsspi.wssecurity.SoapSecurityException:
WSEC6500E:
There is no candidate used to login.]]></faultstring>
<detail encodingStyle=""/>
</soapenv:Fault>


The above error does not occur if global security is ENABLED on
the application server hosting the web service.

Local fix

Enable global security on the application server hosting the web
service.

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server versions   *
*                  6.0.2 and 6.1 administrators and            *
*                  programmers of JAX-RPC web services         *
*                  applications                                *
****************************************************************
* PROBLEM DESCRIPTION: When developing or debugging JAX-RPC    *
*                      web services applications, there        *
*                      isn't a way to run a web service        *
*                      without application security enabled    *
*                      without removing the WS-Security        *
*                      information from the deployment         *
*                      descriptors.                            *
****************************************************************
* RECOMMENDATION:  Install a fix pack that contains this APAR. *
****************************************************************
If an application's WS-Security constraints require
WebSphere application security be enabled, there isn't a way to
run the service with application security disabled without
removing the WS-Security information from the deployment
descriptors.  If the service is run with the deployment
descriptors unmodified, a SoapSecurityException will occur.

Sometimes, during development or debuggging of an application,
it may be necessary to turn off application security for some
reason on the application server.  In this case, there should
be some way to override the WS-Security constraints on the
application without totally removing them since removing and
re-applying WS-Security constraints from an application is
sometimes very difficult.

Problem conclusion

A web services security property was added to disable
WS-Security if WebSphere application security is disabled.

The following web services security property was added for
use on the application server:

com.ibm.wsspi.wssecurity.config.
disableWSSIfApplicationSecurityDisabled

This property will enable web services security to not enforce
configured WS-Security constraints if WebSphere application
security is disabled on the application server.

This will enable system administrators and application
programmers to debug aspects of their services in
a non-secure environment without having to remove the
WS-Security information from their deployment descriptors.

It is important to note that the use of this property is only
intended for diagnostic purposes and not for a production
environment.

Valid values for this property are true and false and defaults
to false.  It can be specified in the following locations, in
priority order:

1)Web services: Default bindings for Web services security
(cell or server)-> Default consumer bindings:properties (could
apply to all apps in the cell)

2)Web services: Default bindings for Web services security
(cell or server)-> Additional Properties: properties (could
apply to all apps in the cell)

3) JVM system property (applies to all application on the
server)

This update will be avaliable in fixpacks 6.0.2.23 and
6.1.0.13.
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
PK42833
Reported component name
WEBSPH APP SERV
Reported component ID
5724J0800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-04-06
Closed date
2007-07-26
Last modified date
2009-02-03

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

PK78538

Modules/Macros

```
SECURITY SERVICES WEB
```

Fix information

Fixed component name
WEBSPH APP SERV
Fixed component ID
5724J0800

Applicable component levels

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z 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

PK42833: WEB SERVICE CLIENT INVOKING WEB SERVICE USING WS-SECURITY RECEIVES EXCEPTION WHEN GLOBAL SECURITY IS DISABLED.

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:

Modules/Macros

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

Document Information

Share your feedback

Need support?