Facebook Login error: "[Error]: this auth is already used"

[meilers]

I'm using parse-server on AWS Elastic beanstalk with MongoLab and I'm getting this error when I login using Facebook:

[Error]: this auth is already used (Code: 208, Version: 1.12.0)

When I create the user via Facebook, everything is fine, but when I logout and then re-login again using Facebook I get the error.

Any ideas?

EDIT: It seems the user is created twice in the DB (one has the email, the other doesn't)

EDIT2: This error was also happening on parse.com, but more as a warning: "[Error]: Another user is already linked to this facebook id. (Code: 208, Version: 1.10.0)". This happens if the user logs out - which creates a new anonymous user - and then relogs in with Facebook. But a duplicate user was never created on parse.com. It is however created here with Parse Server.

[natario1]

So you logout, create an anonymous user (which is the second entry there) and then link it with facebook? You should handle that yourself. However I agree that if it returns 208, parse-server should not save invalid auth data in the unlinkable user.

[drew-gross]

This looks like bug potentially related to some recent changes in anonymous users. @steven-supersolid do you mind taking a look?

[steven-supersolid]

I can take a look next week but looks like the issue was opened before the changes in #341 were merged.

@meilers would you mind clarifying the repro steps and version of parse-server this occurs in? I would like to narrow down the issue to Facebook login, anonymous login or Facebook linking. The error message seems to indicate this is an issue with linking though. If you post more of the authData screenshot then will be able to see if there is any anonymous authData,

[drew-gross]

OK, if you think it's not related to your changes thats fine and we can do our own investigation.

[gfosco]

Since a good number of things have changes in the user/auth space, please re-open if you're still experiencing this with 2.1.2.

[LBKevinSibue]

Hi everyone !
Yesterday I have updated my parse-server to the latest version and now when I call a CloudCode function from my app (iOS or Android) it's say to me there are an error.

So when I look at the log I can see that:

[31merror�[39m: Error generating response. ParseError { code: 208, message: 'this auth is already used' } code=208, message=this auth is already used

and that:

31merror�[39m: Error generating response. [TypeError: Cannot read property 'getSessionToken' of undefined]
�[31merror�[39m: Uncaught internal server error. [TypeError: Cannot read property 'getSessionToken' of undefined] TypeError: Cannot read property 'getSessionToken' of undefined
at /var/app/current/cloud/event.js:74:33
at /var/app/current/node_modules/parse-server/lib/triggers.js:249:26
at new Promise (/var/app/current/node_modules/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:191:7)
at Object.maybeRunTrigger (/var/app/current/node_modules/parse-server/lib/triggers.js:228:10)
at RestWrite.runAfterTrigger (/var/app/current/node_modules/parse-server/lib/RestWrite.js:875:19)
at /var/app/current/node_modules/parse-server/lib/RestWrite.js:107:18
at run (/var/app/current/node_modules/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:87:22)
at /var/app/current/node_modules/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:100 :28
at flush (/var/app/current/node_modules/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/_microtask.js:18:9)
at nextTickCallbackWith0Args (node.js:420:9)
TypeError: Cannot read property 'getSessionToken' of undefined
at /var/app/current/cloud/event.js:74:33
at /var/app/current/node_modules/parse-server/lib/triggers.js:249:26
at new Promise (/var/app/current/node_modules/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:191:7)
at Object.maybeRunTrigger (/var/app/current/node_modules/parse-server/lib/triggers.js:228:10)
at RestWrite.runAfterTrigger (/var/app/current/node_modules/parse-server/lib/RestWrite.js:875:19)
at /var/app/current/node_modules/parse-server/lib/RestWrite.js:107:18
at run (/var/app/current/node_modules/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:87:22)
at /var/app/current/node_modules/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:100 :28
at flush (/var/app/current/node_modules/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/_microtask.js:18:9)
at nextTickCallbackWith0Args (node.js:420:9)

Do you know what I need to do to correct that ?

[flovilmart]

can you post the content of your cloud function? As well as the logs printed in the console with VERBOSE=1 environment variable set when you start your server?

[LBKevinSibue]

This error appear for example, when I call the cloud function "participateIntoEvent":

[31merror�[39m: Failed running cloud function participateIntoEvent for user XwDt4J1yXH with:
Input:
(if you want to search in the log).

It's seem like if the user is not log (still a anonymous user) and so the server can't get the session token, but I don't understand why.

Any idea ?

ParseServer - Error ParticipateIntoEvent.pdf
nodejs.pdf

[flovilmart]

Can you isolate the relevant logs? Also, given the complexity/size of your function it's really tough to understand what's going on. You should probably try to reduce the size of that cloud function to isolate the failing part.

[LBKevinSibue]

Important logs are from my previous post:

[31merror [39m: Error Generating response. ParseError {code: 208 Message: 'this auth is already used'} = 208 code, message = this auth is already used

This appears each time a user.

And each call of function cloudcode using 'getSessionToken ()' I have this error:

31merror [39m: Error Generating response. [TypeError: Can not read property 'getSessionToken offi undefined]
[31merror [39m: Uncaught internal server error. [TypeError: Can not read property 'getSessionToken offi undefined] TypeError: Can not read property' getSessionToken offi undefined
at /var/app/current/cloud/event.js:74:33
at /var/app/current/node_modules/parse-server/lib/triggers.js:249:26
at New Promise (/var/app/current/node_modules/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:191:7)
at Object.maybeRunTrigger (/var/app/current/node_modules/parse-server/lib/triggers.js:228:10)
at RestWrite.runAfterTrigger (/var/app/current/node_modules/parse-server/lib/RestWrite.js:875:19)
at /var/app/current/node_modules/parse-server/lib/RestWrite.js:107:18
Has run (/var/app/current/node_modules/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:87:22)
/var/app/current/node_modules/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:100 at 28
Has flush (/var/app/current/node_modules/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/_microtask.js:18:9)
at nextTickCallbackWith0Args (node.js: 420: 9)
TypeError: Can not read property 'getSessionToken offi undefined
at /var/app/current/cloud/event.js:74:33
at /var/app/current/node_modules/parse-server/lib/triggers.js:249:26
at New Promise (/var/app/current/node_modules/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:191:7)
at Object.maybeRunTrigger (/var/app/current/node_modules/parse-server/lib/triggers.js:228:10)
at RestWrite.runAfterTrigger (/var/app/current/node_modules/parse-server/lib/RestWrite.js:875:19)
at /var/app/current/node_modules/parse-server/lib/RestWrite.js:107:18
Has run (/var/app/current/node_modules/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:87:22)
/var/app/current/node_modules/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/es6.promise.js:100 at 28
Has flush (/var/app/current/node_modules/parse-server/node_modules/babel-polyfill/node_modules/core-js/modules/_microtask.js:18:9)
at nextTickCallbackWith0Args (node.js: 420: 9)

I think the connection goes wrong (to view the error 'auth already used') but I do not know why.

[flovilmart]

This error occurs when you're trying to save a user with auth data that doesn't belongs to him. I don't see any logs referring to that.

Also, the session token seems properly passed to the request to your cloud code function, therefore the user should be properly set in req.user. If req.user is set, you should not have the crash you're describing.

Also, because your function is so big, I can't possible write a test to make sure this can't reproduce in the future.

So please, try to isolate the error and the relevant logs, and when I say relevant it's the full trace that leads to the issue. If req.user is never set in your cloudCode, you should be able to write a simple cloud function that shows it.

[flovilmart]

Also, in the first page of your logs, you can see a user getting fetched with the Facebook authData with the Facebook ID 891415857609934. Then a few pages later, another user (with a different objectId) is trying to link it's account with the same Facebook ID. That's why you see that 'auth already used' error. You should not try to link 2 accounts with the same authData. I'm not sure what you're doing in the client, probably log out, create a new anonymous user and then link to the same Facebook Account. So far it looks like a problem in the client, not the server