search

Laith- / lightopenid

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

can't get it to work with pip.versisignlabs.com #34

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
I've installed lightopenid and successfully used it with three openID providers 
(including Yahoo, myid.net and one which I installed a provider library on), 
but I get an error (below) when trying to use it with Symantec's 
pip.versignlabs.com provider.

If I enter my openID (https://<myid>.pip.verisignlabs.com) the error arises 
immediately; if I use the generic address http://pip.verisignlabs.com and then 
login, the error is the same but on return from the remote login.

[Tue Apr 12 11:54:52 2011] [error] [client 86.26.13.165] PHP Fatal error:  
Uncaught exception 'ErrorException' with message 'error:14077458:SSL 
routines:SSL23_GET_SERVER_HELLO:reason(1112)' in 
/home/ensembling/DevV3/www/lightopenid/openid.php:193\nStack trace:\n#0 
/home/ensembling/DevV3/www/lightopenid/openid.php(292): 
LightOpenID->request_curl('https://...', 'GET', Array)\n#1 
/home/ensembling/DevV3/www/lightopenid/openid.php(431): 
LightOpenID->request('https://...', 'GET')\n#2 
/home/ensembling/DevV3/www/lightopenid/openid.php(651): 
LightOpenID->discover('https://...')\n#3 
/home/ensembling/DevV3/www/lightopenid/openidreturn.php(11): 
LightOpenID->validate()\n#4 {main}\n  thrown in 
/home/ensembling/DevV3/www/lightopenid/openid.php on line 193, referer: 
https://pip.verisignlabs.com/dataExchange?target=render&identityName=...

FYI this is PHP5.3.3-7 and the php curl library reports 7.21.0 and libssh2/1.2.5

Original issue reported on code.google.com by david.j....@gmail.com on 12 Apr 2011 at 11:14

GoogleCodeExporter commented 9 years ago 
I did some research, and then apparently forgot to write the results here. 
Sorry about that.

Anyway, what you've got is an error from the cURL library, so I can't really do 
anything about it. However, I've searched for more information about that, but 
while there were some questions asked about that, there were no answers. 
Perhaps you should try to do the same thing from a console version of curl? In 
order to find the url that causes problems, simply add an `echo $url;` to the 
request() method.

You could also try disabling curl support in LightOpenID. It's currently only 
possible by removing the call to request_curl in request method. The best way 
to test that would be to disable curl support in php altogether, because 
otherwise it might be used even with streams.

Original comment by mewp...@gmail.com on 21 Apr 2011 at 7:07