LaurensRietveld
commented
10 years ago Hi jneubert, did you manage to log in (using this openid) before without any problems?
Closed jneubert closed 10 years ago
LaurensRietveld
commented
10 years ago Hi jneubert, did you manage to log in (using this openid) before without any problems?
jneubert
commented
10 years ago No, this was my first try.
LaurensRietveld
commented
10 years ago Could you check whether you are successful logging in with your openId on yasgui.laurensrietveld.nl? In the other bug report you mentioned a reverse proxy. That might be the reason why logging in fails (e.g. the openid callback not properly arriving at its location).
jneubert
commented
10 years ago The try reported above was on yasgui.laurensrietveld.nl (it did not work on my site, either). I just repeated it, but no luck.
LaurensRietveld
commented
10 years ago I've tried to reproduce this issue using the stackoverflow openid, and failed to get the reported error. This bug is closely related to something a colleague of mine encountered (though with google openid). I'm still busy trying to figure out the cause. Could you try whether the same issue occurs on dev.yasgui.laurensrietveld.nl? I've added several debug statements to that version, so I'll be better able to debug this issue
jneubert
commented
10 years ago Yes, it's just the same with dev.yasgui.laurensrietveld.nl. I get the
dev.yasgui.laurensrietveld.nl wants you to log in Do you wish to share your information with dev.yasgui.laurensrietveld.nl?
When I confirm, I'm redirected to dev.yasgui.laurensrietveld.nl, but still not logged in.
jneubert
commented
10 years ago As an afterthougt: I've configured Firefox to never accept Third-Party-Cookies. Is this the mechanism OpenID uses?
LaurensRietveld
commented
10 years ago Hmm, that might very well be. Could you try setting firefox to accept these third party cookies?
My logs do show a few interesting things, very similar to the bug described here (with stackexchange account as well..): http://stackoverflow.com/questions/8309927/consumermanager-verify-fails-with-no-service-element-found-to-match-the-claim
Could you try one of the other openid providers, to make sure we are not dealing with a stackexchange-specific error here?
jneubert
commented
10 years ago I've enabled third-party cookies. After the download of a new yasgui version for offline use, the application hangs with a white screen at the uri:
Same with
Same happens with my new myopenid account
LaurensRietveld
commented
10 years ago ah, the white screen is a similar issue I encountered before with a colleague of mine, though I havent been able to reproduce it myself... I've updated the openid library I use, hoping this will fix this issue. The new YASGUI version + the new openid library will be available in a few minute on both the dev as well as the normal yasgui version. Could you check whether this solves anything?
jneubert
commented
10 years ago Some additional information (for yasgui.laurensrietveld.nl):
LaurensRietveld
commented
10 years ago update: I'm able to reproduce this issue, but haven't been able to pinpoint the exact cause yet. The step where the authentication goes wrong is where the yasgui server is unable to validate the response received from the openid server. What is strange, is that the yasgui server -is- able to validate responses from other openid servers. I.e., to be continued
LaurensRietveld
commented
10 years ago I'll continue this in #245 , where I'll implement OpenId functionality for the new meteor.js alpha version
Just (27.12.2013, 13:19 Berlin time) tried to login via https://openid.stackexchange.com/ (used MSIE for this, tried before with Firefox). The openid dialog looks correct, but yasgui still shows "(not logged in)".