Multiple User child Models problem

[glesage]

Hi All,

I've got 2 separate models that both inherit from the User model: Driver & Agent.
When I login with the first created user of each, the response I get is:

Agent/Login

{
  "id": "55EFKiN0ZtUGgh4mefU4s7DRM9KvyogV7dg14iQEjjD1tNSZK276HBZRVTCpGIFd",
  "ttl": 1209600,
  "created": "2014-09-02T19:02:27.411Z",
  "userId": 1
}

Driver/Login

{
  "id": "pL9qucXRAq9E6YKyAFRBMXc0K4FcTpFYQh9ZxqLN2p3DSDn9A6U3u3zDK57enEz9",
  "ttl": 1209600,
  "created": "2014-09-02T19:03:24.995Z",
  "userId": 1
}

Why is the "userId" always 1? It makes it impossible to trace back the user based on the token and such... also, once I log in a driver the agent that was logged in probably gets his accessToken overridden...

Please advise!

Thanks

[glesage]

Apologies if this needs to go into https://github.com/strongloop/loopback-datasource-juggler... It's unclear to me which one it belongs to (:

[raymondfeng]

What data source do you use?

Each model has its own sequence of id values. Now you have two models, do you map them to the same table?

[glesage]

nope, they are both in separate MySQL tables.
but in the accessToken table, the userId column refers to a generic "User" so I have no way of knowing which of the driver or agent it is for...

[raymondfeng]

Now you have two physical types of users backed by separate tables, there will be overlapping user ids. If you want to use the same access token model, you will have to override userModel.prototype.createAccessToekn(). The other option is to configure Agent/Driver model with a new belongsTo relation to AccessToken so that tokens are stored in separate tables too.

[glesage]

oh ok interesting. Thanks for the tips!

[glesage]

Wait, apologies for too quickly assuming all would work without issues /:
I did try your suggestion but the AccessTokens behave the same... There is still one table for all tokens.

How can I separate the tokens?

[raymondfeng]

You'll have to create two sub-models to AccessToken, such as AgentAccessToken and DriverAccessToken.

[glesage]

oh alright makes sense... will try

[glesage]

Will I still need to override the userModel.prototype.createAccessToken() though?

[raymondfeng]

No, if you have two AccessToken models and configure Agent/Driver model to hasMany/belongsTo them respectively.

[glesage]

yea I have but how do you link them to the login process... I did do:

"relations": {
    "AccessToken": {
      "type": "belongsTo",
      "model": "DriverAccessToken",
      "foreignKey": "userId"
    }
}

But it still uses the original "AccessToken" model

[raymondfeng]

For Driver, the relation should be:

"relations": {
    "accessTokens": {
      "type": "hasMany",
      "model": "DriverAccessToken",
      "foreignKey": "userId"
    }
}

[glesage]

oh alright perfect!