aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs
diff options
context:
space:
mode:
authorJoey Hess <joeyh@joeyh.name>2016-04-28 19:32:58 -0400
committerJoey Hess <joeyh@joeyh.name>2016-04-28 19:32:58 -0400
commit3aa705b38a03e4d0c936756e5a213604ba75829e (patch)
tree99229bf321f6dc62ac585e656512941b88afaa2e /doc/bugs
parent95c0a63675036b0f8bed7fd7a0d8485d4f605578 (diff)
downloadikiwiki-3aa705b38a03e4d0c936756e5a213604ba75829e.tar
ikiwiki-3aa705b38a03e4d0c936756e5a213604ba75829e.tar.gz
response
Diffstat (limited to 'doc/bugs')
-rw-r--r--doc/bugs/cannot_login.mdwn20
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/bugs/cannot_login.mdwn b/doc/bugs/cannot_login.mdwn
index a4f129500..cd13ba313 100644
--- a/doc/bugs/cannot_login.mdwn
+++ b/doc/bugs/cannot_login.mdwn
@@ -38,3 +38,23 @@ Thanks. --[[anarcat]]
Update: now I can't login to the ikiwiki.info site anymore, getting
the same errors as on the git-annex site.
+
+> This seems to be a concacentation of multiple unrelated problems with
+> different stuff, which is not a good bug report technique. Then to add to
+> the fun, you filed the same bug on branchable too. Sigh!
+>
+> The `time_bad_sig` problem with the perl openid library is a problem I am
+> aware of but it's not clear if the problem is clock skew, or a protocol
+> problem. At least one user to report it seemed to get it due to a http
+> proxy. I'm pretty sure it could also happen if multiple openid logins
+> were attempted at the same time (the `consumer_secret` which is stored
+> server-side is used). The problem is not specific to ikiwiki.
+>
+> Ikiwiki says "login failed, perhaps you need to turn on cookies?" when
+> the user successfully logged in, but their cookie does not indicate why
+> they were logging in to begin with, so ikiwiki does not know what action
+> to continue to. One way to get this when cookies are enabled is to
+> re-post a login form after already using it, by eg using the back button
+> to go back to a previous login form and try to reuse it.
+>
+> --[[Joey]]