nspcc-dev / nspcc-dev/neofs-node
Add backward response for N3 account verification
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
Is your feature request related to a problem? Please describe.
Using N3 accounts gives a powerful tool. But in case of VerifySignature fails (return false), the Node doesn't return a response to the client app.
For instance, for container removal. If a user tries to remove someone's container:
VerifySignaturereturns false- There is a log message in AIO:
error container/process_container.go:172 delete container check failed {"error": "auth container removal: verification script run resulted in false"}
But the client app still waits for the response. Eventually timeout.
Describe the solution you'd like
Return a clear response, the check failed
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in process_container.go around line 172 and trace the VerifySignature failure path for container removal. Follow how client responses are returned, then make the failed check produce a clear response instead of leaving the client waiting until timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100