GeeCON Prague 2014*
The moose likes Web Services and the fly likes Configuring Axis2 WS Security, Rampart etc for a Web Service Client Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Java » Web Services
Bookmark "Configuring Axis2 WS Security, Rampart etc for a Web Service Client" Watch "Configuring Axis2 WS Security, Rampart etc for a Web Service Client" New topic
Author

Configuring Axis2 WS Security, Rampart etc for a Web Service Client

Sebastian Boccardi
Greenhorn

Joined: Apr 03, 2013
Posts: 1
Hi,

Im having some trouble configuring my web service client. As i don´t have much experience and i had an example of a valid request from a previously developed client (phasing out), i sniffed the valid request and compared it to the request from the new client being developed.

I will paste both here, maybe somebody can give my some pointers on how to configure the client to generate a valid request:

First the request that works:



now the request that fails (FAILS with this error: The security token could not be authenticated or authorized ---> Invalid Password)



As you see there is some differences (some info was changed to keep some private info, well... private).

The first is the standalone property or whatever on the xml tag.
Message id is not generated in the same "fashion" also i think is not important...
Timestamp in the valid request has some info equivalent to message id
Nonce doen´t specify encoding type, which makes me believe is not the same coding type
UsernameToken has a SecurityToken thing also related to messageid.

Well any tip is appreciated....

Sebastian


 
GeeCON Prague 2014
 
subject: Configuring Axis2 WS Security, Rampart etc for a Web Service Client