Ahh, I see. Okay first its been a while since I have used axis 2 / rampart on
the client side. I have an Android client which has extreme difficulty
supporting axis2 so I created the SOAP message using basic Java http classes.
But I have done it using axis2/rampart. I will see if I can dig th
Prakash,
After looking at that old code I see that you do exactly the same thing as I
did. Of course that raises the question of whether or not your STS request was
successfully generating the token. One has to take the effort to extract the
token from the STS response and store it using the
Brian,
I was using rampart1.5, replaced it with rampart1.6.1 now and
tested. It is working, now I can see the SAML Assertion added to soap header. I
guess issue with the lower version jars. Thanks for your help.
Can you suggest any tutorial for axis rampart..
From: Brian Reinho
Prakash,
Unfortunately I know of no tutorials. And I know their examples are not correct
in the secure domain. I had to make a number of fixes on the client side to get
it to work.
Brian
From: Rangasamy, Prakash [mailto:prakash.rangas...@scientificgames.com]
Sent: Friday, April 3, 20
M.A.M. Sanz created AXIS2-5692:
--
Summary: Conflict between wsdl2java and Apache Rampart's libraries
Key: AXIS2-5692
URL: https://issues.apache.org/jira/browse/AXIS2-5692
Project: Axis2
Issue Typ
