nspcc-dev / nspcc-dev/neofs-api
Allow cross-header matching in EACL
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 11
- Forks
- 15
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 9
Description
Is your feature request related to a problem? Please describe.
I'm always frustrated when I can't express some header field relations in EACL. It is possible to set ALLOW DELETE MATCH $Object:ownerID == XYZ behavior. But it's not possible to get ALLOW DELETE MATCH $Object:ownerID == $Request:author or $Object:creationEpoch == SOME_OTHER_ATTRIBUTE
Describe the solution you'd like
Add a level of indirection for value, allow to get it from the same set of headers (object/request) we have.
Describe alternatives you've considered
For owner/author an extended sticky bit can be useful, but EACL is more generic and allows for richer semantics.
Additional context
Related to sticky ACL bit, currently its interpretation is not very useful (static objects only, strange corner case).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the EACL declaration and expression definitions in this repository; the issue names no file, entry point, or test. Determine how ALLOW DELETE MATCH currently handles object and request headers, then define and validate the intended cross-header value syntax for the examples in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100