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.

CommentFileSizeAuthor
noopenid.png19.85 KBryantm

Comments

ryantm’s picture

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...

sidharth_k’s picture

Thanks for your comment. I'm facing similar problems. My request to the author of the plugin to include this basic feature

robin monks’s picture

I also have this issue, with using my robinmonks.com site as my openid on any Drupal 6 site.

Robin

sanduhrs’s picture

subscribing.

heine’s picture

Slightly more details are available here, though it's kinda a whiny rant:

Care to post those details here? The post is not available.

c960657’s picture

Status: Active » Closed (duplicate)

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.