Skip to content
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

Expand session token statuses #289

Open
carpawell opened this issue Feb 22, 2024 · 0 comments
Open

Expand session token statuses #289

carpawell opened this issue Feb 22, 2024 · 0 comments
Labels
feature Completely new functionality I2 Regular impact S2 Regular significance U4 Nothing urgent

Comments

@carpawell
Copy link
Member

Is your feature request related to a problem? Please describe.

I'm always frustrated when I see regular problems but cannot assign some well-known status to them. Session token is a good well-structed candidate. We did it once: #191. Now we also have validation on the SN side and now such errors can be seen by a user: nspcc-dev/neofs-node#2731, nspcc-dev/neofs-node#2727.

Describe the solution you'd like

Possible status codes:

  1. Wrong token issuer/not signed by container owner
  2. Invalid signature
  3. Wrong session operation
  4. Wrong container

Describe alternatives you've considered

Not sure all of them (or any of them) are required and having a separate code for them can make user's life easier but for the tests a well structured response for such an important NeoFS part may look pretty.

@carpawell carpawell added U4 Nothing urgent S2 Regular significance I2 Regular impact feature Completely new functionality labels Feb 22, 2024
@carpawell carpawell changed the title Expand session tokens statuses Expand session token statuses Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Completely new functionality I2 Regular impact S2 Regular significance U4 Nothing urgent
Projects
None yet
Development

No branches or pull requests

1 participant