2012-02-13 17:04:59 +01:00
|
|
|
Please consider providing a plugin for [BrowserID](https://browserid.org/) authentication, preferably enabled by default.
|
|
|
|
|
|
|
|
|
|
Some additional information on BrowserID:
|
|
|
|
|
|
2012-02-13 17:07:00 +01:00
|
|
|
- <https://github.com/mozilla/browserid/wiki/How-to-Use-BrowserID-on-Your-Site>
|
|
|
|
|
- <http://identity.mozilla.com/post/7616727542/introducing-browserid-a-better-way-to-sign-in>
|
|
|
|
|
- <http://identity.mozilla.com/post/7669886219/how-browserid-differs-from-openid>
|
|
|
|
|
- <http://identity.mozilla.com/post/7899984443/privacy-and-browserid>
|
2012-02-13 17:37:08 +01:00
|
|
|
|
|
|
|
|
> I would like to see BrowserID offered as a signin option in ikiwiki
|
|
|
|
|
> right next to the buttons for common openid providers.
|
|
|
|
|
>
|
|
|
|
|
> As far as implementing it goes, I don't want to rely on browserid.org.
|
|
|
|
|
> This means that include.js needs to be shipped with ikiwiki (or in a
|
|
|
|
|
> dependency in a sane world).
|
|
|
|
|
>
|
|
|
|
|
> And it means that relying on a https
|
|
|
|
|
> connection to browserid.org to verify the user's identity assertion
|
|
|
|
|
> token is out. (Well, it's probably out anyway, since it relies on https
|
2012-02-13 17:40:54 +01:00
|
|
|
> CA security as the only security in that part of the protocol.)
|
2012-02-13 17:37:08 +01:00
|
|
|
>
|
|
|
|
|
> This seems to need an implementation, in perl or an externally callable
|
|
|
|
|
> program (haskell would be fine ;),
|
2012-02-13 17:54:07 +01:00
|
|
|
> of <https://wiki.mozilla.org/Identity/BrowserID#Assertion_Verification>.
|
2012-02-13 17:37:08 +01:00
|
|
|
> --[[Joey]]
|
