Error when trying to run the test_oauth_client.js #16

Open
sanjib75 opened this Issue Oct 24, 2010 · 2 comments

Comments

Projects
None yet
3 participants
@sanjib75

Hi

When I try to run node test_oauth_client.js, everyhting starts up fine.
$ node test_oauth_client.js

24 Oct 23:08:04 - oauth : { _requestUrl: 'http://localhost:3000/oauth/request_token'
, _accessUrl: 'http://localhost:3000/oauth/access_token'
, _consumerKey: 'JiYmll7CX3AXDgasnnIDeg'
, _consumerSecret: 'mWPBRK5kG2Tkthuf5zRV1jYWOEwnjI6xs3QVRqOOg'
, _version: '1.0A'
, _authorize_callback: 'http://localhost:3000/oauth/callback'
, _signatureMethod: 'HMAC-SHA1'
, nonceSize: 32
, headers:
{ Accept: '
/
'
, Connection: 'close'
, 'User-Agent': 'Node authentication'
}
}

But when I try to access it thro URL, it gives me this in the URL value
http://localhost:3000/oauth/authorize?oauth_token=undefined

And I see in my logs
{ lastAccess: 1287958084173
, oauth_token_secret: undefined
}

What am I missing here? I am trying to be an oauth provider for my site.

Thanks,
Sanjib

@ciaranj

This comment has been minimized.

Show comment
Hide comment
@ciaranj

ciaranj Oct 28, 2010

Owner

Hmm, I'm not sure that test_client, is paired with the test_server in the examples folder, can you give me more details ?

Owner

ciaranj commented Oct 28, 2010

Hmm, I'm not sure that test_client, is paired with the test_server in the examples folder, can you give me more details ?

@andrewluetgers

This comment has been minimized.

Show comment
Hide comment
@andrewluetgers

andrewluetgers Aug 7, 2011

I have seen alot of this and there needs to be some better error messages to help us out here i think. maybe a debug mode that would throw a stack in such a case. At any rate i had this happened in my oAuth provider because i neglected to place the body parser above the auth section of the express.createServer call, moving the bodyparser to come before auth fixed it for me in one case. Im now seeing this problem now that I put an nginx proxy infront of things... ugh soo hard to debug :-(

Im also using the following to setup routes, im wondering if this is the culprit?

app.configure(function() {
app.use(app.router);
});

I have seen alot of this and there needs to be some better error messages to help us out here i think. maybe a debug mode that would throw a stack in such a case. At any rate i had this happened in my oAuth provider because i neglected to place the body parser above the auth section of the express.createServer call, moving the bodyparser to come before auth fixed it for me in one case. Im now seeing this problem now that I put an nginx proxy infront of things... ugh soo hard to debug :-(

Im also using the following to setup routes, im wondering if this is the culprit?

app.configure(function() {
app.use(app.router);
});

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment