mirror of
https://github.com/nspcc-dev/neofs-node.git
synced 2026-03-01 04:29:10 +00:00
Practical use case for tokens attached to the request wrappers #878
Labels
No labels
I1
I2
I3
I4
S0
S1
S2
S3
S4
U0
U1
U2
U3
U4
blocked
bug
config
dependencies
discussion
documentation
enhancement
enhancement
epic
feature
go
good first issue
help wanted
neofs-adm
neofs-cli
neofs-cli
neofs-cli
neofs-ir
neofs-lens
neofs-storage
neofs-storage
performance
question
security
task
test
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neofs-node#878
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 @carpawell on GitHub (Nov 11, 2022).
I faced some bug (or not) in #2045 while was testing request forwarding: a node took tokens from the first
MetaHeaderit has and did not try to unwrap any other despite the fact that for example, the ACL service checks the deepest one only. Was it a bug? Do we have any info about how to treat sessions/bearers attached to the wrappers not the original requests?/cc @cthulhu-rider, @realloc, @alexvanin, @fyrchik