omab/django-social-auth — Issue #178: Anyone using django-social-auth with Pinax?
Author: dimebagdai
Created: 2011-11-14 05:20:50+00:00
State: open

I'm developing a website using Pinax and tried using django-social-auth to build Facebook and Google authentication and was wondering if the setup is supported and if any folks here have tried it.

I followed the installation and config instructions and created a sample signup page using the django-social-auth demo. But when I click on the link to login with Facebook, I get the following error. I am stumped as to what the problem really is.

https://www.facebook.com/dialog/oauth?redirect_uri=http%3A%2F%2Fssnews.com%2Fsocial%2Fcomplete%2Ffacebook%2F&client_id=################

Error
An error occurred with ssnews. Please try again later.

Also, when I try to use the Facebook registration plugin for signup, I hit the following error. Any insights will be highly appreciated.

Forbidden (403)
CSRF verification failed. Request aborted.
Help
Reason given for failure:
CSRF token missing or incorrect.

In general, this can occur when there is a genuine Cross Site Request Forgery, or when Django's CSRF mechanism has not been used correctly. For POST forms, you need to ensure:
The view function uses RequestContext for the template, instead of Context.
In the template, there is a {% csrf_token %} template tag inside each POST form that targets an internal URL.
If you are not using CsrfViewMiddleware, then you must use csrf_protect on any views that use the csrf_token template tag, as well as those that accept the POST data.
You're seeing the help section of this page because you have DEBUG = True in your Django settings file. Change that to False, and only the initial error message will be displayed.
You can customize this page using the CSRF_FAILURE_VIEW setting.