-
Notifications
You must be signed in to change notification settings - Fork 159
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
OCM. user cannot delete accepted user #11688
Comments
@kulmann is that an issue of the sciencemesh app? |
The web ui does not send any payload, so the server cannot identify which user to delete.
no payload |
could you provide some example how should look request? then I can add api test for that |
@rhafer and me tried to use it but it doen't work. we got 200 but federated connection still exist |
This one just didn't work because we were using the wrong userid. The federated users userids look slightlyg diffferent since cs3org/reva@3e6ce69. Using the correct ids (those returned by So the remaining issue is basically a bug in web. It is sending a DELETE request with an empty body. To delete a federated user you can either use a json BODY like this:
Or form-urlencoded parameters as in @ScharfViktor example above. I am transferring this issue to web, since the ocis side seems to work AFAICS. |
can confirm that it works one more question: Case:
Actual: if |
precondition:
ocis-server
andfederation-ocis-server
see here https://owncloud.dev/ocis/development/testing/#running-test-suite-with-federated-sharing-ocmSteps:
And "Alice" has generated invitation
And using server "REMOTE"
And "Brian" has accepted invitation
And using server "LOCAL"
When "Alice" deletes accepted user "Brian"
Then the HTTP status code should be "204"
Actual:
Screen.Recording.2024-07-08.at.11.48.05.mov
Expected:
I guess web uses wrong
DELETE sciencemesh/delete-accepted-user
request. should be likeDELETE sciencemesh/delete-accepted-user/user-uuid
but it doesn't work-> I get 404 error with log:The text was updated successfully, but these errors were encountered: