Django should have OpenID implemented in django.contrib.auth

[dev@…]

​OpenID is cool, & it would be nice if Django could support it out of the box. There's a ​cookbook recipe available but this could be folded into django.contrib.auth to make it all much easier.

[anonymous]

+1 on this!

[John D'Agostino <john.dagostino@…>]

I'm +1 on this too, the only issue i see is that ​python library is released under LGPL, which is incompatible with the BSD license which Django is released under. One solution i see to this is to do the same thing which is currently done with the database backends - ship the module (django.contrib.auth.openid) and require the developer to download the required library.

[ikke@…]

I implemented a store for the Python OpenID library more Django-style (using some Django models, and a Store interface implementation around it) for my Django-based OpenID server. Currently this is GPL-licensed, I could relicense this though if you guys 'd want to use it.

The server is at ​http://svn.nicolast.be/djangoid/

[djangonaut#378]

If django 1.0 could have OpenID, it would do great wonders for django's popularity as a platform.

[byteflood@…]

I am +1 as well. Looks like the same plan a that used for the database backends in the best plan for integration.

[smurf@…]

+1 from me too.

If nothing else, I want all Django sites out there to be able to do OpenID so that I don't need to store or remember another heap of random passwords. ;-)
(And enabling the same on my own blog would be a nice benefit.)

[.jon]

+1

OpenID needs to gain momentum. I would love to have it in Django.

[James Bennett]

Please remember that a solid implementation in code gets far more attention than "+1 from me too" comments in tickets ;)

[Simon G. <dev@…>]

Simon Willison has an ​implementation here

[Sung-Jin Hong <serialx.net@…>]

Why close the ticket? It's about whether to include openid support in django or not. Not about whether there is an implementation or not.

[Simon G. <dev@…>]

I closed the ticket as Simon Willison's implementation works well and just plugs into Django easily. There's no need for Django to maintain this, since this looks like it'll be a fairly robust project on its own. In short: I'm happy with this. However, if you do want this moved into Django, then it's best to raise this issue in the developers group.

[mcroydon]

Reclosing this. Use ​django-openid for OpenID functionality in Django. If you feel strongly that it should be folded in to a django.contrib app, please raise the issue on django-developers.

[Chris Hager]

Replying to mcroydon:

Reclosing this. Use ​django-openid for OpenID functionality in Django. If you feel strongly that it should be folded in to a django.contrib app, please raise the issue on django-developers.

django-openid is probably not the best solution, since the project supports only python-openid-1.2, which prevents using 2.0 provider like yahoo, ... for me the best way to get openid 2.x running with django is ​django-authopenid. it has excellent django-examples which work out of the box.

i've tried most of the openid projects and it seems django-authopenid is the only way to get python-openid-2.x running. i summarized my progress ​here.

[Jari Pennanen]

django-authopenid has lost it's maintainer, duh... this is what happens if it is not part of the contribs, there is no motivation to try to keep up with Django.

[amanjsingh]

are we going to get this OpenID implementation in django.contrib.auth?

[Luke Plant]

Replying to amanjsingh:

are we going to get this OpenID implementation in django.contrib.auth?

As stated before, please stop re-opening. Bring this up as a solid proposal on django-developers. Also, look up the definition of django-contrib ​http://jacobian.org/writing/what-is-django-contrib/ - based on the comments above, there isn't one solid implementation or de-facto standard.