6 ms·

How is this better than the decentralized Persona Identify solution that Mozilla's promoting: https://developer.mozilla.org/en-US/docs/Persona/Identity_Provider

by ecaron 14y ago

How is this better than the decentralized Persona Identify solution that Mozilla's promoting: https://developer.mozilla.org/en-US/docs/Persona/Identity_Provider_Overview https://developer.mozilla.org/en-US/docs/Persona/Identity_Pr...

TazeTSchnitzel 14y ago
Especially considering Persona already has some websites that use it (like MDN, and my websites)
dreamdu5t 14y ago
It's not. We should be spending time implementing Persona rather than trying to come up with new identity solutions. Mozilla browserid/Persona is good enough or better than any other solution presented thus far, and has the best chance for adoption.
- StavrosK 14y ago
  I cannot agree with this enough. I implemented BrowserID on one of my sites once, and never looked back. Now every new project uses BrowserID as the only way to log in. It is superior to all other ways I've seen in usability, which is ultimately what counts, and integration takes all of two minutes, much less than traditional password auth. Plus, you don't even need to secure any passwords. I really, really hope it catches on, and Google/Yahoo!/other mail providers start supporting it.
  - FourthProtocol 14y ago
    From a usability perspective WS-Federation is far superior to BrowserId. Not least because BrowserId is hobbled by the browser, whereas WS-Fed works across any platform, any architecture (native desktop/phone/tablet, browser, cloud ...), any OS.
  - gregcohn 14y ago
    How does BrowserID work in the use case of a native mobile app?
    - StavrosK 14y ago
      Looks like it works like this: https://github.com/mozilla/browserid-ios https://github.com/mozilla/browserid-ios
- FourthProtocol 14y ago
  Note that this is my personal opinion. I think we should be trying to come up with new solutions - BrowserId/Persona some some identity problems, but nowhere near all. Have a read through Kim Cameron's post [1] to get a feel for how naive, if noble, Mozilla's efforts are. http://www.identityblog.com/?p=352 http://www.identityblog.com/?p=352
callahad 14y ago
It's interesting in that it's trying to learn from newer efforts and back-port aspects of them into OpenID, while maintaining backward compatibility. I'm still not sure who it's for, though, since OpenID shows that URL-based IDs are really hard for the general public... That said, I wouldn't go as far as dreamdu5t in suggesting that we as a community stop working on alternative solutions. I work on Persona and think it's fantastic, but no identity system is a panacea. Of course, I would really love to read a more thorough post from the author regarding his decision to roll his own system. PS: ecaron, I think I owe you a coffee and a much belated email. :)

by ecaron 14y ago

TazeTSchnitzel 14y ago

Especially considering Persona already has some websites that use it (like MDN, and my websites)

dreamdu5t 14y ago

It's not. We should be spending time implementing Persona rather than trying to come up with new identity solutions. Mozilla browserid/Persona is good enough or better than any other solution presented thus far, and has the best chance for adoption.

StavrosK 14y ago
I cannot agree with this enough. I implemented BrowserID on one of my sites once, and never looked back. Now every new project uses BrowserID as the only way to log in. It is superior to all other ways I've seen in usability, which is ultimately what counts, and integration takes all of two minutes, much less than traditional password auth. Plus, you don't even need to secure any passwords. I really, really hope it catches on, and Google/Yahoo!/other mail providers start supporting it.
- FourthProtocol 14y ago
  From a usability perspective WS-Federation is far superior to BrowserId. Not least because BrowserId is hobbled by the browser, whereas WS-Fed works across any platform, any architecture (native desktop/phone/tablet, browser, cloud ...), any OS.
- gregcohn 14y ago
  How does BrowserID work in the use case of a native mobile app?
  - StavrosK 14y ago
    Looks like it works like this: https://github.com/mozilla/browserid-ios https://github.com/mozilla/browserid-ios
FourthProtocol 14y ago
Note that this is my personal opinion. I think we should be trying to come up with new solutions - BrowserId/Persona some some identity problems, but nowhere near all. Have a read through Kim Cameron's post [1] to get a feel for how naive, if noble, Mozilla's efforts are. http://www.identityblog.com/?p=352 http://www.identityblog.com/?p=352

callahad 14y ago

It's interesting in that it's trying to learn from newer efforts and back-port aspects of them into OpenID, while maintaining backward compatibility. I'm still not sure who it's for, though, since OpenID shows that URL-based IDs are really hard for the general public... That said, I wouldn't go as far as dreamdu5t in suggesting that we as a community stop working on alternative solutions. I work on Persona and think it's fantastic, but no identity system is a panacea. Of course, I would really love to read a more thorough post from the author regarding his decision to roll his own system. PS: ecaron, I think I owe you a coffee and a much belated email. :)