Introduction
Frequently added questions
I'm getting problems with SSL.
If you are getting "Exception CURL error: SSL certificate problem, verify that the CA cert is OK" or similar, that indicates problem with the remote SSL certificate.
To fix this, you should just pass array(CURLOPT_SSL_VERIFYPEER => false) as the $curl_options parameter in OAuthRequester::requestRequestToken.
I don't have CURL, what do I do?
You need CURL installed to use this library, sorry. There's no workaround.
I am not having cURL on my server and cannot install it. How to use the OAuth - Consumer and Server library for PHP?
Getting the SSL exception described above, but the supplied twitter example http://code.google.com/p/oauth-php/source/browse/trunk/example/client/twoleggedtwitter.php doesn't call OAuthRequester::requestRequestToken directly, and $result = $request->doRequest(0, $curl_options); has no effect. Any help greatly appreciated.
As of version 175, $result = $request->doRequest(0, array(CURLOPT_SSL_VERIFYPEER => false)); does work and fix the SSL execption on the twoleggedtwitter.php sample script.
I'm very new at coding. I extracted and copied the folder structure of oauth-php-175.tar.gz to my server (Bluehost) and am accessing http://myserver.com/oauth-php/example/client/twolegged.php.
I get merely "Exception".
If I try http://myserver.com/oauth-php/example/client/twoleggedtwitter.php I get "ExceptionRequest? failed with code 401: Failed to validate oauth signature and token".
Where do I go from here? I am trying to authorize users for the Gmail API.
Hi everyone, I just tried an example (twoleggedtwitter.php) and I had the following error : "ExceptionCURL error: Could not resolve host: twitter.com; No data record of requested type". I'm using the last release revision 175. Any idea ?
Is this OAuth Code supports 1.x OAuth Version or 2.0 OAuth Version?
in PHP google api i fixed this problem by changing line 115 in apiCurlIO.php Like this: curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
Guys, I'm not sure if not verifying the destination is a good idea - this is what SSL is created for, to avoid the man-in-the-middle attacks, if you just ignored the CA authority or "it is OK to have problems with remote SSL certificate" then you kind-of killing the whole idea of SSL, don't you?