<?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: django-openid-auth</title>
	<atom:link href="http://blogs.gnome.org/jamesh/2009/04/14/django-openid-auth/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/jamesh/2009/04/14/django-openid-auth/</link>
	<description>Random stuff</description>
	<lastBuildDate>Wed, 28 Oct 2009 02:53:32 +0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Peter Robinett</title>
		<link>http://blogs.gnome.org/jamesh/2009/04/14/django-openid-auth/comment-page-1/#comment-809</link>
		<dc:creator>Peter Robinett</dc:creator>
		<pubDate>Sun, 10 May 2009 09:59:46 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/jamesh/?p=426#comment-809</guid>
		<description>Has anyone gotten this to work with App Engine and Django 1.0? I&#039;d love to use it for my project but I&#039;m getting the following error:
ViewDoesNotExist: Could not import django_openid_auth.views. Error was: No module named contenttypes.models

This is peculiar because I don&#039;t see any reference to contenttypes except in settings.py. I&#039;m using google-app-engine-django and contenttypes is commented out, though uncommenting it doesn&#039;t help (you can see my whole process here: http://www.bubblefoundry.com/blog/2009/05/installing-the-google-app-engine-sdk-and-django-102/). As you can tell, I&#039;m quite new to Django and App Engine, so any help would be appreciated.

