<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Andrew McFague</title>
	<atom:link href="http://www.andrew-mcfague.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.andrew-mcfague.com</link>
	<description>Programming in Brooklyn</description>
	<lastBuildDate>Sat, 16 Jul 2011 00:23:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Repoze.who: Part 1 &#8211; Using authentication in your site by Andrew</title>
		<link>http://www.andrew-mcfague.com/python/repoze-who-part-1-using-authentication-in-your-site/comment-page-1/#comment-118</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Sat, 16 Jul 2011 00:23:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.andrew-mcfague.com/?p=86#comment-118</guid>
		<description>This is actually not entirely True, because the middleware itself uses a &lt;code&gt;401&lt;/code&gt; error code to determine whether or not it needs to issue a request.  For example, you&#039;ll notice that the &lt;code&gt;authenticated&lt;/code&gt; decorator aborts with a 401--this NEEDS to be caught by the repoze.who middleware, otherwise the error page will always be displayed if you haven&#039;t logged in.

However, one alternative is to force the error handling middleware to ignore the 401 error--by removing it from the list of status codes the error handler will catch.  If the repoze.who middleware tries to authenticate but cannot, then the 403 (or other) should trickle up to the error handling middleware.

I&#039;ll have to do some testing myself to verify that this is 100% correct, but that&#039;s what my understanding is.</description>
		<content:encoded><![CDATA[<p>This is actually not entirely True, because the middleware itself uses a <code>401</code> error code to determine whether or not it needs to issue a request.  For example, you&#8217;ll notice that the <code>authenticated</code> decorator aborts with a 401&#8211;this NEEDS to be caught by the repoze.who middleware, otherwise the error page will always be displayed if you haven&#8217;t logged in.</p>
<p>However, one alternative is to force the error handling middleware to ignore the 401 error&#8211;by removing it from the list of status codes the error handler will catch.  If the repoze.who middleware tries to authenticate but cannot, then the 403 (or other) should trickle up to the error handling middleware.</p>
<p>I&#8217;ll have to do some testing myself to verify that this is 100% correct, but that&#8217;s what my understanding is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Repoze.who: Part 1 &#8211; Using authentication in your site by Vincent</title>
		<link>http://www.andrew-mcfague.com/python/repoze-who-part-1-using-authentication-in-your-site/comment-page-1/#comment-117</link>
		<dc:creator>Vincent</dc:creator>
		<pubDate>Fri, 15 Jul 2011 21:35:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.andrew-mcfague.com/?p=86#comment-117</guid>
		<description>Great article! I definitely agree that the current repoze.who and repoze.what documentation is way too sparse for Pylons. I appreciate the write-up!

However, it is my understanding that the middleware setup for repoze.who needs to be done BEFORE the &lt;code&gt;if asbool(full_stack):&lt;/code&gt;. This is because repoze.who will throw an exception along with an error code, for instance, when a user fails to authenticate. The error is then passed to the StatusCodeRedirect function which then gets passed on to your applications custom error handling controller in &lt;strong&gt;controllers/error.py&lt;/strong&gt;. This is what allows the developer to customize different error actions for the application.</description>
		<content:encoded><![CDATA[<p>Great article! I definitely agree that the current repoze.who and repoze.what documentation is way too sparse for Pylons. I appreciate the write-up!</p>
<p>However, it is my understanding that the middleware setup for repoze.who needs to be done BEFORE the <code>if asbool(full_stack):</code>. This is because repoze.who will throw an exception along with an error code, for instance, when a user fails to authenticate. The error is then passed to the StatusCodeRedirect function which then gets passed on to your applications custom error handling controller in <strong>controllers/error.py</strong>. This is what allows the developer to customize different error actions for the application.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Repoze.who: Part 1 &#8211; Using authentication in your site by Andrew</title>
		<link>http://www.andrew-mcfague.com/python/repoze-who-part-1-using-authentication-in-your-site/comment-page-1/#comment-115</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Mon, 09 May 2011 17:31:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.andrew-mcfague.com/?p=86#comment-115</guid>
		<description>The answer as to whether or not you can is probably `yes`. But as for how, I’m not really sure–mostly because I have no idea how the Apache webauth module works.

However, I am currently drafting my next article, which is how to extend the functionality by writing your own plug-in. Since you seem to be familiar with the webauth module, I feel fairly certain you could write your own module to add this functionality.

Does that sound good? I might be able to provide more immediate support, but I think waiting on the next article is definitely your best bet. :)

Andrew</description>
		<content:encoded><![CDATA[<p>The answer as to whether or not you can is probably `yes`. But as for how, I’m not really sure–mostly because I have no idea how the Apache webauth module works.</p>
<p>However, I am currently drafting my next article, which is how to extend the functionality by writing your own plug-in. Since you seem to be familiar with the webauth module, I feel fairly certain you could write your own module to add this functionality.</p>
<p>Does that sound good? I might be able to provide more immediate support, but I think waiting on the next article is definitely your best bet. :)</p>
<p>Andrew</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Repoze.who: Part 1 &#8211; Using authentication in your site by Anusha Ranganathan</title>
		<link>http://www.andrew-mcfague.com/python/repoze-who-part-1-using-authentication-in-your-site/comment-page-1/#comment-113</link>
		<dc:creator>Anusha Ranganathan</dc:creator>
		<pubDate>Mon, 09 May 2011 13:57:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.andrew-mcfague.com/?p=86#comment-113</guid>
		<description>Hello Andrew,
Thanks for the post. I have pylons / repoze working with htpasswd but need to have it working with SSO. Would you be able to provide any insight on how to achieve this? I need to integrate repoze with Apache&#039;s webauth module.

Any help would be much appreciated.

Regards,
Anusha</description>
		<content:encoded><![CDATA[<p>Hello Andrew,<br />
Thanks for the post. I have pylons / repoze working with htpasswd but need to have it working with SSO. Would you be able to provide any insight on how to achieve this? I need to integrate repoze with Apache&#8217;s webauth module.</p>
<p>Any help would be much appreciated.</p>
<p>Regards,<br />
Anusha</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on tmux: a screen alternative by Jim A</title>
		<link>http://www.andrew-mcfague.com/linux/utilities-linux/tmux-a-screen-alternative/comment-page-1/#comment-94</link>
		<dc:creator>Jim A</dc:creator>
		<pubDate>Fri, 21 Jan 2011 17:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://redmumba.wordpress.com/?p=16#comment-94</guid>
		<description>great intro, thanks!</description>
		<content:encoded><![CDATA[<p>great intro, thanks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Database Caching 3/14 queries in 0.072 seconds using disk: basic
Object Caching 520/528 objects using disk: basic

Served from: www.andrew-mcfague.com @ 2012-02-22 20:58:01 -->
