It Worked like a charm!! So many thanks!!!
Marcus V. Sánchez D. ______________________ Enterprise Developer. Sun Certified Java Programmer (SCJP) PD: Thanks Again!! On Wed, Feb 4, 2009 at 1:29 PM, Nandana Mihindukulasooriya < nandana....@gmail.com> wrote: > Hi Marcus, > try changing > > <sp:X509Token sp:IncludeToken=" > http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Never";> > > to > > <sp:X509Token sp:IncludeToken=" > http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient > "> > > in the <sp:RecipientToken> assertion. > > thanks, > nandana > > > On Wed, Feb 4, 2009 at 11:26 PM, m4rkuz <m4r...@gmail.com> wrote: > >> HI Nandana, >> >> Attached to this message is the soap message generated by rampart(the one >> that fails), is quite different and the first big difference I see is that >> oracle made soap has two (2) BinarySecurityToken and the rampart made just >> have one. >> >> the error I get in the client side wrap around the soap response message >> is: >> >> *InvalidSecurity FAULT MESSAGE: An invalid token was provided* >> >> >> >> Any Ideas? >> >> I would ask for the Oracle Log, to post it. >> >> >> Marcus V. Sánchez D. >> ______________________ >> Enterprise Developer. >> Sun Certified Java Programmer (SCJP) >> >> >> On Wed, Feb 4, 2009 at 12:21 PM, Nandana Mihindukulasooriya < >> nandana....@gmail.com> wrote: >> >>> Hi Marcus, >>> From the first look, it seems the policy you have matches the >>> success SOAP message. Do you get an error from the OWM side when you use >>> this policy at the client ? If so what is the error message ? The returning >>> message may not say what the error is, but if you have access to the OWM >>> logs, you will be able to find out what the error is. And can you attach the >>> message generated with this policy in Axis2/Rampart client so we can compare >>> it. >>> >>> thanks, >>> nandana >>> >>> >>> On Wed, Feb 4, 2009 at 10:37 PM, m4rkuz <m4r...@gmail.com> wrote: >>> >>>> Hi Eeveryone, >>>> >>>> I've trying for a while now to make a proper client for a web service >>>> made in oracle (OWM ) with Axis2 and Rampart, I had been able to overcome >>>> some issues about x509v3 and the hole signing process but now in the last >>>> part the Encription I just don't know how to declare it properly for the >>>> client to sussesfuly call the WS. >>>> >>>> I had an example of a suscessfull soap message (oracle client generated) >>>> and a copy of my policy for someone to take a quick look and help me out. >>>> >>>> >>>> The files are attached. >>>> >>>> that same policy file and without the encription configuration works >>>> fine if the WS require only signing, so is not totally wrong. >>>> >>>> >>>> >>>> If someone had an idea how to mimic that message from axis2, would help >>>> me a lot, >>>> >>>> >>>> Marcus V. Sánchez D. >>>> ______________________ >>>> Enterprise Developer. >>>> Sun Certified Java Programmer (SCJP) >>>> >>> >>> >>> >>> -- >>> Nandana Mihindukulasooriya >>> WSO2 inc. >>> >>> http://nandana83.blogspot.com/ >>> http://www.wso2.org >>> >> >> > > > -- > Nandana Mihindukulasooriya > WSO2 inc. > > http://nandana83.blogspot.com/ > http://www.wso2.org >
