Win a copy of Functional Reactive Programming this week in the Other Languages forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

WS-Security, <wsse:Security> Missing in client request

 
Ravi Choudhari
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I am trying to implement a secure webservice using WS-Security in

JBoss 5.1 following the steps in

http://www.developer.com/java/other/article.php/3802631/Securing-Web-Services-in-JBoss-Application-Server-with-WS-Security.htm


On the server Side I have:


Service:



standard-jaxws-endpoint-config.xml



jboss-wsse-server.xml




I have copied jboss-wsse-server.xml, standard-jaxws-endpoint-config.xml, server.keystore, server.truststore to META-INF directory of the server project.



And on the client side I have:


standard-jaxws-client-config.xml



jboss-wsse-client.xml




Client Application:




I have copied standard-jaxws-client-config.xml, jboss-wsse-client.xml and client.keystore, client.truststore to META-INF directory of the client.


But, When there is request from the client, I am getting the following Execption.


Exception in thread "main"

javax.xml.ws.soap.SOAPFaultException: This service requires <wsse:Security>, which is missing.


I have checked the request SOAP message & response messages, The client is not adding any <wsse:Security>, which is expected by the server.

Is there anything I am missing on client side which is preventing adding <wsse:Security> to request?

 
Pk Martin
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator


This is for HTTP Authentication, which is different than SOAP Authentication.
 
Ulf Dittmer
Rancher
Posts: 42968
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This is for HTTP Authentication, which is different than SOAP Authentication.

Um, yes, so it is not relevant here.
 
Pk Martin
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ulf Dittmer wrote:
This is for HTTP Authentication, which is different than SOAP Authentication.

Um, yes, so it is not relevant here.


I'll clarify. Injecting "username" and "password" in such a way will not be sufficient for the WS-Security. If the original poster showed the above client-code to convey that that was how he was trying to provide credentials to a web service protected by WS-Security, that will not work because



puts the username and password in the HTTP header, not the SOAP header. If the original poster intended to convey something else by showing the above client-code, I apologize.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic