Closed Bug 715723 Opened 14 years ago Closed 14 years ago

browserid: Signing into MDN takes you away from the page you were at

Categories

(developer.mozilla.org Graveyard :: Wiki pages, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jrmuizel, Assigned: groovecoder)

References

Details

(Whiteboard: u=user c=browserid p=3)

Attachments

(1 file)

STR: - Goto https://developer.mozilla.org/en/Debugging_Safari - Click "Sign in". - Sign in using browser id - End up here: https://developer.mozilla.org/en-US/users/login
Whiteboard: u=user c=browserid p=
Target Milestone: --- → 2.0
Luke this is related to what we discussed on IRC
Summary: Signing into MDN takes you away from the page you were at → browserid: Signing into MDN takes you away from the page you were at
Craig, is there any way to do the browserid pop-up with the post to /users/browserid_verify on the deki skin header the same way we do on the django header?
Target Milestone: 2.0 → 2.1
Few things have to happen: * Bypass CSRF for browserid_verify * Add browserid javascript to MT skin ** Only for en locale
Whiteboard: u=user c=browserid p= → u=user c=browserid p=3
Bypassing CSRF for browserid_verify: https://github.com/mozilla/kuma/pull/90
Commits pushed to https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/1893f195045effe7f05c5d5be568b4ea87bd8ce9 bug 715723: Make the browserid verification form exempt from CSRF protection https://github.com/mozilla/kuma/commit/edb99c36ff8e72d09fa5700101ea1cb9095d609e Merge pull request #90 from lmorchard/bug-715723 Bug 715723 - Make the BrowserID verification form exempt from CSRF protection
Assignee: nobody → craigcook.bugz
I've done the initial integration of BrowserID into the skin in r100272 but it now needs to be wired into our django authentication, and the info dropdown needs to be cookied so it's only shown to first-timers (and it should read the same cookie we're setting on the django site). So alas, I've done about all I can do and must hand off to Luke now to actually make it work.
Assignee: craigcook.bugz → nobody
Assignee: nobody → lcrouch
Diff applied in r100284
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Need to address a potential CSRF scenario.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Component: Website → Landing pages
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: