I am using the D7 port of openid_provider provided by the patch in comment #51 from http://drupal.org/node/983128#comment-5396932. I'm also using the required D7 port of xrds_simple from http://drupal.org/sandbox/paranojik/1232184.

I receive this error on the redirect back to slashdot: "Unable to verify with http://specs.openid.net/auth/2.0/identifier_select."

I have also applied the patch at http://drupal.org/node/831162#comment-5523752 which fixes an issue logging in to stackoverflow sites. This had no effect on slashdot -- I received the same error before and after this patch.

Also, I was unable to select a 7.x version for this bug report since none was available in the dropdown.

CommentFileSizeAuthor
#7 Screenshot-Recent log messages.png37.21 KBjwineinger
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Version: 6.x-1.x-dev » 7.x-1.0-beta1

Updating version number. Note that this probably also applies to 6.x though.

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Status: Active » Closed (cannot reproduce)

I could login here. It took me two attempts however, but it worked. Try again with beta3.

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Version: 7.x-1.0-beta1 » 7.x-1.0-beta3
Status: Closed (cannot reproduce) » Needs work

In fact, i can reproduce this issue, but only from the dropdown login box on the frontpage. It works from /login.pl. Not sure what's going on here, maybe a case of check_immediate not working?

jwineinger’s picture

jwineinger CreditAttribution: jwineinger commented

I tried to test with rc1 today but I got a new error for both slashdot and stackexchange. I opened a new issue for that at http://drupal.org/node/1421536

jwineinger’s picture

jwineinger CreditAttribution: jwineinger commented

After applying the commit mentioned in http://drupal.org/node/1421536#comment-5533702 (http://drupalcode.org/project/openid_provider.git/commit/9a7efea), I got past the error I mentioned in #4.

There is, however, no change in my inability to login to slashdot. I receive the same error as in the initial bug report above.

anarcat’s picture

anarcat CreditAttribution: anarcat commented

I have tried to improve the code again, but I doubt it will fix your problem.

Please try to enable debugging in the module and provide information from the watchdog.

jwineinger’s picture

jwineinger CreditAttribution: jwineinger commented
FileSize
Screenshot-Recent log messages.png37.21 KB

No, I have the same result with slashdot. I've attached a screenshot of the watchdog report with all messages during the time I attempted to login to slashdot. Let me know if any of the items are important and if you need more detail.

anarcat’s picture

anarcat CreditAttribution: anarcat commented

Hum, so things look fine on our end - i guess i would need the dump of all messages marked 12:49 (within the same minute).

Also, please try again with rc2, I have formalized more things... It this applies to rc2, please changed the version field. :)

jwineinger’s picture

jwineinger CreditAttribution: jwineinger commented
Version: 7.x-1.0-beta3 » 7.x-1.0-rc2
anarcat’s picture

anarcat CreditAttribution: anarcat commented

Crap. :)

Please provide the full log, not only the screenshot of the listing, but what you get when you click on the messages. You can also get a full dump with "drush ws --tail".

Thanks for your persistence!