Peter</description>
		<content:encoded><![CDATA[<p>Has anyone gotten this to work with App Engine and Django 1.0? I&#8217;d love to use it for my project but I&#8217;m getting the following error:<br />
ViewDoesNotExist: Could not import django_openid_auth.views. Error was: No module named contenttypes.models</p>
<p>This is peculiar because I don&#8217;t see any reference to contenttypes except in settings.py. I&#8217;m using google-app-engine-django and contenttypes is commented out, though uncommenting it doesn&#8217;t help (you can see my whole process here: <a href="http://www.bubblefoundry.com/blog/2009/05/installing-the-google-app-engine-sdk-and-django-102/)" rel="nofollow">http://www.bubblefoundry.com/blog/2009/05/installing-the-google-app-engine-sdk-and-django-102/)</a>. As you can tell, I&#8217;m quite new to Django and App Engine, so any help would be appreciated.</p>
<p>Peter</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Henstridge</title>
		<link>http://blogs.gnome.org/jamesh/2009/04/14/django-openid-auth/comment-page-1/#comment-806</link>
		<dc:creator>James Henstridge</dc:creator>
		<pubDate>Tue, 28 Apr 2009 10:09:45 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/jamesh/?p=426#comment-806</guid>
		<description>Faruk: that column should indeed be unique -- each identity URL must only be associated with a single user.  As I mentioned above, the column should probably be changed to CharField with an appropriate length for MySQL compatibility.

Aaron: django-openid-auth already supports querying the openid provider for a full name, nickname and email address using the simple registration extension.  It uses these when creating new django.contrib.auth User objects.  As there is already space in the User object to store them, it doesn&#039;t use a profile model.</description>
		<content:encoded><![CDATA[<p>Faruk: that column should indeed be unique &#8212; each identity URL must only be associated with a single user.  As I mentioned above, the column should probably be changed to CharField with an appropriate length for MySQL compatibility.</p>
<p>Aaron: django-openid-auth already supports querying the openid provider for a full name, nickname and email address using the simple registration extension.  It uses these when creating new django.contrib.auth User objects.  As there is already space in the User object to store them, it doesn&#8217;t use a profile model.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://blogs.gnome.org/jamesh/2009/04/14/django-openid-auth/comment-page-1/#comment-804</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Mon, 27 Apr 2009 00:55:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/jamesh/?p=426#comment-804</guid>
		<description>Thanks for the great app. I and was unclear what the best way is to deal with user information like a username, email address, etc for an openid user. Should I just follow http://docs.djangoproject.com/en/dev/topics/auth/#storing-additional-information-about-users and add a profile model? If so, should that model be foreignkeyed to django_openid_auth.openiduser?

Also, is there a way to get extended information like a username from the openid provider?</description>
		<content:encoded><![CDATA[<p>Thanks for the great app. I and was unclear what the best way is to deal with user information like a username, email address, etc for an openid user. Should I just follow <a href="http://docs.djangoproject.com/en/dev/topics/auth/#storing-additional-information-about-users" rel="nofollow">http://docs.djangoproject.com/en/dev/topics/auth/#storing-additional-information-about-users</a> and add a profile model? If so, should that model be foreignkeyed to django_openid_auth.openiduser?</p>
<p>Also, is there a way to get extended information like a username from the openid provider?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Faruk Akgul</title>
		<link>http://blogs.gnome.org/jamesh/2009/04/14/django-openid-auth/comment-page-1/#comment-803</link>
		<dc:creator>Faruk Akgul</dc:creator>
		<pubDate>Sun, 19 Apr 2009 05:20:57 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/jamesh/?p=426#comment-803</guid>
		<description>@Ivan: It&#039;s Django&#039;s fault actually. You need to open django_openid_auth/models.py file and remove unique=True from the claim_id which is in the UserOpenID class, then sync. After that you need ALTER TABLE to create the proper index, then add unique=True option again in the file. Hope this helps.

Cheers,
Faruk</description>
		<content:encoded><![CDATA[<p>@<a href="http://blogs.gnome.org/jamesh/2009/04/14/django-openid-auth/#comment-800">Ivan</a>: It&#8217;s Django&#8217;s fault actually. You need to open django_openid_auth/models.py file and remove unique=True from the claim_id which is in the UserOpenID class, then sync. After that you need ALTER TABLE to create the proper index, then add unique=True option again in the file. Hope this helps.</p>
<p>Cheers,<br />
Faruk</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Henstridge</title>
		<link>http://blogs.gnome.org/jamesh/2009/04/14/django-openid-auth/comment-page-1/#comment-802</link>
		<dc:creator>James Henstridge</dc:creator>
		<pubDate>Wed, 15 Apr 2009 09:47:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/jamesh/?p=426#comment-802</guid>
		<description>Ivan: I can&#039;t say I tested it on MySQL: the test suite is against SQLite, and the only other database we use it against is PostgreSQL.

You could try editing django_openid_auth/models.py and changing the claimed_id definition to a CharField with a shorter maximum length.  If that works for you, please file a bug report in Launchpad.</description>
		<content:encoded><![CDATA[<p>Ivan: I can&#8217;t say I tested it on MySQL: the test suite is against SQLite, and the only other database we use it against is PostgreSQL.</p>
<p>You could try editing django_openid_auth/models.py and changing the claimed_id definition to a CharField with a shorter maximum length.  If that works for you, please file a bug report in Launchpad.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Turner</title>
		<link>http://blogs.gnome.org/jamesh/2009/04/14/django-openid-auth/comment-page-1/#comment-801</link>
		<dc:creator>Kevin Turner</dc:creator>
		<pubDate>Wed, 15 Apr 2009 07:27:07 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/jamesh/?p=426#comment-801</guid>
		<description>Looks like the known issues in the googleappengine relating to python-openid have been fixed in the last few months (i.e. issue #404).  So it should work!</description>
		<content:encoded><![CDATA[<p>Looks like the known issues in the googleappengine relating to python-openid have been fixed in the last few months (i.e. issue #404).  So it should work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ivan</title>
		<link>http://blogs.gnome.org/jamesh/2009/04/14/django-openid-auth/comment-page-1/#comment-800</link>
		<dc:creator>Ivan</dc:creator>
		<pubDate>Wed, 15 Apr 2009 07:18:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/jamesh/?p=426#comment-800</guid>
		<description>Hi,

I was looking for an OpenID library to use in our Django application but when I run &quot;python manage.py syncdb&quot; I receive the following error. Am I missing something?

Creating table django_openid_auth_useropenid

_mysql_exceptions.OperationalError: (1170, &quot;BLOB/TEXT column &#039;claimed_id&#039; used in key specification without a key length&quot;)</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I was looking for an OpenID library to use in our Django application but when I run &#8220;python manage.py syncdb&#8221; I receive the following error. Am I missing something?</p>
<p>Creating table django_openid_auth_useropenid</p>
<p>_mysql_exceptions.OperationalError: (1170, &#8220;BLOB/TEXT column &#8216;claimed_id&#8217; used in key specification without a key length&#8221;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Henstridge</title>
		<link>http://blogs.gnome.org/jamesh/2009/04/14/django-openid-auth/comment-page-1/#comment-799</link>
		<dc:creator>James Henstridge</dc:creator>
		<pubDate>Tue, 14 Apr 2009 15:47:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/jamesh/?p=426#comment-799</guid>
		<description>Marius: I don&#039;t think there is any code in django-openid-auth that would be a problem.  However, it is built on top of Jan Rain&#039;s python-openid which is more likely to have compatibility problems.

At a minimum, you might need to provide a custom URLFetcher class that uses the appengine HTTP API.  It is possible that someone has already done this work though, so you might want to google it.</description>
		<content:encoded><![CDATA[<p>Marius: I don&#8217;t think there is any code in django-openid-auth that would be a problem.  However, it is built on top of Jan Rain&#8217;s python-openid which is more likely to have compatibility problems.</p>
<p>At a minimum, you might need to provide a custom URLFetcher class that uses the appengine HTTP API.  It is possible that someone has already done this work though, so you might want to google it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marius Scurtescu</title>
		<link>http://blogs.gnome.org/jamesh/2009/04/14/django-openid-auth/comment-page-1/#comment-798</link>
		<dc:creator>Marius Scurtescu</dc:creator>
		<pubDate>Tue, 14 Apr 2009 15:10:43 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/jamesh/?p=426#comment-798</guid>
		<description>Would this also work with Google App Engine?</description>
		<content:encoded><![CDATA[<p>Would this also work with Google App Engine?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Henstridge</title>
		<link>http://blogs.gnome.org/jamesh/2009/04/14/django-openid-auth/comment-page-1/#comment-797</link>
		<dc:creator>James Henstridge</dc:creator>
		<pubDate>Tue, 14 Apr 2009 14:35:47 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/jamesh/?p=426#comment-797</guid>
		<description>Launchpad is not a Django application -- it is built on top of Zope 3 and Storm.

Some of the non-internal projects we&#039;ve got using Django include summit.ubuntu.com and paste.ubuntu.com.</description>
		<content:encoded><![CDATA[<p>Launchpad is not a Django application &#8212; it is built on top of Zope 3 and Storm.</p>
<p>Some of the non-internal projects we&#8217;ve got using Django include summit.ubuntu.com and paste.ubuntu.com.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
