Problem using delegated identity

Brian Kissel bkissel at
Fri Jan 23 18:50:54 UTC 2009


Your X-XRDS-Location HTTP header points to, which is an empty file.  RPX is
discovering that file, but then doesn't know what to do because there
isn't any useful information in it.  See the output below.

brianellin at r4d: $ wget -S
--2009-01-22<> 12:00:27--
Connecting to<>||:80... connected.
HTTP request sent, awaiting response...
 HTTP/1.1 200 OK
 Date: Thu, 22 Jan 2009 19:59:40 GMT
 Server: Apache/2.0.63
 Content-Type: text/html; charset=utf-8

HTTP headers are used first when discovering services, so change that
header to point to and it will
work.  Also, you may safely remove the X-Yadis-Location header and
meta tags from your page.  Additionally, you should only have one
X-XRDS-Location meta tag in your page, and it should point to

Hope that helps,
Brian Ellin


Brian Kissel
Cell: 503.866.4424
Fax: 503.296.5502

From: user-experience-bounces at [mailto:user-experience-bounces at] On Behalf Of Chris Messina
Sent: Wednesday, January 21, 2009 5:48 PM
To: OpenID user experience
Subject: Re: Problem using delegated identity

I'm not sure this is the best place for this kind of discussion, but we can certainly work through it see what we come up with.

It does look like the sites you mentioned are using Janrain's RPX service:

Your delegation looks okay for the most part. I'm unclear whether RPX is prioritizing the <link />-based delegation or directing grabbing your XRDS profile.

In either case, it looks like you have a duplicate tag for the X-XRDS-Location. Try removing these tags:

<meta http-equiv="X-XRDS-Location" content="" />

<meta http-equiv="X-Yadis-Location" content="" />

You already specified this earlier in the document:

<meta http-equiv="X-XRDS-Location" content="" />

and the later URLs seem to return an empty document.


On Wed, Jan 21, 2009 at 1:44 PM, Ahmad Gharbeia <gharbeia at<mailto:gharbeia at>> wrote:

I'm having trouble using delegated OpenID identity with some, but not
all, of the websites which claim to support OpenID.

I'm unable to log in to<> nor<> with my
delegated OpenID [<>], which I use to log in to many
other sites, including<> and many others.

Needless to say, I can log-in, if I enter the delegated provider's URI
directly, so it seems to be a problem in my delegation code, or these
consumers are unable to handle delegates.

I thought it was a v2.0 vs v1.1 issue so I changed the delegate
announcement to another which is 1.1 only, but still I get:
"failed for the OpenID you entered" for the first, and "Authentication
error; not a valid OpenID." for the second.

I tried several identity providers as delegates.

I'm unable to use with some other services as well, like<>
and<>, both of which seems to be using the same log-in applet

Any insights?

user-experience mailing list
user-experience at<mailto:user-experience at>

Chris Messina
Citizen-Participant &
 Open Web Advocate-at-Large<> #<><> #<>
This email is:   [ ] bloggable    [X] ask first   [ ] private

__________ Information from ESET NOD32 Antivirus, version of virus signature database 3787 (20090121) __________

The message was checked by ESET NOD32 Antivirus.

__________ Information from ESET NOD32 Antivirus, version of virus signature database 3794 (20090123) __________

The message was checked by ESET NOD32 Antivirus.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the user-experience mailing list