-
Oct 11th, 2012, 04:20 PM
#1
Spring WebServices Soap Fault Security Exception regarding Password
I am new to Spring Web Services, I have a very basic question maybe someone can answer it:
I am getting an XWSSecurityException when trying to write a client to talk to a WS server. The exception says that I am sending Password-Digest instead of Plain-Text Password. I don't see where I can configure to fix it.
Here is the section where the Wss4jSecurityInterceptor is configured in my spring-context file:
<bean id="wsSecurityInterceptor" class="org.springframework.ws.soap.security.wss4j. Wss4jSecurityInterceptor">
<property name="securementActions" value="UsernameToken"/>
</bean>
The message is shown below.
Thanks a lot!
-cy-
[org.springframework.ws.soap.saaj.SaajSoapMessageFa ctory] - Creating SAAJ 1.3 MessageFactory with SOAP 1.1 Protocol
Exception in thread "main" org.springframework.ws.soap.client.SoapFaultClient Exception: com.sun.xml.wss.XWSSecurityException: Receiver Requirement for Plain-Text Password has not been met, Received token has Password-Digest; nested exception is com.sun.xml.wss.XWSSecurityException: com.sun.xml.wss.XWSSecurityException: Receiver Requirement for Plain-Text Password has not been met, Received token has Password-Digest
at org.springframework.ws.soap.client.core.SoapFaultM essageResolver.resolveFault(SoapFaultMessageResolv er.java:37)
at org.springframework.ws.client.core.WebServiceTempl ate.handleFault(WebServiceTemplate.java:738)
at org.springframework.ws.client.core.WebServiceTempl ate.doSendAndReceive(WebServiceTemplate.java:564)
at org.springframework.ws.client.core.WebServiceTempl ate.sendAndReceive(WebServiceTemplate.java:502)
at org.springframework.ws.client.core.WebServiceTempl ate.marshalSendAndReceive(WebServiceTemplate.java: 351)
at org.springframework.ws.client.core.WebServiceTempl ate.marshalSendAndReceive(WebServiceTemplate.java: 345)
at org.springframework.ws.client.core.WebServiceTempl ate.marshalSendAndReceive(WebServiceTemplate.java: 337)
-
Oct 15th, 2012, 10:51 AM
#2
Found the problem. The solution is to set the wsSecurityInterceptor using a XwsSecurityInterceptor.
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules