Closed (duplicate)
Project:
Drupal core
Version:
6.2
Component:
openid.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
29 May 2008 at 18:45 UTC
Updated:
5 Apr 2010 at 22:41 UTC
I delegate my openid provider using openid.delegate and openid.server like so:
<link href='http://www.myopenid.com/server' rel='openid.server' />
<link href='http://ryantm.myopenid.com' rel='openid.delegate' />
<meta content='http://www.myopenid.com/xrds?username=ryantm.myopenid.com' http-equiv='X-XRDS-Location' />
while this is perfectly valid under the openid protocol and actually works on a lot of other sites, this module is telling me that my URL is not a valid OpenID.
I have filed this as a bug report because the current implementation claims to support OpenID but deviates from the standard protocol.
| Comment | File | Size | Author |
|---|---|---|---|
| noopenid.png | 19.85 KB | ryantm |
Comments
Comment #1
ryantm commentedSlightly more details are available here, though it's kinda a whiny rant:
http://www.ryantm.com/blog/2008/05/29/delegating-your-openid-authenticat...
Comment #2
sidharth_k commentedThanks for your comment. I'm facing similar problems. My request to the author of the plugin to include this basic feature
Comment #3
robin monks commentedI also have this issue, with using my robinmonks.com site as my openid on any Drupal 6 site.
Robin
Comment #4
sanduhrssubscribing.
Comment #5
heine commentedCare to post those details here? The post is not available.
Comment #6
c960657 commentedThe problem is that you site contains <meta content='http://www.myopenid.com/xrds?username=ryantm.myopenid.com' http-equiv='X-XRDS-Location' /> which is perfectly valid, but Drupal expects the http-equiv attribute to appear before the content.
This is a duplicate of #469590: Improve robustness of OpenID parsing for link 'rel' and meta 'http-equiv' attributes.