[OpenID] Interoperability problem with OpenID POST response between myopenid and Google

[Peter Williams]

I cannot draw that conclusion.

You now have two interesting points on the curve, with contrary results. A fact in common is myopenid.

Extend your own experiment to include http://dotnetopenauth.net/samples/v3.0/OpenIdRelyingPartyWebForms/

See if you can replicate my trial on your platforms.

you can use home_pw.myopenid.com, and password "password" if you want, to save time.

-------

@blog*lockbox doesn't work at that RP, as a redirector to https://home_pw.myopenid.com. I suspect it should. Using XRI i-services (and HXRIs) allows you test the engineering limits of the RP's discovery support.


________________________________________
From: André Cruz [andre.cruz at co.sapo.pt]
Sent: Monday, May 25, 2009 8:10 AM
To: Peter Williams
Cc: general at openid.net
Subject: Re: [OpenID] Interoperability problem with OpenID POST response between        myopenid and Google

On May 23, 2009, at 17:34 , Peter Williams wrote:

> I put a large cert (a long string in reality) in myopenid account
> profile. This worked reasonably at the UI, would persist, and indeed
> induced use of the POST binding when the value was asserted. The RP
> was Andrew's .NET library (using his site's demo RP), which
> correctly processed the POST and the large valued attribute. There
> were no signature exceptions reported.

So you're saying that the myopenid implementation is the correct one
and the others (blogger, plaxo, sourceforge) are flawed? I just need
to know which one to test against. :)

André