APE access to receive specific object from specific container #1101
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#1101
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I got this APE rule set by S3 Gateway
To access
cat.jpg
, S3 Gateway uses tree service and object service (head / get object). Requests contain bearer token withimpersonate
flag, signed by0212f413f56c7da16102f721b4e3c7302efb35013e2291e28a1b58ce28ec1117c4
public key.Expected Behavior
Access is granted.
Current Behavior
Access is denied due to several issues:
FilePath
attribute is not passed to request context.Possible Solution
Steps to Reproduce (for bugs)
Regression
No
Your Environment
frostfs-node v0.38.5
frostfs-s3-gw v0.29.0-rc.7
/cc @fyrchik, @dkirillov
#1090
I've checked this issue and it doesn't work for me yet.
frostfs-node v0.42.0-rc.6
I am not sure this can be fixed without introduction of separate policy actions for tree service.
S3 Gateway wants GetObject access with FilePath condition.
It also wants GetSubtree access without any specific conditions in this container.
While these two different operations are processed by the same
GetObject
action, we either fail on one of them (current behaviour) or S3 gateway should drop condition for GetObject, which may be considered as access policy violation by the user.Thus, reopen to test this again when tree service actions are introduced.
To test it, we can simplify policy a bit:
It should produces this ingress rule