some openId urls don't work in the example server.

[psortino]

I'm a beginner on this, but when I was tested the server joid.war I
noticed the following.:

It's working with:
- myopenid: username.myopenid.com
- clamid: username.clamid.com

It's not working with:
- wordpress: username.wordpress.com
- yahoo: yahoo.com

Questions:
Is this an error in the joid code?
if not what can i do to make the server work correctly with every
openid urls?

Cheers,
Pablo.

[todkap]

I am able to reproduce the issue with yahoo.com.

The problem appears to be on yahoo's side


One of the association response parameters (dh_server_public) that is
being returned is not Base64 encoded (I am seeing '3' as a value) and
thus causes problems during the parsing the association response.

Diffie-Hellman Response Parameters

* dh_server_public

Value: base64(btwoc(g ^ xb mod p))

Description: The OP's Diffie-Hellman public key.


I am trying to find out how to report this to yahoo but have not been
successful. Any thoughts???

[Travis Reeder]

Good find. Not sure how you can contact them, but you can probably find a mailing list/yahoo group or something from here: http://developer.yahoo.com/openid/ that the yahoo developers would be on.

Travis

[tod...@us.ibm.com]

>It's not working with:

>- yahoo: yahoo.com
>Questions:
>Is this an error in the joid code?

I was able to work with an engineer at Yahoo to at least get me
started in the right direction. There were a couple of changes I made
to the JOID code to get this to work. I opened a bug for this (http://
code.google.com/p/joid/issues/detail?id=18) with the proposed
solution. The major changes were to the response params that are
signed and to add support for openid2.provider in addition
openid.server.