Opened 12 years ago

Closed 11 years ago

Last modified 11 years ago

#314 closed enhancement (fixed)

Mozilla Persona (BrowserID) support

Reported by: Christopher Allan Webber Owned by:
Priority: minor Milestone: 0.5.0
Component: programming Keywords: auth
Cc: Parent Tickets:

Description (last modified by Christopher Allan Webber)

Talked to the openphoto people. They have browserid support, which
looks easy and pleasant:
` <>`_

Furthermore, the OpenPhoto people say it's easy. So why not support
it? :)


    <paroneayea> hub: we don't use browserid yet
    <paroneayea> but I'd like to
    <jmathai> paroneayea: said there's a json spec but it's not finalized yet
    <paroneayea> how hard is browserid to implement?
    <paroneayea> it looks beautifully pleasant to use
    <jmathai> trivial
    <paroneayea> really?
    <paroneayea> awesome

Change History (10)

comment:1 by Will Kahn-Greene, 12 years ago

I spent a few hours today looking at BrowserID. It does look easy
to implement. We'd probably want to use Ian's wsgibrowserid:

` <>`_

Some interesting things I learned:

1. browserid doesn't currently support non-browser or
   non-js-enabled-browser authentication

2. in order to support non-browser applications through an API,
   we'd have to provide another authentication backend; Ian suggested
   maybe OAuth

3. if we implement browserid, we essentially nix the idea of
   "registration". i'm not sure how this affects mediagoblin. it's
   possible that someone would log in and then MG would deny them
   access if it's not accepting new registrations?


-  ` <>`_
-  ` <>`_
   (note no "register")

Last edited 11 years ago by Christopher Allan Webber (previous) (diff)

comment:2 by Christopher Allan Webber, 12 years ago

Do we **have to** nix the idea of registration? Can't we associated
a browserid with a registered account as an easier way to log in?
Alternately, use browserid for accelerated registration?

comment:3 by Will Kahn-Greene, 12 years ago

The original url for this bug was .

comment:4 by Aleksej, 12 years ago

Summary: BrowserID supportMozilla Persona (BrowserID) support
Type: defectenhancement

comment:5 by Christopher Allan Webber, 11 years ago

Description: modified (diff)

Okay, here's some updates. More generally, I'm updating this as a "support multiple authentication login systems" ticket.

  • We have a plugin system. Yayy!
  • I need to have a better understanding of it. Because of that, I'm working on #477 so I can actually do some plugin work myself.
  • After that's done I'd like to evaluate the state of login stuff and how we can make it more flexible.

comment:6 by Christopher Allan Webber, 11 years ago

Keywords: auth added

Note: if the pluggable auth stuff happens for GSoC/OPW, this ticket might wrap into it.

comment:7 by rodney757, 11 years ago

Owner: set to rodney757
Status: acceptedin_progress

comment:8 by rodney757, 11 years ago

Owner: rodney757 removed
Status: in_progressreview

need basic_auth and openid branches to land first as this is branch is based off of those.

comment:9 by rodney757, 11 years ago

Resolution: fixed
Status: reviewclosed


comment:10 by rodney757, 11 years ago

Milestone: 0.5.0
Note: See TracTickets for help on using tickets.