blogspam uses JSON instead of RPC::XML now.

[git.ikiwiki.info.git] / doc / todo / BrowserID.mdwn

diff --git a/doc/todo/BrowserID.mdwn b/doc/todo/BrowserID.mdwn
index 9340dc0f1848971f92ce7dc43fc88d73af9c68b1..04a9166a8e9e883705702141b20ba0f44d580d99 100644 (file)
--- a/doc/todo/BrowserID.mdwn
+++ b/doc/todo/BrowserID.mdwn
@@ -6,3 +6,20 @@ Some additional information on BrowserID:
 - <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>
 - <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>

+
+> 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
+> CA security as the only security in that part of the protocol.)
+> 
+> This seems to need an implementation, in perl or an externally callable
+> program (haskell would be fine ;),
+> of <https://wiki.mozilla.org/Identity/BrowserID#Assertion_Verification>.
+> --[[Joey]]