> Next I tried using a Yahoo OpenID, but the
> Yahoo site reports the following error at URL:
>
> https://open.login.yahooapis.com/openid/op/auth?openid.ns=http%3A%2F
> %2Fspecs.openid.net%2Fauth%2F2.0&openid.claimed_id=http%3A%2F%
> 2Fspecs.openid.net%2Fauth%2F2.0%
> 2Fidentifier_select&openid.identity=http%3A%2F%2Fspecs.openid.net%
> 2Fauth%2F2.0%2Fidentifier_select&openid.return_to=http%3A%2F%
> 2Ftest.galway.net%3A8080%2FGalwayNet%2Fjsp%2Fcustomer%2Flogin-
> openid.jsp&openid.realm=http%3A%2F%2Ftest.galway.net%3A8080%
> 2FGalwayNet%2Fjsp%2Fcustomer%2Flogin-
> openid.jsp&openid.assoc_handle=XKcVelLGqAhv8IhW83aFTCmDxTkOvY8jicQEa6_
> ZF2C74FPaGpbLFakrAlzq9Mi4eYKLKJ2mgPyP6Ms3nxZLlkrSlKhfGs2SU6nGgRsa8g26R
> dxLNm92B0gRlNeI0x.d1A--&openid.mode=checkid_setup
This request seems to be a v2 request (judging from the presence of
the claimed_id and realm params), but it's missing the openid.ns
namespace declaration.
Yahoo only supports OpenID 2.0, so I believe this is the cause of the
failure, while myopenid falls back to v1 when it doesn't see the
namespace.
Johnny
>
>> This request seems to be a v2 request (judging from the presence of
>> the claimed_id and realm params), but it's missing the openid.ns
>> namespace declaration.
>
> I just looked at that URL again and it does have a:
> openid.ns=http://specs.openid.net/auth/2.0
> parameter (it's the first parameter in the URL). So can that really
> be the problem?
You're right, I missed the openid.ns - it is there indeed.
Next thing I notice is the claimed_id : identifier_select; maybe
Yahoo is not supporting this feature, so I suggest you try with
"me.yahoo.com" as they recomment.
Also, Allen Tom just posted on the openid list their support contact;
you may want to let them know as well.
openid-...@yahoo-inc.com
http://openid.net/pipermail/general/2008-January/004024.html
Johnny