Unexpected behavior when logging in

[cdcme]

I've been looking at this issue for a couple of days now. I thought at first that I might be losing my marbles, so I rebuild the app from scratch to see if I could isolate what's going on. Following the documentation on authenticating users, I tried to do exactly the same thing and got back a totally different result.

curl -X POST -H "Content-Type:application/json" \   
> -d '{"email": "somebody@somedomain.com", "password":"password", "ttl": 1209600000}' \
> http://localhost:3000/v1/users/login

Result:

{
  "id": "XeXMzum40E9Gi8jY3OJIL1qRoXySiyLEG29OUhJi0dPt92Gbzl72ZMrsvg6v4DpK",
  "ttl": 31556926,
  "created": "2014-06-26T22:53:48.271Z"
}

So, not only is it not associating a token with a userId like it does in the example given in the docs, but it's also messing with the TTL value. This is on a fresh project created via slc lb project myApp.

My slc -v output:

strong-cli v2.5.5 (node v0.10.29)
node-inspector v0.7.4
strong-build v0.1.0
strong-cluster-control v0.4.0
strong-registry v1.1.0
strong-supervisor v0.2.3 (strong-agent v0.4.9, strong-cluster-control v0.4.0)

My package.json:

{
  "version": "0.0.1",
  "main": "app.js",
  "bin": "server.js",
  "scripts": {
    "start": "node app.js"
  },
  "dependencies": {
    "lodash": "^2.4.1",
    "loopback": "1.x >=1.7.0",
    "loopback-connector-mongodb": "^1.4.0",
    "loopback-datasource-juggler": "^1.6.1",
    "moment": "^2.7.0"
  },
  "optionalDependencies": {
    "loopback-explorer": "~1.1.0",
    "loopback-push-notification": "~1.2.0"
  },
  "name": "myApp"
}

[karlmikko]

@carlodicelico The default user model when creating the accessToken has a maxTTL setting

User.prototype.createAccessToken = function(ttl, cb) {
  var userModel = this.constructor;
  ttl = Math.min(ttl || userModel.settings.ttl, userModel.settings.maxTTL);
  this.accessTokens.create({
    ttl: ttl
  }, cb);
};

DEFAULT_MAX_TTL = 31556926 which is exactly what you are seeing. To allow this to be larger change the maxTTL setting in models.json.

{
    "name": "Users",
    "options": {
         "maxTTL": 1209600000
    }
}

[karlmikko]

@carlodicelico with regard to the userId not being associated, I suspect that in your models.json the relations are not set in both directions.

More specifically, I think you have the Users relations with hasMany to the accessToken but no foreignKey defined.

Can you please post your models.json?

[cdcme]

@karlmikko regarding the TTL, thanks! I did not know that. I looked right at that code, too, and just didn't see it! Anyway, changing the maxTTL did the trick. As far as the associations, I did have the hasMany association specified with the foreignKey defined but did not have a belongsTo relation specified the other way. However, I did add that relation and tested and still get the same result:

Request:

curl -X POST -H "Content-Type:application/json" \                                                          [Genetrix 8:57 PM]
-d '{"email": "somebody@somedomain.com", "password":"password", "ttl": 1209600000}' \
http://localhost:3000/v1/users/login

Response:

{
  "id": "j1PrbKtq38QBl3Yyn9yDN1772ZRPPwZXfLjKAgytXgyDwq9IAZpuhtNmW4WRS8nT",
  "ttl": 1209600000,
  "created": "2014-06-27T00:58:38.932Z"
}

Relevant part of models.json:

"user": {
    "dataSource": "mongo_dev",
    "public": true,
    "options": {
      "base": "User",
      "maxTTL": 9999999999,
      "relations": {
        "accessTokens": {
          "model": "accessToken",
          "type": "hasMany",
          "foreignKey": "userId"
        }
      }
    }
  },
  "accessToken": {
    "dataSource": "mongo_dev",
    "public": true,
    "options": {
      "base": "AccessToken",
      "relations": {
        "users": {
          "model": "user",
          "type": "belongsTo",
          "foreignKey": "userId"
        }
      }
    }
  }

[karlmikko]

@carlodicelico I have been stuck in the past with the case of model names in relations. Try defining your relations with "model":"User".

