lablup / lablup/backend.ai

Write the BEP for field-permission enforcement

Open
#14,128 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
670
Forks
183
Avg merge
15h 13m
Merged PRs (30d)
368

Description

BEP-1077 defines the field-permission model (role field_permissions, grant caps, effective fields = role list intersected with cap list); this BEP fixes how it is enforced. Decisions to settle: how lookup, querier, searcher and updater validate against the effective field set (blank on read, drop on update input, refuse filter/sort, natural-key lookup requiring READ on the key's field); at which layer an explicitly requested unpermitted GraphQL field is rejected and with what error; and the shape in which the resolved field set travels from the permission check into the specs (the validator-to-spec interface). Written against the BA-7593 tables. Korean draft first, then English, per the BEP workflow.

JIRA Issue: BA-7597

Contributor guide

Open the contributing guide

Research direction

Start by reading BEP-1077 and the BA-7593 tables, then use the listed decisions to structure the BEP: effective-field validation for lookup, querier, searcher and updater, GraphQL rejection behavior, and the validator-to-spec field-set interface. Done means resolving these questions in a Korean draft first, followed by the English version under the BEP workflow.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql
Domain
authorization, backend-api-design, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.