Posted by ryantm on May 29, 2008 at 6:45pm
Jump to:
| Project: | Drupal core |
| Version: | 6.2 |
| Component: | openid.module |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (duplicate) |
Issue Summary
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.
| Attachment | Size | Status | Test result | Operations |
|---|---|---|---|---|
| noopenid.png | 19.85 KB | Ignored: Check issue status. | None | None |
Comments
#1
Slightly more details are available here, though it's kinda a whiny rant:
http://www.ryantm.com/blog/2008/05/29/delegating-your-openid-authenticat...
#2
Thanks for your comment. I'm facing similar problems. My request to the author of the plugin to include this basic feature
#3
I also have this issue, with using my robinmonks.com site as my openid on any Drupal 6 site.
Robin
#4
subscribing.
#5
Care to post those details here? The post is not available.
#6
The 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.