Win a copy of Mesos in Action this week in the Cloud/Virtualizaton forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

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

 
sri kasireddy
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Team,

Someone please respond...
we are running out of time...
 
senthilkumar vedachalam
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

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
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic