OpenID login fails when using Google Account (http://openid-provider.appspot.com/[username]) as an OpenID URL with following notices:

Notice: Undefined index: openid.response_nonce in openid_verify_assertion_nonce() (line 862 of /modules/openid/openid.module).
Notice: Undefined index: openid.response_nonce in openid_verify_assertion_nonce() (line 867 of /modules/openid/openid.module).

CommentFileSizeAuthor
#5 google-openid-error.png9.41 KBAnonymous (not verified)
#5 yahoo-openid-error.png20.17 KBAnonymous (not verified)

Comments

tormi’s picture

tormi
Primary language Estonian
Location Tallinn
commented
Status: Active » Closed (works as designed)

Tried with wrong URL, http://www.google.com/profiles/[username] is working just fine. Sry ;)

aldaris’s picture

aldaris commented

Hi,

I've encountered a very similar error:
Notice: Undefined index: openid.response_nonce in openid_verify_assertion_nonce() (line 929 of /modules/openid/openid.module).
also on line 924 with drupal-7.10

For me the problem was that the OP failed to discover the RP, so it sent back an error message, like:
http://FQDN/drupal/?q=openid/authenticate&destination=node&openid.mode=e...

In http://openid.net/specs/openid-authentication-2_0.html#indirect_comm section 5.2.3 openid.mode=error is used, so I believe the Drupal OpenID implementation should be able to handle such indirect error messages.

aldaris’s picture

aldaris commented
Status: Closed (works as designed) » Active
c960657’s picture

c960657 commented

AFAICT http://openid-provider.appspot.com/[username] advertises itself as an OpenID 2.0 Provider, but in fact it responds using OpenID 1.x. This is a spec violation, so it is not expected to work (but we should still handle this more gracefully than throwing PHP notices).

Anonymous’s picture

Anonymous (not verified) commented
StatusFileSize
new yahoo-openid-error.png20.17 KB
new google-openid-error.png9.41 KB

I am on Drupal 7.22 and I can not use yahoo nor google open id to log in or to assign it to my local user account.
I am getting errors as on attached images.

Status: Active » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.