loopback/lib
Miroslav Bajtoš 9c5fe088e3 AccessControl for change replication
1) Add integration tests running change replication over REST to verify
that access control at model level is correctly enforced.

2) Implement a new access type "REPLICATE" that allows principals
to create new checkpoints, even though they don't have full WRITE
access to the model. Together with the "READ" permission, these
two types allow principals to replicate (pull) changes from the server.

Note that anybody having "WRITE" access type is automatically
granted "REPLICATE" type too.

3) Add a new model option "enableRemoteReplication" that exposes
replication methods via strong remoting, but does not configure
change rectification. This option should be used the clients
when setting up Remote models attached to the server via the remoting
connector.
2015-04-07 19:53:58 +02:00
..
connectors Enable jscs for `lib`, fix style violations 2014-11-04 08:25:33 +01:00
access-context.js AccessControl for change replication 2015-04-07 19:53:58 +02:00
application.js Add support for app level Model isolation 2015-04-03 11:48:45 -07:00
browser-express.js Emit a 'modelRemoted' event by app.model() 2014-07-24 17:00:27 -07:00
builtin-models.js Add support for app level Model isolation 2015-04-03 11:48:45 -07:00
express-middleware.js Expose more loopback middleware for require 2014-11-19 11:32:22 -08:00
global-registry.js Add support for app level Model isolation 2015-04-03 11:48:45 -07:00
loopback.js Add support for app level Model isolation 2015-04-03 11:48:45 -07:00
model.js AccessControl for change replication 2015-04-07 19:53:58 +02:00
persisted-model.js AccessControl for change replication 2015-04-07 19:53:58 +02:00
registry.js Add support for app level Model isolation 2015-04-03 11:48:45 -07:00
runtime.js Enable jscs for `lib`, fix style violations 2014-11-04 08:25:33 +01:00
server-app.js Add a workaround to avoid conflicts with NewRelic 2015-02-25 09:47:18 -08:00