-
Notifications
You must be signed in to change notification settings - Fork 187
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
Project Space has owner
#4419
Comments
"something happened" (tm) a little while ago about this, from memory. One of the problems was that a project space can have multiple users that have "all rights" to manage the space. And if the "owner" is set to the user who created the space, then there is the problem of what to do if that user is deleted, disabled, or has their rights to the space removed. IMO @micbar is offline at the moment. Maybe @kulmann you can point to the discussion and design/implementation that happened? |
@butonic can you clarify? |
@micbar added a technical owner to spaces which is impersonated when using public links to access a space. Public links are no longer tied to the user that creates them, but the space. For that to work introduced a technical user for every space, because we wanted to prevent a public link from ever accessing a different space. cc @C0rby please don't hate us: cs3org/reva#3091 (comment) |
Now that you pinged me, I can also contribute 😄 What @butonic says is correct. But this should not be exposed. Neither cs3 api nor graph api should have an owner on project spaces. So this needs to be fixed. |
@SwikritiT @individual-it @butonic @phil-davis please always refer to #4316 |
for this is there a separate ticket or should I create one? |
owner
@micbar I've updated the title and description. |
Einstein
a space adminEinstein
create a project spaceNew Space
Einstein
lists the drives using the graph APIcurl -u einstein:relativity -k -X GET https://host.docker.internal:9200/graph/v1.0/me/drives -v | jq
As per #4419 (comment) and #4419 (comment) the project spaces
owner
should not be exposed but in the current implementation, we can see theowner
of a project space.The text was updated successfully, but these errors were encountered: