Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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"
Comment | File | Size | Author |
---|---|---|---|
#10 | openid-blogger-3.patch | 917 bytes | c960657 |
#8 | openid-blogger-D6-1.patch | 1.38 KB | c960657 |
#6 | openid-blogger-2.patch | 2.95 KB | c960657 |
#4 | openid-blogger.patch | 1.37 KB | c960657 |
Comments
Comment #1
jjzeidner CreditAttribution: jjzeidner commentedI got the same problem... are you using a blogger id that is a mapped domain?
Comment #2
techtonik CreditAttribution: techtonik commentedBlooger 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.
Comment #3
mfer CreditAttribution: mfer commentedThere 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.
Comment #4
c960657 CreditAttribution: c960657 commentedPatch 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.
Comment #6
c960657 CreditAttribution: c960657 commentedRequired some changes to the openid_test.module also.
Comment #7
Dries CreditAttribution: Dries commentedCommitted to CVS HEAD. Thanks.
Changing the version number so we can backport it to Drupal 6.
Comment #8
c960657 CreditAttribution: c960657 commentedBackport for D6.
Comment #9
Vacilando CreditAttribution: Vacilando commentedSubscribing
Comment #10
c960657 CreditAttribution: c960657 commentedUpdated D6 patch.
Comment #11
Anonymous (not verified) CreditAttribution: Anonymous commentedI'm going to guess this is a won't fix for D6, since D6 commits focus on security fixes at this point.
Comment #12
Anonymous (not verified) CreditAttribution: Anonymous commentedChanging issue status to reflect that it was fixed in 7.x.