Closed (duplicate)
Project:
OAuth Connector
Version:
7.x-1.0-beta2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 Apr 2013 at 13:56 UTC
Updated:
7 Jul 2014 at 10:58 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
seghezzou2 commentedI'm having a similar problem. This is an issue from Oauth module. I've attached an small patch that could help you solving this. Enjoy!
Comment #2
Frederic wbase commentedI can confirm that the patch of seghezzou2 does the job!
Thanks
Comment #3
arlina commentedPatch works, thanks!
Comment #4
cramrez commentedPatch works very well, thanks!
Comment #5
pedrospkudos @seghezzou2 !
Maybe this patch should be noticed (if not yet) to Oauth module contributors, and therefore cross-linked with this thread #justsayin'
Comment #6
alexverb commentedI don't know if hardcoding an exception for facebook is the right thing to do here. Isn't oauth supposed to have one general way of doing things? I don't think it will get committed as long as there's no reasoning behind it.
But I've put the status to needs review so the maintainers can have a look at it...
Comment #7
profir90 commentedHi! I have the following error message: Exception: SSL certificate problem, verify the CA That definitely is OK. Details: error: 14445586: SSL routines: SSL3_GET_SERVER_CERTIFICATE: certificate verify failed in DrupalOAuth2Client-> get () (line 119 of D: \ Drupal \ .... \ modules \ contrib \ oauthconnector \ modules \ OAuth2 \ lib \ DrupalOAuth2Client.inc )
Comment #8
hmartens commentedI've been struggling for a week now to get the FB login working to no avail :) But the twitter login works beautifully!
When I try to login, it gives me the
"AUTHORIZATION FINISHED
The application has been authorized" message but I'm still not logged in or taken to a registration page. I also see in the addressbar the following: "/oauth/authorized2/3?error_code=190&error_message=Invalid+OAuth+access+token.#_=_"
Comment #9
tvilms commentedI get the same problem with the FB login not working.
But @hmartens, I'm curious about your comment that "Twitter login works beautifully". If you log out and try to log back in, does it take you right back in? Check that out and if you're seeing something not working after all, then chime in on another thread, http://drupal.org/node/2006212
Some of us are seeing a problem with the Drupal site not "remembering" the Twitter user.
Comment #10
dparvanova commentedI applied the patch from #1.
Now instead of "Invalid OAuth access token." message I am redirected to the user/register page
Comment #11
bojanz commentedCommitted a fix:
http://drupalcode.org/project/oauthconnector.git/commitdiff/42c6f66
Tagging a beta2.
Comment #12
seghezzou2 commentedThanx @pedrosp!!!, I'll do it.
Comment #13
JadH commentedHello All,
I was facing the same issue.
I applied Patch #1.
I got redirected to the Facebook Authentication page, when I clicked ok, I got the below error.
Exception: SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed in DrupalOAuth2Client->get() (line 119 of /Applications/XAMPP/xamppfiles/htdocs/kalabsha/profiles/commerce_kickstart/modules/contrib/oauthconnector/modules/oauth2/lib/DrupalOAuth2Client.inc).Is it related to the change done in #patch1? or is it a separate issue?
Comment #14
bojanz commentedThere's no bug there, you need to have SSL setup on your server if you want to use facebook login (or any other oauth2 based authorization).
Comment #15
coolkid4689 commentedHi everybody. i have some problem about facebook login
this is link after i tried to login commerce kickstart by facebook:
http://localhost/commerce_fb/oauth/authorized2/1?code=AQAEZvhKIDhThzgv7m...
I had run DrupalOAuthClient.inc_.patch of seghezzou2. thanks seghezzou2. i fixed error nvalid OAuth access token.
But when i click facebook login my commerce i get this status Authorization finished. and not logon by account facebook.
Help me!
Comment #16
nevmoor commentedI get the same results as #15!
The patch clears the invalid token error, but now I get sent directly to the Authorization finished page, still not logged in and no user account set up.
I will have to go back and check but I could have sworn I created a couple of accounts on my test AND live sites before this stopped working.
Does this patch really fix the true error, or is it really a patch around?
Comment #17
bojanz commentedbeta2 contains an actual fix. No patch in this issue is valid or ever was.
Comment #18
nevmoor commentedThanks!
Comment #20
Gravitator commentedThank you very much seghezzou2.
I changed the patch for Google, replacing facebook on Google.
Comment #21
bryanmanalo commentedI am currently using beta 2, and I am still experiencing the same error as #15.
More details:
1.) I have followed the drupal commerce video on http://www.drupalcommerce.org/videos/commerce-kickstart-tips/ck-tip-1-so....
2.) I only added curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false) to ~\profiles\commerce_kickstart\modules\contrib\oauthconnector\modules\oauth2\lib\DrupalOAuth2Client.inc because I am just using localhost.
Is anyone else experiencing the same problem?\
**** Update
I traced the code, and it has redirected me to this line. Which is kind of off, because at this line it says, TODO: Add error message http://drupalcode.org/project/oauthconnector.git/blob/53f8a1ec9e4cc24128...
Regards,
Comment #22
mubiesam commentedseems there are still issues, I'm using commerce_kickstart-7.x-2.12 with oauth 7.x-3.1, beta2 is already there...but it always redirected to the user/register page while the callback url is set to oauth/authorized2/1
Comment #23
mubiesam commentedHi,
Will it be conflict to install fboauth-7.x-1.6.zip inside commerce_kickstart-7.x-2.12 ...
Thanks,
Comment #24
BigElsk commentedI'm also having this issue mentioned in #15 with Kickstart. Disabled the block for now waiting for a fix...
Comment #25
xamanu commentedSame error here, as described in #15.
* OAuth 7.x-3.2
* OAuthconnector 7.x-1.0-beta2
* Tried it without success with seghezzou2's patch.
Anyway this is kind of a duplicate of the issue handled in the OAuth module #1981228: Invalid OAuth access token when trying to login using facebook and anything related should be reported there.
Comment #26
Amit Raghav commentedHi All,
I have to perform a load testing for my application containing media steaming contents. for that user first log in to the application. But while validating the script I am getting "Invalid OAuth Request" in response.
This application is Windows Desktop based application.
Please guide me how would I manage this Oauth error.
Request
**********************************
PUT /v3/xauth/access_token.json HTTP/1.1
Host: qa-api.shrbt.com
Connection: keep-alive
Content-Length: 92
Accept: application/json, text/plain, */*
Authorization: OAuth oauth_body_hash=5ElPjvM1y3hJYxtiDq83UYoS4tc%3D,oauth_callback=oob,oauth_consumer_key=urCdB1SIcfB8RvuEJDFUTF4DHt2JPfjlv6TNpItYDP,oauth_nonce=re7EeD7FKFFMERQX,oauth_signature_method=HMAC-SHA1,oauth_timestamp=1410437032,oauth_version=1.0,oauth_signature=2FRDJFURBDsCAg6OO5eZwKz1S5CKA%3D
Content-Type: application/json;charset=UTF-8
Origin: http://web.cdn.eqa.movenetworks.com
User-Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.91 Safari/537.36 SherbetDesktop/3.4.30; CIDishWorld2QA Safari/537.1
Referer: http://web.cdn.eqa.movenetworks.com/gryphon/desktop-env-qa/
Accept-Encoding: gzip,deflate
Accept-Language: en-us,en
Accept-Charset: iso-8859-1,*,utf-8
{"email":"**********","password":"******","device_guid":"48498b04-37f5-11e4-8000-000000000000"}
Response
*********************************************
HTTP/1.1 401 Unauthorized
Server: nginx/1.0.14
Date: Thu, 18 Sep 2014 05:08:58 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Status: 401 Unauthorized
X-UA-Compatible: IE=Edge,chrome=1
Cache-Control: no-cache
X-Request-Id: 336c60cb658f1a5e6ea4287f3f97f4f7
X-Runtime: 0.039976
X-Rack-Cache: invalidate, pass
Invalid OAuth Request
Thanks
Amit