You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LabWiki is receiving "invalid check_authentication request" errors from the portal when using the OpenID authentication. The exact text of the error shown by LabWiki is:
This happens sometimes but not all the time. It happens frequently enough to be disturbing, especially for their upcoming tutorial. They estimate it happens between every third to every 10th time.
It's not clear whether the error is on the server side or the client side. The server side is not leaving anything in the logs that indicates a problem. It was easy to replicate the issue.
Imported from trac ticket #869, created by tmitchel on 10-23-2013 at 14:01, last modified: 05-16-2014 at 16:24
The text was updated successfully, but these errors were encountered:
One possibly interesting piece of information I stumbled upon today. This issue seems to not occur for all users.
Jack reported this morning that he was not able to reproduce this problem. After I tried this with both of my portal
users today, I found that I was able to reproduce it with user "johren" but not with "johren2". I tried over 20 times in a row
with both. I also swapped browsers and tried again. The problem followed the user (johren).
LabWiki is receiving "invalid check_authentication request" errors from the portal when using the OpenID authentication. The exact text of the error shown by LabWiki is:
Authentication failed. Server https://portal.geni.net/server/server.php responds that the 'check_authentication' call is not valid
Try again
This happens sometimes but not all the time. It happens frequently enough to be disturbing, especially for their upcoming tutorial. They estimate it happens between every third to every 10th time.
It's not clear whether the error is on the server side or the client side. The server side is not leaving anything in the logs that indicates a problem. It was easy to replicate the issue.
Imported from trac ticket #869, created by tmitchel on 10-23-2013 at 14:01, last modified: 05-16-2014 at 16:24
The text was updated successfully, but these errors were encountered: