mirror of
https://github.com/nspcc-dev/neofs-s3-gw.git
synced 2026-03-01 04:29:15 +00:00
Caching of EACL #102
Labels
No labels
I2
I2
I3
I4
S2
S3
S4
S4
U0
U1
U2
U2
U3
U4
U4
auth-mate
blocked
bug
config
dependencies
discussion
documentation
enhancement
epic
feature
go
good first issue
help wanted
performance
question
security
test
tree-service
tree-service
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neofs-s3-gw#102
Loading…
Add table
Add a link
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?
Originally created by @KirillovDenis on GitHub (Aug 6, 2021).
Originally assigned to: @realloc, @alexvanin, @KirillovDenis, @carpawell, @masterSplinter01, @cthulhu-rider on GitHub.
Should we cache eACL on s3-gate side in view of storage node also caches it?
@realloc commented on GitHub (Aug 11, 2021):
We should have the "small cache" for eACL responses with the SideChain block generation time TTL.
Maybe that should be done as a part of Container Cache, as we use container attributes a lot.
@KirillovDenis commented on GitHub (Aug 12, 2021):
I believe that this problem can be turned into a task of implementing an ACL validation layer before executing the business logic.
@realloc commented on GitHub (Aug 26, 2021):
We need to cache not the eACL, but the internal S3 ACL representation. The S3 ACL must be able to be saved as eACl to make the S3 gateway stateless.
The summary of the discussion is that we need to implement ti ACL processing layer first.