/usr/share/doc/python-social-auth-doc/html/_sources/configuration/porting_from_dsa.txt is in python-social-auth-doc 1:0.2.21+dfsg-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 | Porting from django-social-auth
===============================
Being a derivative work from django-social-auth_, porting from it to
python-social-auth_ should be an easy task. Porting to others libraries usually
is a pain, I'm trying to make this as easy as possible.
Installed apps
--------------
On django-social-auth_ there was a single application to add into
``INSTALLED_APPS`` plus a setting to define which ORM to be used (default or
MongoEngine). Now the apps are split and there's not need for that extra
setting.
When using the default ORM::
INSTALLED_APPS = (
...
'social.apps.django_app.default',
...
)
And when using MongoEngine::
INSTALLED_APPS = (
...
'social.apps.django_app.me',
...
)
The models table names were defined to be compatible with those used on
django-social-auth_, so data is not needed to be migrated.
URLs
----
The URLs are namespaced, you can chose your namespace, the `example app`_ uses
the ``social`` namespace. Replace the old include with::
urlpatterns = patterns('',
...
url('', include('social.apps.django_app.urls', namespace='social'))
...
)
On templates use a namespaced URL::
{% url 'social:begin' "google-oauth2" %}
Account disconnection URL would be::
{% url 'social:disconnect_individual' provider, id %}
Porting settings
----------------
All python-social-auth_ settings are prefixed with ``SOCIAL_AUTH_``, except for
some exception on Django framework, ``AUTHENTICATION_BACKENDS`` remains the
same for obvious reasons.
All backends settings have the backend name into it, all uppercase and with
dashes replaced with underscores, take for instance Google OAuth2 backend is
named ``google-oauth2``, any setting name related to that backend should start
with ``SOCIAL_AUTH_GOOGLE_OAUTH2_``.
Keys and secrets are some mandatory settings needed for OAuth providers, to
keep consistency the names follow the same naming convention ``*_KEY`` for the
application key, and ``*_SECRET`` for the secret. OAuth1 backends use to have
``CONSUMER`` in the setting name, not anymore. Following with the Google OAuth2
example::
SOCIAL_AUTH_GOOGLE_OAUTH2_KEY = '...'
SOCIAL_AUTH_GOOGLE_OAUTH2_SECRET = '...'
Remember that the name of the backend is needed in the settings, and names
differ a little from backend to backend, like `Facebook OAuth2 backend`_ name
is ``facebook``. So the settings should be::
SOCIAL_AUTH_FACEBOOK_KEY = '...'
SOCIAL_AUTH_FACEBOOK_SECRET = '...'
Authentication backends
-----------------------
Import path for authentication backends changed a little, there's no more
``contrib`` module, there's no need for it. Some backends changed the names to
have some consistency, check the backends, it should be easy to track the names
changes. Examples of the new import paths::
AUTHENTICATION_BACKENDS = (
'social.backends.open_id.OpenIdAuth',
'social.backends.google.GoogleOpenId',
'social.backends.google.GoogleOAuth2',
'social.backends.google.GoogleOAuth',
'social.backends.twitter.TwitterOAuth',
'social.backends.facebook.FacebookOAuth2',
)
Session
-------
Django stores the last authentication backend used in the user session as an
import path, this can cause import troubles when porting since the old import
paths aren't valid anymore. Some solutions to this problem are:
1. Clean the session and force the users to login again in your site
2. Run a migration script that will update the authentication backend session
value for each session in your database. This implies figuring out the new
import path for each backend you have configured, which is the value used in
``AUTHENTICATION_BACKENDS`` setting.
`@tomgruner`_ created a Gist here_ that updates the value just for Facebook
backend. A ``template`` for this script would look like this::
from django.contrib.sessions.models import Session
BACKENDS = {
'social_auth.backends.facebook.FacebookBackend': 'social.backends.facebook.FacebookOAuth2'
}
for sess in Session.objects.iterator():
session_dict = sess.get_decoded()
if '_auth_user_backend' in session_dict.keys():
# Change old backend import path from new backend import path
if session_dict['_auth_user_backend'].startswith('social_auth'):
session_dict['_auth_user_backend'] = BACKENDS[session_dict['_auth_user_backend']]
new_sess = Session.objects.save(sess.session_key, session_dict, sess.expire_date)
print 'New session saved {}'.format(new_sess.pk)
.. _django-social-auth: https://github.com/omab/django-social-auth
.. _python-social-auth: https://github.com/omab/python-social-auth
.. _example app: https://github.com/omab/python-social-auth/blob/master/examples/django_example/example/urls.py#L17
.. _Facebook OAuth2 backend: https://github.com/omab/python-social-auth/blob/master/social/backends/facebook.py#L29
.. _@tomgruner: https://github.com/tomgruner
.. _here: https://gist.github.com/tomgruner/5ce8bb1f4c55d17b5b25
|