wood burning stoves*
The moose likes Web Services and the fly likes Axis2- enable security using Rampart Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Axis2- enable security using Rampart" Watch "Axis2- enable security using Rampart" New topic
Author

Axis2- enable security using Rampart

Anjali S Sharma
Ranch Hand

Joined: Jun 29, 2005
Posts: 279


I am following this article to enable security (using Rampart) on my Axis2 webservice.

I have installed Rampart and also engaged it using the admin UI

Now this article instructs to add the following to services.xml

<parameter name="InflowSecurity">
<action>
<items>Timestamp</items>
</action>
</parameter>

<parameter name="OutflowSecurity">
<action>
<items>Timestamp</items>
</action>
</parameter>

At this point the client (soapUI in this case), is not sending any headers while calling the service. So the service should throw a fault.

But in my case, when I call the service using soapUI (and supplying no headers) it does not throw any error.

It seems that Rampart is not getting engaged.

Can you please guide me as to why this could be happening?

thank you
shivendra tripathi
Ranch Hand

Joined: Aug 26, 2008
Posts: 263
Does your wsdl has some policy element saying that it expect time stamp? Can you post your wsdl?


SCJP 1.5(97%) My Blog
Anjali S Sharma
Ranch Hand

Joined: Jun 29, 2005
Posts: 279
shivendra tripathi wrote:Does your wsdl has some policy element saying that it expect time stamp? Can you post your wsdl?


For headers do I need to update my WSDL as well?

Here is my WSDL

 
It is sorta covered in the JavaRanch Style Guide.
 
subject: Axis2- enable security using Rampart
 
Similar Threads
SOAP Header missing using Rampart w/ Axis2 Generated Stub
Dynamically setting the username/password with Rampart.
WSHandler: cannot create instance of password callback
rampart problem with oc4j
Axis2, client handler not getting called