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

Listing permissions for disabled spaces not possible #9764

Closed
JammingBen opened this issue Aug 8, 2024 · 6 comments
Closed

Listing permissions for disabled spaces not possible #9764

JammingBen opened this issue Aug 8, 2024 · 6 comments
Labels

Comments

@JammingBen
Copy link
Contributor

Describe the bug

Listing permissions for disabled spaces is not possible and returns a 404 error.

Steps to reproduce

  1. Create a new space
  2. Disable the space
  3. List its permissions (e.g. https://host.docker.internal:9200/graph/v1beta1/drives/309ae7c7-2db4-4c08-8e7c-d272086aa607%24449cb542-3d80-4ef5-9d94-12ef5444adac/root/permissions)

Expected behavior

The permissions are being listed despite the space being disabled. I believe this was the behavior pre sharing NG.

Actual behavior

The server responds with a 404 error.

@kobergj
Copy link
Collaborator

kobergj commented Aug 13, 2024

Are you sure this was the behaviour before? There corresponding code path seems much older than sharing NG: https://github.com/cs3org/reva/blob/edge/pkg/storage/utils/decomposedfs/node/node.go#L290-L291

If we allow listing permissions for disabled spaces, should we also allow changing them? As of now disabled spaces cannot be edited in any way (save restore)

@JammingBen
Copy link
Contributor Author

Pre Sharing NG you were able to list space members of disabled spaces (although not change them):

image

@kobergj
Copy link
Collaborator

kobergj commented Aug 14, 2024

Yes. But that information is included in the GET drive call. You don't need to call permissions endpoint for this. Are you sure web called this before?

@JammingBen
Copy link
Contributor Author

Ahh now I get it, you're right. The old ocm /shares endpoint didn't return any space members, no matter if the space was enabled or disabled. We always got this information via the drive itself and then querying each and every user/group (ouch). With sharing NG though, we're using the /permissions endpoint.

So before jumping into any kind of implementation or fix, I'd raise the question if it is necessary for as disabled space to display its members. Might be a little tricky, but definitely possible. @tbsbdr What do you think?

@tbsbdr
Copy link

tbsbdr commented Aug 15, 2024

As long as one can see the managers in den details panel, I'd not require to see all other space members. if someone needs it, we can discuss again. until then, lets not implement it an focus on more important features.
i.e. we could remove the members panel.

@JammingBen
Copy link
Contributor Author

Ok thanks, then I'll close here since there is nothing for the server to do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

No branches or pull requests

4 participants