<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: RSS and Authentication</title>
	<atom:link href="http://www.rassoc.com/gregr/weblog/2003/08/10/rss-and-authentication/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rassoc.com/gregr/weblog/2003/08/10/rss-and-authentication/</link>
	<description>Musings on just about everything.</description>
	<pubDate>Thu, 28 Aug 2008 04:04:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Vitriol &#187; Blackboard Secure RSS</title>
		<link>http://www.rassoc.com/gregr/weblog/2003/08/10/rss-and-authentication/#comment-746</link>
		<dc:creator>Vitriol &#187; Blackboard Secure RSS</dc:creator>
		<pubDate>Wed, 04 Oct 2006 11:16:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.gregrphoto.com/rassoc/gregr/weblog/2003/08/10/rss-and-authentication/#comment-746</guid>
		<description>Pingback
</description>
		<content:encoded><![CDATA[<p>Pingback</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quickfinch: The Blog</title>
		<link>http://www.rassoc.com/gregr/weblog/2003/08/10/rss-and-authentication/#comment-745</link>
		<dc:creator>Quickfinch: The Blog</dc:creator>
		<pubDate>Wed, 24 May 2006 03:59:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.gregrphoto.com/rassoc/gregr/weblog/2003/08/10/rss-and-authentication/#comment-745</guid>
		<description>Pingback
</description>
		<content:encoded><![CDATA[<p>Pingback</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Reinacker</title>
		<link>http://www.rassoc.com/gregr/weblog/2003/08/10/rss-and-authentication/#comment-744</link>
		<dc:creator>Greg Reinacker</dc:creator>
		<pubDate>Thu, 02 Sep 2004 05:50:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.gregrphoto.com/rassoc/gregr/weblog/2003/08/10/rss-and-authentication/#comment-744</guid>
		<description>Steve, shoot a note over to support at newsgator.com with what you're seeing, and we'll be able to get you fixed up.
</description>
		<content:encoded><![CDATA[<p>Steve, shoot a note over to support at newsgator.com with what you&#8217;re seeing, and we&#8217;ll be able to get you fixed up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://www.rassoc.com/gregr/weblog/2003/08/10/rss-and-authentication/#comment-743</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Wed, 01 Sep 2004 20:00:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.gregrphoto.com/rassoc/gregr/weblog/2003/08/10/rss-and-authentication/#comment-743</guid>
		<description>I use newsgator and setup autheticated access to by blog, blogware hosted.  This has secure categories.  When I access, (authenticated), using the browser everything is fine, I see &lt;br&gt;&lt;br&gt;http://steves.businessblog.com/blog/Secure/AlternativeDesktop/index.xml&lt;br&gt;&lt;br&gt;when I access via newsgator I see&lt;br&gt;&lt;br&gt;http://steves.businessblog.com/blog/index.xml&lt;br&gt;&lt;br&gt;which implies my credentials are not being provided.
</description>
		<content:encoded><![CDATA[<p>I use newsgator and setup autheticated access to by blog, blogware hosted.  This has secure categories.  When I access, (authenticated), using the browser everything is fine, I see </p>
<p><a href="http://steves.businessblog.com/blog/Secure/AlternativeDesktop/index.xml" rel="nofollow">http://steves.businessblog.com/blog/Secure/AlternativeDesktop/index.xml</a></p>
<p>when I access via newsgator I see</p>
<p><a href="http://steves.businessblog.com/blog/index.xml" rel="nofollow">http://steves.businessblog.com/blog/index.xml</a></p>
<p>which implies my credentials are not being provided.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill French</title>
		<link>http://www.rassoc.com/gregr/weblog/2003/08/10/rss-and-authentication/#comment-742</link>
		<dc:creator>Bill French</dc:creator>
		<pubDate>Sun, 17 Aug 2003 20:25:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.gregrphoto.com/rassoc/gregr/weblog/2003/08/10/rss-and-authentication/#comment-742</guid>
		<description>Erik raises an important issue that's a bit deeper than most people realize. Using HTTP authentication is but one dimension of a complex requirement.&lt;br&gt;&lt;br&gt;In our experience, enterprises are asking for RSS to be delivered in a security context, not just securely. What this means is that given a specific individuals permissions, what items in an RSS feed are they able to see and/or read. This is very similar to search within a security context - where just the _knowing_ that there is a document in the system entitled "Layoff's 2003" is in fact a security violation even though the user couldn't read it.&lt;br&gt;&lt;br&gt;When it comes to the simple act of blogging in a secure manner, we have already experienced requests for single blogs (channels) to publish items based on user permissions. In fact, I use this model to blog to 15 consulting clients, each of which see a secure collection of content that is targeted specifically for their interests but is accomplished in one weblog (channel). There are many benefits to this approach - one is the ability to reuse some items on multiple clients without any additional effort.&lt;br&gt;&lt;br&gt;RSS is about to face some stringent tests as enterprises launch blog initiatives, and the engines that generate the feeds will have to come up to speed in terms of a granular (object/item-level) permissions model. The MyST platform already provides this (and much more for larger businesses). ;-)&lt;br&gt;&lt;br&gt;bf
</description>
		<content:encoded><![CDATA[<p>Erik raises an important issue that&#8217;s a bit deeper than most people realize. Using HTTP authentication is but one dimension of a complex requirement.</p>
<p>In our experience, enterprises are asking for RSS to be delivered in a security context, not just securely. What this means is that given a specific individuals permissions, what items in an RSS feed are they able to see and/or read. This is very similar to search within a security context - where just the _knowing_ that there is a document in the system entitled &#8220;Layoff&#8217;s 2003&#8243; is in fact a security violation even though the user couldn&#8217;t read it.</p>
<p>When it comes to the simple act of blogging in a secure manner, we have already experienced requests for single blogs (channels) to publish items based on user permissions. In fact, I use this model to blog to 15 consulting clients, each of which see a secure collection of content that is targeted specifically for their interests but is accomplished in one weblog (channel). There are many benefits to this approach - one is the ability to reuse some items on multiple clients without any additional effort.</p>
<p>RSS is about to face some stringent tests as enterprises launch blog initiatives, and the engines that generate the feeds will have to come up to speed in terms of a granular (object/item-level) permissions model. The MyST platform already provides this (and much more for larger businesses). ;-)</p>
<p>bf</p>
]]></content:encoded>
	</item>
</channel>
</rss>
