Feedback from AARNet

[madsi1m]

Overview

We now have an almost working deployment of OCIS, here are some notes on what is not working/missing

Environment

Phoenix 0.2.3
Reva from github Nov 7, 2019 e56ca76b99b163e8d27dad2630bf415fae73c16a

These are the things that currently do not work for us:

• Sharing buttons are missing in the UI
• Navigating into a sub folder does not work Fixed
• Media view can not get to /remote.php/dav/public-files//<>/image.png?stuff
• example toml files do not work
  (FIXED fix configuration examples in separate folder by madsi1m · Pull Request #351 · cs3org/reva · GitHub)
• /ocs/v2.php/apps/notifications/api/v1/notifications?format=json still misssing 404
• Trash bin does not work
• Favorites does not work
• Media viewer does not recognise mp4 as media
• Deleteing a file is broken
• Overwrite a file is broken

These are the things that are currently missing:

• We authenticate via federated (almost) openid connect compatible end point. In the current model OCIS makes the assumption that the user must exist in the "basic auth". We need a way to create a user on successful login. At the moment it seems OCIS is smart enough to create missing user folders on first login but not create the user.
• Sync client compatibility, I am not able to add ocdav/frontend to the sync client as it tells me the "Host requires authentication"

[butonic]

Tested with current example/separate config: cs3org/reva@ac1b961

• Sharing buttons are missing in the UI
  • should be visible with the right capabilities, reenabled with https://github.com/cs3org/reva/pull/368/files#diff-af7641b220981605161a6ea06b79d3a7R189-R220
• Navigating into a sub folder does not work
  • works with current example/separate config (jfd)
• Media view can not get to /remote.php/dav/public-files//<>/image.png?stuff
  • not implemented yet, tracked in [reva] public links webdav API #18
• example toml files do not work
  (FIXED fix configuration examples in separate folder by madsi1m · Pull Request #351 · cs3org/reva · GitHub)
• /ocs/v2.php/apps/notifications/api/v1/notifications?format=json still misssing 404
  • not implemented, should be disabled with the right capabilities, tracked in Notifications endpoint #14
• Trash bin does not work
  • confirmed, tracked in Trash bin does not work #47
• Favorites does not work
  • not implemented yet, tracked in [reva] favorites #15
• Media viewer does not recognise mp4 as media
  • not yet implemented, tracked in Video playback web#2051
• Deleteing a file is broken
  • works with current example/separate config (jfd)
• Overwrite a file is broken
  • confirmed, tracked in Overwriting files does not work #48
• We authenticate via federated (almost) openid connect compatible end point. In the current model OCIS makes the assumption that the user must exist in the "basic auth". We need a way to create a user on successful login. At the moment it seems OCIS is smart enough to create missing user folders on first login but not create the user.
  • @madsi1m During authentication the gateway establishes the user id (sub@iss) and then tries to fill in user metadata. Currently only one of the available user manager implementations is possible: https://github.com/cs3org/reva/tree/master/pkg/user/manager The oidc provider reads the necessary claims from the user context, which has been filled by the oidc auth provider. Can you send the necessary claims with your oidc provider? If so you can use the oidc user manager and reva will log in any user that is authenticated with oidc. In that regard we are working an adding roles and permissions, which is tracked in [reva] roles concept and permissions endpoint #12
• Sync client compatibility, I am not able to add ocdav/frontend to the sync client as it tells me the "Host requires authentication"
  • access to status.php was protected, fixed with https://github.com/cs3org/reva/pull/368/files#diff-af7641b220981605161a6ea06b79d3a7R55
  • client oidc support tracked in OpenID Connect support client#7482, PR in Support for openid connect client#7509
  • @madsi1m For testing you can either limit reva to basic auth, or setup a dedicated frontend-basic.toml that only supports basic auth and point the client to that. To do that, set credential_chain = ["basic"] in https://github.com/cs3org/reva/blob/master/examples/separate/frontend.toml#L50

[DeepDiver1975]

* Media viewer does not recognise mp4 as media

phoenix media viewer is currently only for images - videos to come

[butonic]

@DeepDiver1975 is that tracked in phoenix or is there a dedicated repo for the mediaviewer?

[DeepDiver1975]

is that tracked in phoenix o

in the phoenix repo - THX

[butonic]

I either linked an existing issue, created a new one or could not reproduce the problem (likely due to a not up to date config). Feedback addressed -> closing.

[madsi1m]

The sync client points to /oauth2/.* which does not exist is our deployment as we do not have a oidcprovider in our frontend.toml. Do I need to add one? How to i link it to my external openidc provider?