WSDoAllReceiver Question

[Shawn McKinney <sm...@sbcglobal.net>]

Greetings,

We're running Soap transactions through Axis w/ WSS4J
WSDoAllReceiver handler enabled.  With action defined
as below:

<parameter name="action" 
value="UsernameTokenSignature UsernameToken Encrypt"/>

I've had success running very simple message-style
transactions through with user creds passed via
username token.  Furthermore the username token is
signed and encrypted. (obviously)

My problem comes when I vary the Soap payload, passing
an IFX-style instead of simple xml.  In this case, the
signature validation fails on the receiving end.
  
However, when I vary the payload back to a simple
"hello-world" style of message, the  signature
validation succeeds.  ( same client, same service )

My question - Is the action as defined above,
digitally signing the username token only, or the
entire Soap payload?

If it is validating the username token only, why would
the signature fail when I pass bigger, more complex
xml documents through?

With the IFX Soap payload senario, when I change
action to:
<parameter name="action" value="UsernameToken
Encrypt"/>

Then transaction runs successfully.  So it seems that
this problem is limited in scope to the digital sig
processing. 

Thanks,

Shawn

Re: WSDoAllReceiver Question

[Shawn McKinney <sm...@sbcglobal.net>]

Stolen from website:

http://www.ifxforum.org/ifxforum.org/index.cfm

What is IFX?
The Interactive Financial eXchange (IFX) is a mature,
well-designed XML-based, financial messaging protocol,
built by financial industry and technology leaders
incorporating decades of combined experience and best
of breed design principles.

The goal for IFX has been two fold:

   1. To use real business use cases and develop
content that is meaningful and useful to the financial
services industry.
   2. To create a strong, flexible, open architecture
that will support extending the protocol in an
efficient, interoperable manner. 


--- Davanum Srinivas <da...@gmail.com> wrote:

> sorry. dumb question. what's IFX?
> 
> -- dims
> 
> On 7/21/05, Shawn McKinney <sm...@sbcglobal.net>
> wrote:
> > 
> > Greetings,
> > 
> > We're running Soap transactions through Axis w/
> WSS4J
> > WSDoAllReceiver handler enabled.  With action
> defined
> > as below:
> > 
> > <parameter name="action"
> > value="UsernameTokenSignature UsernameToken
> Encrypt"/>
> > 
> > I've had success running very simple message-style
> > transactions through with user creds passed via
> > username token.  Furthermore the username token is
> > signed and encrypted. (obviously)
> > 
> > My problem comes when I vary the Soap payload,
> passing
> > an IFX-style instead of simple xml.  In this case,
> the
> > signature validation fails on the receiving end.
> > 
> > However, when I vary the payload back to a simple
> > "hello-world" style of message, the  signature
> > validation succeeds.  ( same client, same service
> )
> > 
> > My question - Is the action as defined above,
> > digitally signing the username token only, or the
> > entire Soap payload?
> > 
> > If it is validating the username token only, why
> would
> > the signature fail when I pass bigger, more
> complex
> > xml documents through?
> > 
> > With the IFX Soap payload senario, when I change
> > action to:
> > <parameter name="action" value="UsernameToken
> > Encrypt"/>
> > 
> > Then transaction runs successfully.  So it seems
> that
> > this problem is limited in scope to the digital
> sig
> > processing.
> > 
> > Thanks,
> > 
> > Shawn
> > 
> 
> 
> -- 
> Davanum Srinivas -http://blogs.cocoondev.org/dims/
> 

Re: WSDoAllReceiver Question

[Davanum Srinivas <da...@gmail.com>]

sorry. dumb question. what's IFX?

-- dims

On 7/21/05, Shawn McKinney <sm...@sbcglobal.net> wrote:
> 
> Greetings,
> 
> We're running Soap transactions through Axis w/ WSS4J
> WSDoAllReceiver handler enabled.  With action defined
> as below:
> 
> <parameter name="action"
> value="UsernameTokenSignature UsernameToken Encrypt"/>
> 
> I've had success running very simple message-style
> transactions through with user creds passed via
> username token.  Furthermore the username token is
> signed and encrypted. (obviously)
> 
> My problem comes when I vary the Soap payload, passing
> an IFX-style instead of simple xml.  In this case, the
> signature validation fails on the receiving end.
> 
> However, when I vary the payload back to a simple
> "hello-world" style of message, the  signature
> validation succeeds.  ( same client, same service )
> 
> My question - Is the action as defined above,
> digitally signing the username token only, or the
> entire Soap payload?
> 
> If it is validating the username token only, why would
> the signature fail when I pass bigger, more complex
> xml documents through?
> 
> With the IFX Soap payload senario, when I change
> action to:
> <parameter name="action" value="UsernameToken
> Encrypt"/>
> 
> Then transaction runs successfully.  So it seems that
> this problem is limited in scope to the digital sig
> processing.
> 
> Thanks,
> 
> Shawn
> 


-- 
Davanum Srinivas -http://blogs.cocoondev.org/dims/