move socorro login to browserid

RESOLVED WORKSFORME

Status

Socorro
Webapp
RESOLVED WORKSFORME
6 years ago
4 years ago

People

(Reporter: rhelmer, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
We still need to use LDAP on the backend, so will probably use https://github.com/ozten/sasl-browserid

More info at https://wiki.mozilla.org/Mozillians/Releases/1.2/BrowserID
(Assignee)

Updated

6 years ago
Component: Socorro → General
Product: Webtools → Socorro

Updated

6 years ago
Component: General → Webapp
I noticed this while testing crash-stats-new-dev.allizom.org tonight, and spoke to a couple folks on the Identity team about it:

[18:17:19.346] GET https://browserid.org/include.js [HTTP/1.1 302 Moved Temporarily 124ms]
[18:17:19.454] GET https://login.persona.org/include.js [HTTP/1.1 304 Not Modified 113ms]

They say we should change to use the persona.org/include.js, rather than defaulting to the browserid.org one, as well as changing the backend verifier from https://browserid.org/verify -> https://verifier.login.persona.org/verify
(Reporter)

Comment 2

4 years ago
We moved onto persona/browserid with the new django frontend.

re: comment 1, we are using a django app to do this (django-browserid) so that issue should be taken there if it's still a problem.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.