Opened 14 years ago
Last modified 12 years ago
#314 closed enhancement
Mozilla Persona (BrowserID) support — at Version 5
| Reported by: | Christopher Allan Webber | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.5.0 |
| Component: | programming | Keywords: | auth |
| Cc: | Parent Tickets: |
Description (last modified by )
Talked to the openphoto people. They have browserid support, which
looks easy and pleasant:
`https://browserid.org/ <https://browserid.org/>`_
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 (5)
comment:2 by , 14 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:4 by , 13 years ago
| Summary: | BrowserID support → Mozilla Persona (BrowserID) support |
|---|---|
| Type: | defect → enhancement |
comment:5 by , 13 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.
Note:
See TracTickets
for help on using tickets.
