3.20161229.1~bpo8+1

[git.ikiwiki.info.git] / doc / index / openid / discussion.mdwn

diff --git a/doc/index/openid/discussion.mdwn b/doc/index/openid/discussion.mdwn
index d692bf011be940115aace5b57f52f239db701ee0..4a50fd9dd5c39876ab1bcbecb79d0c4e2b5c906b 100644 (file)
--- a/doc/index/openid/discussion.mdwn
+++ b/doc/index/openid/discussion.mdwn
@@ -26,6 +26,8 @@ do=postsignin&oic.time=1238224497-1450566d93097caa707f&openid.assoc_handle=%7BHM
 
 The `return_to` arg should NOT be `signed`, it should be the originating URL where you initially logged in.
 
 
 The `return_to` arg should NOT be `signed`, it should be the originating URL where you initially logged in.
 

+>> Yes, exactly. That's also my understanding of the spec.
+

 > I think you're confusing 'openid.return_to' with 'return_to'. The
 > former is present above, and is, indeed, the originating url, the latter
 > is part of the *value* of the 'openid.signed' parameter generated by myopenid.com. --[[Joey]] 
 > I think you're confusing 'openid.return_to' with 'return_to'. The
 > former is present above, and is, indeed, the originating url, the latter
 > is part of the *value* of the 'openid.signed' parameter generated by myopenid.com. --[[Joey]] 


@@ -36,14 +38,25 @@ Also, I dunno what the assoc_handle is doing spitting out an arg like `{HMAC-SHA
 > I see the same HMAC-SHA1 when using myopenid, and completly different
 > things for other openid servers. (Ie, when using livejournal as an openid server,
 > `openid.assoc_handle=1239305290:STLS.QiU6zTZ6w2bM3ttRkdaa:e68f91b751`)
 > I see the same HMAC-SHA1 when using myopenid, and completly different
 > things for other openid servers. (Ie, when using livejournal as an openid server,
 > `openid.assoc_handle=1239305290:STLS.QiU6zTZ6w2bM3ttRkdaa:e68f91b751`)

-> 
+
+>> OK, I wasn't too sure about that, seemed bogus or somehow wrong or in error, like it wasn't actually being `completed`.
+

 > I'm fairly sure that is all a red herring.
 > 
 > So, when I was talking about reproducing the bug, I was thinking perhaps you could tell me what openid server you're using,
 > etc, so I can actually see the bug with my own eyes.
 > I'm fairly sure that is all a red herring.
 > 
 > So, when I was talking about reproducing the bug, I was thinking perhaps you could tell me what openid server you're using,
 > etc, so I can actually see the bug with my own eyes.

->
+
+>> myopenid.com, with the CNAME option turned on.
+

 > The sanitised url parameters you've provided are not generated by ikiwiki at all.
 > They don't even seem to be generated by the underlying [[!cpan Net::OpenID]] library.
 > The sanitised url parameters you've provided are not generated by ikiwiki at all.
 > They don't even seem to be generated by the underlying [[!cpan Net::OpenID]] library.

+
+>> That was a server log entry with date/host/time stripped, and my URL also stripped. Everything else is as was in the log. I installed the Debian packages in Lenny, both server and consumer OpenID Perl packages.
+

 > I'm pretty sure that what you're showing me is the url myopenid redirects
 > the browser to after successfully signing in. At that point, ikiwiki
 > should complete the signin. What fails at this point? How can I reproduce this failure? --[[Joey]] 
 > I'm pretty sure that what you're showing me is the url myopenid redirects
 > the browser to after successfully signing in. At that point, ikiwiki
 > should complete the signin. What fails at this point? How can I reproduce this failure? --[[Joey]] 

+
+I'll try it again myself. I had tried it oh probably 6 times before I finally gave up on it. Maybe I'm getting rusty and I'm just PEBKACing all over the place. :P
+
+Also, to address the point about this discussion being in the wrong area (not under bugs), should I move it, or will you? I don't mind doing it, if you can't.