User can't login becasue of ParseException related to AuthData

[rafapetter]

Issue
Every time I try to login through username/password with a user that was already created on Parse API (before the migration to mongo), I get a ParseException of code -1: java.lang.ClassCastException: org.json.JSONObject$1 cannot be cast to java.util.Map. The debug trace points to line 340 of ParseUser.java:

339  private Map<String, String> getAuthData(String authType) {
340      return getAuthData().get(authType);
341  }

Prerequisites

• I've migrated to AWS Elastic Beanstalk(64bit Amazon Linux 2015.09 v2.0.7, running Node.js 4.2.3) and MongoLab
• I'm running the 2.1.4 of Parse Server.
• I'm testing on Android SDK

Steps to reproduce on Android

• I've changed the endpoint from parse API to my parse server
• Installed the app
• Tried to login with existing user

Log from Verbose
Here we can see that GET actually returns successfully

GET /parse/login { host: 'parseserver-xxxx-env.elasticbeanstalk.com',
  'x-real-ip': 'xxxx',
  'x-forwarded-for': 'xxxxx',
  'content-length': '61',
  'accept-encoding': 'gzip',
  'content-type': 'application/json',
  'user-agent': 'Parse Android SDK 1.13.0 (com.xxxx.xxxx/7) API Level 21',
  'x-newrelic-id': 'xxxx==',
  'x-parse-app-build-version': '7',
  'x-parse-app-display-version': '1.1.3.2',
  'x-parse-application-id': 'xxxx',
  'x-parse-client-key': 'xxx',
  'x-parse-client-version': 'a1.13.0',
  'x-parse-installation-id': 'xxxx',
  'x-parse-os-version': '5.0.2',
  'x-forwarded-port': '80',
  'x-forwarded-proto': 'http' } {
  "username": "xxx@xxxx.com",
  "password": "xxxx"
}
response: {
  "response": {
    "objectId": "xxxxxxxx",

Possible Similar Issues

• Can/Should user.authData.anonymous ever be null? #639

[gfosco]

What is the rest of the response? It is cut off..

[rafapetter]

I'm sorry, here's the GET again. I've covered sensitive data and only removed app custom fields on the response:

GET /parse/login { host: 'parseserver-xxx-env.elasticbeanstalk.com',
  'x-real-ip': 'xxxxx',
  'x-forwarded-for': 'xxxx',
  'content-length': '61',
  'accept-encoding': 'gzip',
  'content-type': 'application/json',
  'user-agent': 'Parse Android SDK 1.13.0 (com.xxx.xxx/7) API Level 21',
  'x-newrelic-id': 'xxxxx==',
  'x-parse-app-build-version': '7',
  'x-parse-app-display-version': 'xxxx',
  'x-parse-application-id': 'xxxxx',
  'x-parse-client-key': 'xxxxx',
  'x-parse-client-version': 'a1.13.0',
  'x-parse-installation-id': 'xxxxx',
  'x-parse-os-version': '5.0.2',
  'x-forwarded-port': '80',
  'x-forwarded-proto': 'http' } {
  "username": "xxxxx@xxxxx.com",
  "password": "xxxxxxxxxx"
}
response: {
  "response": {
    "objectId": "xxxxx",
    "email": "xxxxx@xxxxx.com",
    "updatedAt": "2016-03-07T16:37:11.246Z",
    "username": "xxxxx@xxxxx.com",
    "sessionToken": "r:xxxxxxx",
     "createdAt": "2015-11-16T05:15:26.288Z",
    "email_verified": false,
    "authData": {
      "facebook": null
    }
  }
}

[rafapetter]

One other difference I've found is that the response for new users have ACL returned:

"ACL": {
        "XXXXXX": {
            "read": true,
            "write": true
        },
        "*": {
            "read": true
        }
    },

And old users don't. On mongodb don't even have the _rperm and _wperm columns

[flovilmart]

@weengo does the fix provided in #952 solves the issue. It seems that the Facebook: null may be causing the issue

[rafapetter]

I was just about to comment on this. Nope, even testing locally didn't solve. Should I erase mongodb and migrate again to see if there's a problem with ACL fields being missed?

[rafapetter]

You're right, I've just removed "_auth_data_facebook": null from mongodb, and when tried to access again, it did work. So, that was a case of a user that had sign up as username/password, then later had facebook account linked, and finally have facebook unlinked. So, is that a scenario covered by parse-server?

[flovilmart]

Alright, I'm adding a fix to cleanup those null keys in login

[rafapetter]

Great, thanks

[flovilmart]

Do you have that on many users? Was the user like that just after the migration?

[rafapetter]

We have an ID Verification process, so some users may link their facebook accounts to increase ID verification. But we have very few that link and then unlink.

The user was like that before the migration. Haven't been updated since.

[flovilmart]

I've checked and the JS SDK handles it properly, maybe the fix should be in the android SDK.