-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
object/put: Process session token of the original request in ACL checks #2461
object/put: Process session token of the original request in ACL checks #2461
Conversation
cthulhu-rider
commented
Jul 26, 2023
- closes Broken relay of objects prepared on the client with session #2460
Codecov Report
@@ Coverage Diff @@
## master #2461 +/- ##
=======================================
Coverage 29.47% 29.48%
=======================================
Files 399 399
Lines 30432 30430 -2
=======================================
Hits 8971 8971
+ Misses 20717 20715 -2
Partials 744 744
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
6287bc9
to
e6ac7d6
Compare
need to re-check for >1 replica container |
checked, works fine. #881 doesn't reproduce. |
e6ac7d6
to
8130b9a
Compare
Previously, when checking write access to an object, the storage node used only the session token from the last request sent. In case of a chain of more than one request, the original session token was ignored. As a result, it did not allow to correctly interpret on whose behalf the action was performed. In particular, in private containers, gateways were deprived of the right to write data on behalf of the user. From now storage node always processes the session token from the original request. Signed-off-by: Leonard Lyubich <leonard@morphbits.io>
8130b9a
to
cf3d615
Compare