When you try to login with a Blogger account like "username.blogspot.com" the server returns this error:

"error:Invalid AuthRequest: 768: Invalid value for openid.ns field: http://openid.net/signon/1.0"

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

jjzeidner’s picture

I got the same problem... are you using a blogger id that is a mapped domain?

techtonik’s picture

Blooger doesn't support OpenID 1.1 servers. A patch is available for version 5.x http://drupal.org/node/233885 I guess you should bring more attention to it.

mfer’s picture

Version: 6.0 » 7.x-dev

There is, also, a drupal 5 patch from bryght at https://svn.bryght.com/dev/log/bryghtbase/DRUPAL-5/trunk/patches/openid.....

The issue seems to be that drupal is sending openid.ns to openid 1 or 1.1 servers and that can cause failure (I think).

It looks like this is still in drupal 7 so it should be fixed there and backported.

c960657’s picture

Status: Active » Needs review
FileSize
1.37 KB

Patch for Drupal's HEAD based on the patch in #233885: [PATCH] Blogger Authentication Fix (OpenID 1.1 server compatibility) for the OpenID contrib module for D5.

Status: Needs review » Needs work

The last submitted patch failed testing.

c960657’s picture

Status: Needs work » Needs review
FileSize
2.95 KB

Required some changes to the openid_test.module also.

Dries’s picture

Version: 7.x-dev » 6.x-dev
Status: Needs review » Needs work
Issue tags: +Needs backport to D6

Committed to CVS HEAD. Thanks.

Changing the version number so we can backport it to Drupal 6.

c960657’s picture

Status: Needs work » Needs review
FileSize
1.38 KB

Backport for D6.

Vacilando’s picture

Subscribing

c960657’s picture

FileSize
917 bytes

Updated D6 patch.

Anonymous’s picture

Status: Needs review » Closed (won't fix)

I'm going to guess this is a won't fix for D6, since D6 commits focus on security fixes at this point.

Anonymous’s picture

Version: 6.x-dev » 7.x-dev
Status: Closed (won't fix) » Closed (fixed)

Changing issue status to reflect that it was fixed in 7.x.