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

Finer grain for permissions #468

Closed
Natim opened this issue Feb 26, 2016 · 2 comments
Closed

Finer grain for permissions #468

Natim opened this issue Feb 26, 2016 · 2 comments

Comments

@Natim
Copy link
Member

Natim commented Feb 26, 2016

As per discussion with @chrismbeckett on IRC:

In business application, having write permissions doesn't means nor that you can delete the data nor that you can change its permissions.

We should probably let people define another sharable model for their Kinto Instance.

Today we have:

  • ProtectedResource
  • SharableResource

We may want to let people define other ones more complex with their own inheritance tree and another set of permissions or at least let them define which verb are link to which permission.

Keep in mind that without a collection schema it is possible to remove a records by putting an empty record instead, with the collection schema it is not possible to remove something by putting an empty record for instance but it is still possible to override it with wrong data.

Maybe we should investigate this use case and see what are the options to handle that.

@Natim Natim added the question label Feb 26, 2016
@Natim
Copy link
Member Author

Natim commented Feb 26, 2016

For the question of deletion, something that we had in mind is to mark the record as deleted and put it in a garbage collections (using a listener) and then having a job that remove very old items from the garbage.

@leplatrem leplatrem changed the title Delete permissions should be different from write permission same to give permissions. Finer grain for permissions May 27, 2016
@leplatrem
Copy link
Contributor

I marked this as a duplicate of #101

lavish205 pushed a commit to lavish205/kinto that referenced this issue Jun 20, 2016
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

2 participants