django-allauth 0.18.0 released
Posted by Raymond Penners on 2014-08-12
Note worthy changes
- Storing social access tokens is now optional (SOCIALACCOUNT_STORE_TOKENS).
- nimiq contributed ORCID support, thanks.
- All forms are now pluggable via a new setting: (SOCIAL)ACCOUNT_FORMS.
- James Thompson contributed Windows Live support, thanks!
Backwards incompatible changes
- SECURITY: The Persona provider now requires the AUDIENCE parameter to be explicitly configured, as required by the Persona specification for security reasons.
- The inline Javascript is removed from the fbconnect.html template, which allows for a more strict Content-Security-Policy. If you were using the builtin fbconnect.html this change should go by unnoticed.
Next: django-allauth 0.19.0 released Previous: django-allauth 0.17.0 released