Don't use basic acl in authmate #553
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-s3-gw#553
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?
Is your feature request related to a problem? Please describe.
After TrueCloudLab/frostfs-node#1480 storage node doesn't support basic and eacl anymore.
But gate use still it
basicACL := acl.Private
// allow reading objects to OTHERS in order to provide read access to S3 gateways
basicACL.AllowOp(acl.OpObjectGet, acl.RoleOthers)
basicACL.AllowOp(acl.OpObjectHead, acl.RoleOthers)
basicACL.AllowOp(acl.OpObjectSearch, acl.RoleOthers)
These leads to creating accessbox without any access right for fresh storage node versions. We should fix this.
Describe the solution you'd like
Use APE instead of [e]acl in authmate
Describe alternatives you've considered
No
Additional context
No
Don't use basaic acl in authmateto Don't use basic acl in authmateAddChain
update/invalidate APE cache? #1503