Kinto / Kinto/kinto

Break permission inheritance by adding the none keyword

Open
#368 1 comment 0 reactions 0 assignees View on GitHub
protocol question scope: permissions stale
Dominant language
Python
Stars
4.4k
Forks
437
Avg merge
1d 2h
Merged PRs (30d)
15

Description

Eg.
- `{read: [system.EveryOne]}` on bucket
- `{none: [system.EveryOne]}` on specific collection in this bucket
Users can read every collections in bucket but one specific.

Inspiration: Syncano permission types http://docs.syncano.io/docs/permissions#section-permission-types-for-data-objects-

Contributor guide

Open the contributing guide

Research direction

No implementation files or tests are named. Start with the issue's bucket and collection examples and the linked Syncano permission-types reference, then locate Kinto's permission inheritance logic. Done means a none permission on one collection prevents access inherited from the bucket while other collections retain the bucket permission.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
authorization, backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.