<?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 on: Using OpenID with your Django site</title>
	<atom:link href="http://www.rhonabwy.com/wp/2007/04/23/using-openid-with-your-django-site/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rhonabwy.com/wp/2007/04/23/using-openid-with-your-django-site/</link>
	<description>Mac, iOS, DevOps, and daily life in Seattle</description>
	<lastBuildDate>Fri, 25 Nov 2011 06:40:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: David Cramer</title>
		<link>http://www.rhonabwy.com/wp/2007/04/23/using-openid-with-your-django-site/comment-page-1/#comment-14283</link>
		<dc:creator>David Cramer</dc:creator>
		<pubDate>Tue, 24 Apr 2007 21:01:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.rhonabwy.com/wp/2007/04/23/using-openid-with-your-django-site/#comment-14283</guid>
		<description>The talk was pretty good, it filled in some gaps for me about OpenID. We used the examples from the actual library and were able to get it working for us. We added a field to the users table &quot;openid_key&quot; and made username/password optional. It then requires either openid_key to be set, or username/password to be set. When they log in with their openid key and do not have a username set we force them to choose a unique username.</description>
		<content:encoded><![CDATA[<p>The talk was pretty good, it filled in some gaps for me about OpenID. We used the examples from the actual library and were able to get it working for us. We added a field to the users table &#8220;openid_key&#8221; and made username/password optional. It then requires either openid_key to be set, or username/password to be set. When they log in with their openid key and do not have a username set we force them to choose a unique username.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Willison</title>
		<link>http://www.rhonabwy.com/wp/2007/04/23/using-openid-with-your-django-site/comment-page-1/#comment-14124</link>
		<dc:creator>Simon Willison</dc:creator>
		<pubDate>Tue, 24 Apr 2007 05:27:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.rhonabwy.com/wp/2007/04/23/using-openid-with-your-django-site/#comment-14124</guid>
		<description>Thanks for the write-up - I agonised over the details of that package for far too long, so it&#039;s great to see that they are appreciated. I actually deliberately avoided including obvious support for sreg required v.s. sreg optional precisely because I&#039;ve seen that distinction cause trouble for sites like TrenchMice in the past. I&#039;ve got a few ideas for ways to get contrib.auth integration in, possibly including co-operation with James Bennett&#039;s django-registration package.</description>
		<content:encoded><![CDATA[<p>Thanks for the write-up &#8211; I agonised over the details of that package for far too long, so it&#8217;s great to see that they are appreciated. I actually deliberately avoided including obvious support for sreg required v.s. sreg optional precisely because I&#8217;ve seen that distinction cause trouble for sites like TrenchMice in the past. I&#8217;ve got a few ideas for ways to get contrib.auth integration in, possibly including co-operation with James Bennett&#8217;s django-registration package.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

