django-facebook-auth
A stable Facebook authentication backend for Django >= 1.4.
Starting from version 3.6.0 Django 1.7 is supported. South migrations are move to south_migrations so you need South 1.0 or newer to use them.
Requires Celery for background token operations.
Installation
Package
django-facebook-auth can be installed as a normal Python package.
Example installation for pip:
$ pip install django-facebook-auth
Configuration
Celery
This project requires working Celery integration. In case you are new to Celery, the First steps with Django tutorial will help you to hit the ground running.
settings.py
Set USE_TZ = True
Add facebook_auth to INSTALLED_APPS:
INSTALLED_APPS = (
...
'facebook_auth',
...
)
Add authentication backends to AUTHENTICATION_BACKENDS:
AUTHENTICATION_BACKENDS = (
...
'facebook_auth.backends.FacebookBackend',
'facebook_auth.backends.FacebookJavascriptBackend',
...
)
Set necessary Facebook properties:
FACEBOOK_CANVAS_URL = 'http://pozytywnie.pl/' # root of your domain FACEBOOK_APP_ID = '1234567890' FACEBOOK_APP_SECRET = '91162629d258a876ee994e9233b2ad87'
Usage
The authentication flow is very straightforward:
Redirect your user to Facebook OAuth endpoint using redirect_uri prepared with the help of this library.
First in your view or context processor prepare the necessary parameters for the Facebook OAuth endpoint:
from facebook_auth.urls import redirect_uri def login(request): ... context.update({ 'redirect_uri': redirect_uri('/login/success', '/login/fail'), 'client_id': settings.FACEBOOK_APP_ID, 'scope': 'email' }) ...And embed the link in your template:
<a href="https://www.facebook.com/dialog/oauth?client_id={{ client_id }}&scope={{ scope }}&redirect_uri={{ redirect_uri }}">Login using Facebook</a>User is redirected back to django-facebook-auth authentication handler, which either authenticates the user or refuses to do so.
Prepare a separate view for each scenario.
A best token for authenticated user is negotiated with Facebook in the background, using your Celery worker.
2 maintainers
Metadata
2 maintainers
Release files for django-facebook-auth 3.9.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django-facebook-auth-3.9.0.tar.gz | 18.2 kB | Without provenance | Details |
Release files / django-facebook-auth-3.9.0.tar.gz
| Download URL | django-facebook-auth-3.9.0.tar.gz |
|---|---|
| Size | 18.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
37908818a1fc3603ef0bacb20ed8ae8b2098d4ff07bcd1bfd38079dfdc05b72c
|
|
BLAKE2b-256 checksum How to use checksums |
99977934758993c08e3bfbbc791b0d548a37282ede69f9659c6f5f53446891a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-facebook-auth 3.9.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
