Set forceId = false for AccessToken

[jannyHou]

Connect to loopbackio/loopback-datasource-juggler#849

Some test cases need refactor after we set forceId as true by default.
Details related please see: loopbackio/loopback-datasource-juggler#982 (comment)

[jannyHou]

@slnode test please

[jannyHou]

@bajtos PTAL, thanks!

[bajtos]

AFAICT, we are not setting Post.id explicitly in any of the existing tests. Why is it necessary to set forceId to false in that case?

[bajtos]

@jannyHou I am confused why is it necessary to set forceId:false in test models, since I don't see any test that would be explicitly setting id when creating new instances. It does not match my mental model of how LoopBack & Juggler works.

Could you please elaborate little bit more on why are those changes necessary, so that I can understand what I am missing now?

[bajtos]

@jannyHou let's wait until #2551 is landed, I think we will be able to revert most of the changes proposed here.

[bajtos]

With #2551 landed, there is only one test needing forceId:false. I am going to force-push into this pull request the updated version that works for me. For posterity, @jannyHou's original commit was 8553c2d.

[jannyHou]

@bajtos Thank you 👍 and I will take a look into the CI failings

[jannyHou]

@slnode test please

[jannyHou]

The failing ones are caused by authentication problem in some test cases.
For example:

Wed, 27 Jul 2016 21:45:05 GMT strong-error-handler Handling Error: Authorization Required
at C:\jenkins\workspace\loopback\b88abec9\lib\application.js:393:21
at C:\jenkins\workspace\loopback\b88abec9\lib\model.js:318:7
at C:\jenkins\workspace\loopback\b88abec9\common\models\acl.js:471:23
at C:\jenkins\workspace\loopback\b88abec9\node_modules\async\lib\async.js:251:17
at done (C:\jenkins\workspace\loopback\b88abec9\node_modules\async\lib\async.js:132:19)
at C:\jenkins\workspace\loopback\b88abec9\node_modules\async\lib\async.js:32:16
at C:\jenkins\workspace\loopback\b88abec9\node_modules\async\lib\async.js:248:21
at C:\jenkins\workspace\loopback\b88abec9\node_modules\async\lib\async.js:572:34
at C:\jenkins\workspace\loopback\b88abec9\common\models\acl.js:453:17
at C:\jenkins\workspace\loopback\b88abec9\common\models\role.js:269:21
at C:\jenkins\workspace\loopback\b88abec9\node_modules\continuation-local-storage\node_modules\async-listener\glue.js:188:31
at process._tickDomainCallback [as _tickCallback] (node.js:492:13)
<testcase classname="loopback.rest" name="should report 200 for GET /:id/exists found" time="0.007"/>
Wed, 27 Jul 2016 21:45:05 GMT strong-error-handler Response status 401 data {"statusCode":401,"name":"Error","message":"Authorization 

Will investigate more...

[jannyHou]

@slnode test please

[jannyHou]

I am landing it since all loopback CI are green :squirrel: