Additional registration & login

[h0pbeat]

We need social registration and login for the platform. For the ESOF deployment we need at least Facebook registration.
We need to add another registration page template (in a perfect world we will have wrappers allowing adding/removing registration options, see http://janrain.com/products/engage/social-login/), where we will allow user to register with Facebook. Each such wrapper should be a standalone piece of code that exposes the registration/login url and ends up with user registered/logged in.

Also login page should be switched to 'login with Facebook'.
For ESOF we will NOT support username/password registration & login.

The registration/login wrappers should be re-usable for Profile page (where CAS is right now).

[lassevalentini]

There are two major packages which can be used: django-allauth and python-social-auth. For now python-social-auth seems to be the way to go.

I'm close to have it set up for testing on the esof dev site.

[lassevalentini]

Python social auth have started responding (had a little confusion with the deployment). Should be able to see some integration next week.

[lassevalentini]

First successful Facebook registration creating the user as if they registered through the regular form. It is storing too much info in the user atm. (first & last name).

Replacing the registration & login pages will be next week.

[h0pbeat]

Thanks.

1. Please make sure to stay in sync with devel branch.
2. Please split at some point into a separate django application.
3. Login and registration should be the same page (just login with facebook, whether it is first or returning login)

[lassevalentini]

I've split out the social auth into a separate app. Not sure how we want it to behave by default though. Right now it redefines the login/register/authenticate urls and replaces the login/register buttons with social auth buttons.

We can now use all the social backends that python-social-auth handles (list here).

Adding and removing backends is done by editing main settings/AUTHENTICATION_BACKENDS and giving them a pretty name, icon and btn-style in accounts_social/accounts_social.py.

Still storing first & last name in user object even though we shouldn't.