Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replication and instance-level ACL #1427

Closed
bajtos opened this issue Jun 2, 2015 · 7 comments
Closed

Replication and instance-level ACL #1427

bajtos opened this issue Jun 2, 2015 · 7 comments

Comments

@bajtos
Copy link
Member

bajtos commented Jun 2, 2015

#1270 implemented support for replicating models that use model-level ACL (i.e. a user can either access all instances or no instances). However, this is not enough for many real-world use cases, where the model is configured with a instance-level ACL (e.g. a user can access only the instances he created himself).

We should improve the replication implementation and support instance-level access permissions too.

@sachinhub
Copy link

Dear all,

What is the status of "instance-level" ACLs? Is it already implemented or planned to be implemented as enhancement ?

@jesperbruunhansen
Copy link

Any news on this feature? Or does anybody have ideas how to handle this in a custom build? Our dev-team has been trying off a few ways of doing this, but having native support out the box would be amazing!

@riterrani
Copy link

Any news on this feature? Anybody have implemented this in a custom build?

Thanks!

@antoinebrault
Copy link

Any ETA on this feature? This is blocking for a lot of real world applications.

No progress on https://github.com/strongloop/loopback/milestone/17 for a long time.

@jesperbruunhansen
Copy link

Hi everyone.

My team has open sourced our approach to a custom build of this functionality. Any feedback or help is highly appreciated. Repo: loopback-object-acl

Note: the state of this project is currently in early alpha release and is only tested with Loopback v3.x and MongoDb as datasource.

@stale
Copy link

stale bot commented Aug 23, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot closed this as completed Sep 6, 2017
@stale
Copy link

stale bot commented Sep 6, 2017

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests