Closed Bug 1029086 Opened 11 years ago Closed 11 years ago

Use django-allauth instead of django-browserid for authentication

Categories

(developer.mozilla.org Graveyard :: Sign-in, enhancement)

Product:
developer.mozilla.org Graveyard
Component:
Sign-in
Platform:
x86_64
Linux
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mars, Assigned: jezdez)

References

Details

We should replace our multiple site login libraries with django-allauth, a framework for adding new login methods to django and that comes with a number of popular login methods out of the box. allauth supports Persona, so users could still use Persona for logins, and it would enable us to use new authentication mechanisms like OAuth2.
Pull request is here: https://github.com/mozilla/kuma/pull/2552
Blocks: 981324
Depends on: 1031547
From the Monday meeting: bug 789016 describes the past issues we've had with auth referrers on MDN. We should test the new auth system to see if the referrer bugs still exist. I'm blocking on bug 789016 as a note to ourselves to test for this. Feel free to unblock once we've confirmed if the bug exists and what it's impact may be.
Depends on: 789016
The WebQA tests will need to be updated, too. Do we need to block on this? https://github.com/mozilla/mdn-tests/issues/92
Depends on: 1045112
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.