Different owners error when use client cut object #117
Labels
No labels
P0
P1
P2
P3
good first issue
pool
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-sdk-go#117
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?
Failed to put object using client cut.
Actually I'm not sure if problem in SDK, in storage node or in client code (Pool).
Probably I don't understand session token correctly:
why we check here signature for session key if client only has its public part.
And we cannot use owner id for object that different from one who real sign the request (we have bearer token)
Expected Behavior
Object is successfully created
Current Behavior
Got
Possible Solution
No idea.
Steps to Reproduce (for bugs)
this test should be placed and run here
Context
Such behavior was noticed in scope of #114
So we try to put object using s3 gw
Your Environment
@dkirillov test
TestDifferentOwnersWithSession
Session token must be signed with owner's private key, have gate's public key as auth key and expiration time.
Actually we cannot use this approach in the pool. We don't have
ownerKey
. As workaround of course we can form session token forgateKey
and sign it also bygateKey
but it looks like a kludge a little.But I agree that when we (as pool) was provided by session token, it should be formed with approach you sugessted.
Actually, I would like to be able set owner field for object that it can be different from request signer. It seems that this field has just informative function (@alexvanin @fyrchik am I right?)
Fixed