• Feeds

    Subscribe in a reader

  • Ads

Securely navigating SOAP intermediaries with WSE 2.0

Mr. Tay (Softwaremaker) has tackled the rather sticky problem of securely traversing mutliple SOAP intermediaries and come up with this article over on MSDN. There's a lot of good stuff to dig into here.

The scenario William came up with reminded me of a few customer projects we had going on at Avanade before I left. We were starting to see customers interested in factoring out things like authentication and authorization into separate services that operated pretty much how William described it. Customers are definitely starting to look at multi-hop message paths -- with that in mind, you can see why Indigo puts such a focus on the end-to-end picture when it comes to things like security and reliability.

It will be fun to watch these types of scenarios evolve in the future. An open question to William: what does this scenario look like on the Indigo CTP bits?

 

#1 WilliamT on 3.18.2005 at 2:53 AM

From my blog post here: http://www.softwaremaker.net/blog/PermaLink,guid,efeecf7b-a2bc-45bc-8e71-3f16e586ce15.aspx[Quote]While this architectural setup may come across as 'complicated' and slightly 'unorthodox' in the real world today, I believe we will see more and more setups of this model as we go along with the wide-acceptance of (standards-based) messaging-based systems in the enterprise mainstream. Key-word here is standards-based. Another thing that I believe will happen with Service-Orientation is that this routing/gateway style approach will become the primary extensibility model. [UnQuote]I believe your ex-customers are also adopting this approach....The Open Question ? Stay tuned...I am in the midst of ripping Indigo-bits apart ;)