If you look at the loopback explorer http://0.0.0.0:3000/explorer it shows you the relations it resolved.

[cdcme]

@karlmikko Yeah, I tried using "model":"User" but no luck. I run the app using DEBUG=loopback:* nodemon app so I can see all the debugging output and I can see the request, it finds my user record and so forth but the userId is always undefined. So, it definitely seems like an association problem. I checked Explorer and it looks like the relations are being set up properly, though. Very strange!

loopback:security:access-context ---AccessRequest--- +0ms
  loopback:security:access-context  model user +0ms
  loopback:security:access-context  property login +0ms
  loopback:security:access-context  accessType EXECUTE +0ms
  loopback:security:access-context  permission ALLOW +0ms
  loopback:security:access-context  isWildcard() false +0ms
  loopback:security:access-context  isAllowed() true +0ms
  loopback:connector:mongodb all +8ms user { where: { email: 'somebody@somedomain.com },
  limit: 1,
  offset: 0,
  skip: 0 }
  loopback:connector:mongodb all +1ms user { where: { email: 'somebody@somedomain.com' },
  limit: 1,
  offset: 0,
  skip: 0 } null [ { _id: 53ac6b617772b1d7f47aac41,
    username: 'Carlo DiCelico',
    password: '$2a$10$E8UrnhQ4FtOMse0pvEcuI.q1dx22RKuK5hpYuo4ZXMXVYwNoO.fUe',
    email: 'somebody@somedomain.com',
    emailVerified: true,
    created: Thu Jun 26 2014 14:50:09 GMT-0400 (EDT),
    settings: {},
    profile: {} } ]
  loopback:connector:mongodb create +222ms accessToken { id: '1JuO36qrGAaG0KqWAsPuywQrYrzR4y40NC998EMD49mFN8BB1zANDeer1PdVYFdn',
  ttl: 1209600000,
  created: Thu Jun 26 2014 21:23:02 GMT-0400 (EDT),
  userId: undefined }
  loopback:connector:mongodb create.callback +1ms accessToken null [ { ttl: 1209600000,
    created: Thu Jun 26 2014 21:23:02 GMT-0400 (EDT),
    userId: undefined,
    _id: '1JuO36qrGAaG0KqWAsPuywQrYrzR4y40NC998EMD49mFN8BB1zANDeer1PdVYFdn' } ]
POST /v1/users/login 200 236ms - 140b

[karlmikko]

@carlodicelico you have me stumped now also! The userId is set as part of the related model. The fact it shows them is really odd!

do me a favour and rename your models to be the same name as the Base name.

{
"User": {
    "dataSource": "mongo_dev",
    "public": true,
    "options": {
      "base": "User",
      "maxTTL": 9999999999,
      "relations": {
        "accessTokens": {
          "model": "AccessToken",
          "type": "hasMany",
          "foreignKey": "userId"
        }
      }
    }
  },
  "AccessToken": {
    "dataSource": "mongo_dev",
    "public": true,
    "options": {
      "base": "AccessToken",
      "relations": {
        "users": {
          "model": "User",
          "type": "belongsTo",
          "foreignKey": "userId"
        }
      }
    }
  }
}

[cdcme]

When I try that, I get loopback:user No matching record is found POST /v1/users/login 401 for the same request:

curl -X POST -H "Content-Type:application/json" \                                                          
-d '{"email": "somebody@somedomain.com", "password":"password", "ttl": 1209600000}' \
http://localhost:3000/v1/users/login

[karlmikko]

/to: @bajtos
/to: @raymondfeng

Can you help on why the userId isn't being created on the accessToken from Users.login with the mongo connector?

[raymondfeng]

We ran into a similar issue and had a theory. I'll reproduce and confirm.

Sent from my iPhone 5

On Jun 26, 2014, at 7:04 PM, Karl Mikkelsen notifications@github.com wrote:

/to: @bajtos
/to: @raymondfeng

Can you help on why the userId isn't being created on the accessToken from Users.login with the mongo connector?

—
Reply to this email directly or view it on GitHub.

[karlmikko]

@carlodicelico just realised that the foreignKey set for accessToken relations to users should be id not userId.

[karlmikko]

#354 (comment)
same issue i suspect?

[karlmikko]

nice find @raymondfeng