Session token is not written to the object #8

Closed
opened 2025-12-28 17:18:10 +00:00 by sami · 1 comment
Owner

Originally created by @cthulhu-rider on GitHub (Sep 24, 2020).

Originally assigned to: @cthulhu-rider on GitHub.

Expected Behavior

In case of trusted object placement within opened session between user and trusted node session token must be written to object body.

Current Behavior

Session token is not written to the objects during trusted placement.

Possible Solution

  1. write session token to object in format transformer;

  2. take session token from the request and write to object before transformations.

Your Environment

  • jindo branch
Originally created by @cthulhu-rider on GitHub (Sep 24, 2020). Originally assigned to: @cthulhu-rider on GitHub. <!--- Provide a general summary of the issue in the Title above --> ## Expected Behavior In case of trusted object placement within opened session between user and trusted node session token must be written to object body. ## Current Behavior Session token is not written to the objects during trusted placement. ## Possible Solution 1. write session token to object in format transformer; 1. take session token from the request and write to object before transformations. ## Your Environment <!--- Include as many relevant details about the environment you experienced the bug in --> * `jindo` branch
sami 2025-12-28 17:18:10 +00:00
Author
Owner
@alexvanin commented on GitHub (Sep 30, 2020): Fixed in #56: https://github.com/nspcc-dev/neofs-node/pull/56/commits/7854663fd3ff1fd8c0f85f26c89343f2e02f3176
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neofs-node#8
No description provided.