search

starena / jopenid

Automatically exported from code.google.com/p/jopenid
0 stars 0 forks source link

Verify signature failed because of umlaut #15

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Log into Google or Yahoo with a account where the (Last)Name has a umlaut.

What is the expected output? What do you see instead?
The login should work but instead the verification of the singature fails
and the excetion "org.expressme.openid.OpenIdException: Verify signature 
failed." is thrown.

What version of the product are you using? On what operating system?
jopenid 1.08,
JavaScript and Servlets,
Tomcat 6.0.29 and Tomcat 7.0.4

Original issue reported on code.google.com by a.fl...@gmail.com on 25 Nov 2010 at 10:53

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I'm not sure the umlaut is the problem or not but one thing is certain...
In some cases the return signature and "calculated" hash are not the same.
On my windows machine (Win 7 with JDK 1.6.0_26 works on), on test server where 
we use this (Ubuntu with JDK 1.6.0_25) fails for the same username / password.

Original comment by nd7...@gmail.com on 21 Jun 2011 at 2:14

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Hello. For all who are still interested in this bug, I had success by modifying 
the Tomcat connector settings. I add in the Tomcat connector the following a 
UTF-8 encoding (the URIEncoding="UTF-8"):
<Connector port="8080" protocol="HTTP/1.1" URIEncoding="UTF-8"
 connectionTimeout="20000" redirectPort="8443" />
This solved the problem I had.

P.S. The example is for http connector (port 8080). Be sure you modify the 
right connector. If, for some reasons you cannot do that, try to find a filter 
that may set this particular request to UTF-8.

Original comment by nd7...@gmail.com on 22 Jun 2011 at 2:18

GoogleCodeExporter commented 8 years ago 
it still doesn't work.  The "Verify signature fails" exception is encountered 
too often these days.  I remember it went very well previously. But I don't 
know why.

PS:  I always keep the URIEncoding configuration but it still doesn't work

Original comment by daochaic...@gmail.com on 18 Oct 2011 at 3:24