File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes JBoss/WildFly and the fly likes SOAPFaultException: Security Requirements not  met - No Security header in message Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "SOAPFaultException: Security Requirements not  met - No Security header in message" Watch "SOAPFaultException: Security Requirements not  met - No Security header in message" New topic
Author

SOAPFaultException: Security Requirements not met - No Security header in message

sri kasireddy
Greenhorn

Joined: Mar 26, 2012
Posts: 3
Im using JBoss 5.1GA, jdk 1.6.0_24, Windows

When i try to connect one of my web service in my app im getting the following error.

“javax.xml.ws.soap.SOAPFaultException: Security Requirements not met - No Security header in message ”

Currently the same app is working fine in Websphere.
can you give details why i'm facing this issue.
thanks in advance.
sri kasireddy
Greenhorn

Joined: Mar 26, 2012
Posts: 3
Hi Team,

Someone please respond...
we are running out of time...
senthilkumar vedachalam
Greenhorn

Joined: May 14, 2012
Posts: 1

The SOAP Fault Exception raised here is due to the mismatch between the Metro jar versions between the Jboss and the web service client code. In this case the web service client was created with Metro 2.0.1 and the Jboss native JAXWS jars were not able to support this.

So we created a new web service client code with Metro 2.2 and copied the essential Metro 2.2 and JAXWS-RI 2.2 jars (webservices-rt.jar, jaxws-api.jar) in the endorsed folder of the Jboss.Also deleted the native jars (Jbossws-native-jaxrpc.jar, Jbossws-native-jaxws-ext.jar, Jbossws-native-jaxws.jar, Jbossws-native-saaj.jar) from the Jboss\lib\endorsed directory. This fixed the issue.
jim wowchuk
Greenhorn

Joined: Oct 25, 2012
Posts: 1
We had this occur when the SUN provider in jre/lib/security/java.security file was at a lower priority than an explicity BouncyCastle provider we used.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: SOAPFaultException: Security Requirements not met - No Security header in message