WLS 10.3: Unable To Consume A Webservice After Enabling Security Policy On Weblogic 10.3

(Doc ID 1113618.1)

Last updated on APRIL 05, 2018

Applies to:

Oracle WebLogic Server - Version 10.3 to 10.3.1
Information in this document applies to any platform.
***Checked for relevance on 02-July-2014***

Symptoms

On trying to create a simple message level security for a Webservice using JAX-WS implementation with
the help of the provided documentation (see references link below) you might run into the below issue.

On Weblogic 10.3, you might have enabled policy using annotation:

@Policies({
attachToWsdl=false)
})

However, when you try to consume from a Webservice client, you will get the below exception on the client but on the server side there are no errors.

javax.xml.ws.soap.SOAPFaultException: MustUnderstand
headers:[{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity- secext-1.0.xsd}Security] are not understood
at
com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:188)
at
com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:1
08)
at
com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119
)
at
com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)

at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)
at $Proxy26.printMessage(Unknown Source)
at
demowsclient.wrapper.ClientWrapper.main(ClientWrapper.java:104)

Changes

Configuring Simple Message level Security for JAX-WS Webservice.

Cause

	Sign In with your My Oracle Support account
	Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms