Invalid signature about node-openid HOT 4 CLOSED

I have this issue also except I have it with Gmail, have not had a chance to try it with other OpenID providers. I found that if I use the OpenID stateless authentication method that this issue goes away. To do this when you are creating the OpenId RelyingParty just send in true for the stateless parameter instead of false.

from node-openid.

I have reproduced the issue and isolated it to be a problem with the binary encoding of large integers.

As a workaround, stateless mode will work since it avoids association (at the cost of an additional HTTP request per authentication).

from node-openid.

So, we switched to the stateless approach... but indeed, if there is any way to avoid that extra HTTP request, that'd be amazing.
Thanks

from node-openid.

Fixed in HEAD.

from node-openid.