-
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
SharingNG: initial OCM support #8909
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. |
d98e8d4
to
4e973f4
Compare
4e973f4
to
f5cc95f
Compare
f5cc95f
to
ca9d8f4
Compare
Quality Gate passedIssues Measures |
56a3c21
to
8808fb0
Compare
There was config issue. no issue @butonic can we merge this PR? |
Signed-off-by: Jörn Friedrich Dreyer <[email protected]>
Signed-off-by: Christian Richter <[email protected]>
Quality Gate passedIssues Measures |
Rebased. IMO we should merge this as is. It allows developers to actually set up and debug OCM shares. It will allow implementing E2E tests. The commented code sections point out missing pieces in the CS3 API. I would merge this ASAP to iterate further. |
SharingNG: initial OCM support
I just wanted to fix the CI for cs3org/reva#4630, but to debug I had to make graph support OCM so that I could use web to actually send invites, create shares and browse them ...
This is rudimentary, only supports creating and accepting shares. It is a start ...
To test this you have to set the necessary OCM flags:
enable the ocm web app
and finally configure two ocm providers in the
/path/to/ocis/ocmproviders.json
file:copy this proiders file to both instances.
This is a vscode config to run an additional instance with all the ports configured to use a different port than the default as well as a different registry: