Sorry in the last message I forgot to put another diference that maybe more
trouble,
Rampart:
<wsa:To>http://localhost:8088/gateway/services/SID0003001</wsa:To>
<wsa:MessageID>urn:uuid:AECDDCE53586EDD65F1232669747468</wsa:MessageID>
<wsa:Action>http://test.heinsohn.com//talkToMe</wsa:Action>
...
In the Oracle version that part doesn't exist, there is no
<wsa:To>,<wsa:MessageID> or <wsa:Action> Tags..
Marcus V. Sánchez D.
______________________
Enterprise Developer.
Sun Certified Java Programmer (SCJP)
On Fri, Jan 23, 2009 at 8:35 AM, m4rkuz <[email protected]> wrote:
>
> Hi Everyone,
>
> I'm new to rampart but learning quickly, well not quikly enough because
> I've been having some problems trying to invoke a WS that was made using
> oracle tools, is supposed to be easy initialy I just had to sing the message
> but even at that level I haven't been able to do it, I went thru examples on
> the distribution (1.4.1) and some webs but I'm still getting :
>
> FAULT CODE: UnsupportedSecurityToken FAULT MESSAGE: An unsupported token
> was provided
>
> I asked for a successful soap message example to compare the one I
> generate with a good one, (attached to the message) the only big diference I
> see is that in the rampart made soap message all the URI attributes are not
> encripted as they do in the oracle example
>
> Rampart:
> ...
> <ds:Reference URI="#Id-27978063">
> ..
> <ds:Reference URI="#Timestamp-14707008">
> ....
> <wsse:Reference URI="#CertId-1097338"
> ....
>
> Oracle:
> ..
> <dsig:Reference URI="#bcyKqLafyGSUXDbAEVXbIg22">
> ...
> <dsig:Reference URI="#5KdQ0TRTux484dTYM5mpHQ22">
> ....
> <wsse:Reference URI="#5KdQ0TRTux484dTYM5mpHQ22"
> ....
>
>
> What is all about? (I'm really newbie) and how can I match that using
> rampart ??
>
>
> Best Regards,
>
>
> Marcus V. Sánchez D.
> ______________________
> Enterprise Developer.
> Sun Certified Java Programmer (SCJP)
>
>
