-
Notifications
You must be signed in to change notification settings - Fork 5
Conversation
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
ad74f65
to
b8239e9
Compare
de0522a
to
f8aa141
Compare
AFAICT the problem comes from changing the global namespace to a jailed one at the endpoints. phoenix uses the path 'is sees' and sends a request like
to create the share. but the ocs endpoint takes the path digging deeper... manually prefixing the path in the payload with |
I got other errors with the acceptance tests. It was about the tests where we provide invalide permissions as parameters and expect the ocs service to return an error instead of ok. |
f8aa141
to
20c448e
Compare
This reverts commit ac3381e.
these are the scenarios that failed:
and L119-135
L153-169
L201-219
the flags of this PR makes the storageprovider for root actually run a storage ...
That should jail all api sharing requests to the home storage which makes sense, well, it hides the reva ocs sharing bug that always uses the global namespace ... Well it helps to look at the actual errors
It seems the users service now returns a user ... wtf ... will continue digging tomorrow ... |
adding Steps to reproduce the current issue in CI manually:all steps done using LDAP. Reva started with this command:
Resultswith with 2b2e7f0in every case the result is:
with ac3381e
|
Could you try starting |
Fixes #75