Usernametoken + JaxWS Client + WLS 10.3 not working

Question

I have a webservice deployed and exposed on ESB (jaxws)
It is secured and the policy used is UsernameToken
When i try to access with SOAP UI it works fine when i specify the right username and password.
When I generate a jaxws client for this secured webservice i use clientgen ant task for generating the stubs and i use this code to call the webservice :
// basic Jax-WS service client
final WSImpl provisioningClient = new WSImpl(serviceLocation,SERVICE_QNAME);
securedPort = provisioningClient.getPortTypeSoapPort();
// adding simple UsernameToken
final List credProviders = new ArrayList(1);
credProviders.add(new ClientUNTCredentialProvider(username, password));
final Map<String, Object> rc = ((BindingProvider) projectProvisioningSecuredPort).getRequestContext();
rc.put(WSSecurityContext.CREDENTIAL_PROVIDER_LIST, credProviders);
BUT i get javax.xml.ws.soap.SOAPFaultException: No Security header in message but required by policy.
     at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:188)
     at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:108)
     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 $Proxy29.getProfile(Unknown Source)
when i intercept the soap xml message sent to the web service i do not see indeed thar the header has the information needed for security.
The client is a standalone java client referencing weblogic 10.3 jar weblogic.jar
Same behaviour in a deployed verision of the client into a WLS.
Any idea ?
Thanks

Answer 1

hi ,
I just now tested a fresh version of that Sample in WLS10.3 and it worked for me... I have uploaded the testcase to : http://www.4shared.com/file/Z0faeSK7/JAXWS_UserName_Token.html Can u please try it once. may be some very small thing might be different...in our testcases.
I added the following JAVA_OPTION in server side as well as at client run task <b>"-Dweblogic.wsee.verbose=*" </b> to see the SOAP Header... I got the following request at Server Side:
<font color=maroon>
<?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
*<S:Header>*
*<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" S:mustUnderstand="1"><wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="unt_A72VgTwBn1F12D3T">*
*<wsse:Username>weblogic</wsse:Username>*
*<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">weblogic</wsse:Password>*
*<wsse:Nonce EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">GPAx6+6eyqF82YcqviBgBF2v46kYA7ZBK+w+7MpITSg=</wsse:Nonce>*
*<wsu:Created>2010-09-10T10:20:34Z</wsu:Created>*
*</wsse:UsernameToken>*
*</wsse:Security>*
*</S:Header>*
<S:Body>
<ns2:sayHello xmlns:ns2="http://security_jws.webservices.examples/">
<arg0>World</arg0>
</ns2:sayHello>
</S:Body>
</S:Envelope>
</font>
ANT Client side
<target name="run" >
<java fork="true" classname="client.SecureHelloWorldClient" failonerror="false" >
<classpath refid="client.class.path"/>
<arg line="weblogic weblogic" />
<font color=red> <jvmarg value="-Dweblogic.wsee.verbose=*" />
</font>
</java>
</target>
Thanks
Jay SenSharma