Browserid is rockin', but we still want to require privileged users to authenticate to AMO with a password. If you need UI help, let us know. Greg recently wrote a lightbox login which will also be affected here. Privileged users here include: Admin:*, Editors:*
Sorry, I haven't been following the latest developments with AMO and browserid. How does the use of browserid change the interaction of admins/editors with the privileged sections of AMO? Does logging in with browserid currently allow the same privileges as going through the standard AMO login? I'm guessing that since browserid uses different credentials, requiring AMO password is to prevent abuse of a logged in browserid session.
browserid is going to be equivalent to our current authentication. We're adding password auth for privileged accounts as a secondary auth. This was talked about with mcoates and yboily via email a bit.
(In reply to David Chan [:dchan] from comment #1) > How does the use of browserid change the interaction of admins/editors with > the privileged sections of AMO? Does logging in with browserid currently > allow the same privileges as going through the standard AMO login? This is just another layer of defense for accounts with lots of privilege since browserid is a baby and still "experimental".
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.