Getting 401 on /identity example

[bartve]

Getting 401 on /identity example

[bartve]

Does it work with Discogs Auth as the authentication method?

[sampotts]

Apologies for my lack of knowledge but how would I do that?

[bartve]

Like this: https://www.discogs.com/developers/#page:authentication,header:authentication-discogs-auth-flow

[sampotts]

So does the identity example no longer work then? I was just following the readme. Is it out of date?

[sampotts]

I think this was closed by mistake? It's still not working. Could you maybe try the examples? The identity example does not work.

[bartve]

Oops, I didn't mean to close this indeed! Probably clicked the wrong button. Sorry! I will probably have time to look into this tomorrow.

[sampotts]

Cheers! I'm trying to help a mate out by building him an app and stuck at the moment :-(

On 13 Jun 2016, at 6:39 AM, Bart [email protected] wrote:

Oops, I didn't mean to close this indeed! Probably clicked the wrong button. Sorry! I will probably have time to look into this tomorrow.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[bartve]

I did some tests and I don't seem to be able to reproduce the issue. Are you sure the access token is correctly persisted and passed? The OAuth flow is quite complicated and you must pass the final access token and not a token from an earlier step. Both Discogs Auth and OAuth authentication in combination with the identity endpoint seem to be working fine here. I also would have expected others to complain if this was broken.

[sampotts]

Thanks for taking a look. I'll send some more info when I get home.

On 14 Jun 2016, at 7:52 AM, Bart [email protected] wrote:

I did some tests and I don't seem to be able to reproduce the issue. Are you sure the access token is correctly persisted and passed? The OAuth flow is quite complicated and you must pass the final access token and not a token from an earlier step. Both Discogs Auth and OAuth authentication in combination with the identity endpoint seem to be working fine here. I also would have expected others to complain if this was broken.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[sampotts]

I'm using cookie-session to persist the accessData and requestData:

cookieSession = require('cookie-session');

app.use(cookieSession({
    keys: ['key1', 'key2']
}));

and then I store what's returned in accessData as below in the callback after oauth:

// Persist "accessData" here for following OAuth calls 
req.session.accessData = accessData;

console.log(accessData === req.session.accessData) straight after returns true as does console.log(dis.authenticated()). accessData returns the following (some parts hidden):

{ 
  method: 'oauth',
  level: 0,
  consumerKey: '...',
  consumerSecret: '...',
  token: '...',
  tokenSecret: '...',
  authorizeUrl: 'https://www.discogs.com/oauth/authorize?oauth_token=...' 
}

In the method that uses getIdentity a console.log(req.session.accessData) returns the same as above but it still doesn't seem to authenticate. I tried passing the token and tokenSecret properties rather than the whole object but it didn't seem to work either...

Which seems to be very similar to the requestData used in the earlier step? Sorry if it's a little confusing. I can send you the server.js file if it helps.

[sampotts]

OK, I figured it out. It was earlier in the process. Getting the access token was actually failing silently (as I wasn't checking the err argument value) due to the oauth_verifier query parameter being missing. It was because I wasn't accessing the query property when parsing the URL:

var query = url.parse(req.url, true).query;

Sorry about all this. Thanks for looking into it for me though 👍

[bartve]

No problem. Glad you got it to work 👍

[codecreate]

Hi. I just found this exampe of a similar problem I'm having. I'm using the oAuth method and it's working fine up until trying the /identity test. The flow completes succesfully bringing me back to my app succesfully but I get a 401 auth error on /identity and when I investigate I discover that the accessData that I persisted in the /callback is the same as the requestData that I persisted in the /authorise. I'm persisting both those objects in app.locals. Any idea why they are the same? Neither the /authorise or /callback return any err.

Thanks