[Home] [By Thread] [By Date] [Recent Entries]


> So each message, no matter the size, should be parsed to determine 
> authorization, authentication and validity? As opposed to 
> stopping/redirecting a request based on the URL/request-credentials 
> before a parse happens?

Should be?  Even I'd be reluctant to use something other than "may."
If your gateway facility is fast enough to handle the traffic, than you 
can get significant performance gains by offloading stuff like you 
mention from your application servers.  A J2EE server is not usually the 
most performant place to do a WS-Security signature validation.

There are security benefits, too.  Put the router into your DMZ and you 
prevent bad messages from even getting onto your network.  Pass all XML 
traffic through it and you have a guaranteed policy enforcement point.

But definitely, not everyone needs or wants to do this.  It's all about 
engineering trade-offs.

	/r$

-- 
Rich Salz, Chief Security Architect
DataPower Technology                           http://www.datapower.com
XS40 XML Security Gateway   http://www.datapower.com/products/xs40.html

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member