-
Notifications
You must be signed in to change notification settings - Fork 18
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
acl, container: Add negative tests #582
Conversation
These tests are OK (when fixed), but in #579 we wanted to check for session-based actions as well. |
OK, I'll add session-based tests |
7c9e126
to
d0f4433
Compare
Done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's nice, but I've noticed that generate_session_token()
actually fills in ownerID
from owner_wallet
which then signs the token in sign_session_token()
. What also need is a correct ownerID
in the token, but a token that is signed by a different wallet.
Thank you for the comment. I'll also add a related case. |
3d1b0cd
to
0b9638f
Compare
Done. I have a question in the process of writing tests: nspcc-dev/neofs-node#2466 |
Question resolved |
e215021
to
3b903af
Compare
After the PR nspcc-dev/neofs-node#2501 the error messages have changed. |
Added two negative tests that verify that the container cannot be removed or set container EACL by anyone other than the owner (creator). Closes nspcc-dev#579 Signed-off-by: Oleg Kulachenko <[email protected]>
Added negative tests that verify that the container can be removed or set container EACL only by trusted party proved by the container owner via session token. Closes nspcc-dev#579 Signed-off-by: Oleg Kulachenko <[email protected]>
Added two negative tests that verify that the container cannot be removed or set container EACL by anyone other than the owner (creator) or trusted trusted party proved by the container owner via session token.