<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for karl_mcguinness</title><link>http://disqus.com/by/karl_mcguinness/</link><description></description><atom:link href="http://disqus.com/karl_mcguinness/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Sun, 07 Sep 2008 11:13:54 -0000</lastBuildDate><item><title>Re: Flowing Identity from a Client to a Service when using RESTful WCF Part 2 &amp;#8211; A Solution</title><link>http://www.thefreakparade.com/2008/09/flowing-identity-from-a-client-to-a-service-when-using-restful-wcf-part-2-a-solution/#comment-2212475</link><description>&lt;p&gt;Good to see other folks doing the same thing.  We just finished prototyping a similar approach.  Instead of using custom headers, have you thought about using WS-Security Token Profiles over HTTP headers so that you can leverage the existing profiles and library support?  (see &lt;a href="http://www.xml.com/pub/a/2003/12/17/dive.html)" rel="nofollow noopener" target="_blank" title="http://www.xml.com/pub/a/2003/12/17/dive.html)"&gt;http://www.xml.com/pub/a/20...&lt;/a&gt; . WS-Security has a standard profile for SAML tokens so you can also use this approach to normalize your SOAP and REST strategies in WCF.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">karl_mcguinness</dc:creator><pubDate>Sun, 07 Sep 2008 11:13:54 -0000</pubDate></item></channel></rss>