The following sections list the changes in reva 1.13.0 relevant to reva users. The changes are ordered by importance.
https://github.com/cs3org/reva/pull/2024 https://github.com/cs3org/reva/pull/1968
Added the deleted share to the response after deleting it.
https://github.com/cs3org/reva/pull/2054
As the share receiver, moving a shared file to another share was not possible.
https://github.com/cs3org/reva/pull/2026
This change fixes the way log files were opened. Before they were truncated and now the log file will be open in append mode and created it if it does not exist.
https://github.com/cs3org/reva/pull/2047
Before this fix a share file_target was always harcoded to use a base path. This fix provides the possiblity to expose full paths in the OCIS API and asymptotically in OCIS web.
https://github.com/cs3org/reva/pull/1605
The storageid in the share object contained an incorrect value.
https://github.com/cs3org/reva/pull/2033
Removed the “Got registration for user manager” print statements which spams the log output without respecting any log level.
https://github.com/cs3org/reva/pull/2059
This change fixes the parsing of WOPI discovery URLs for MSOffice /hosting/discovery endpoint. This endpoint is known to contain malformed query paramters and therefore this fix removes them.
https://github.com/cs3org/reva/pull/2051
This change fixes upload of empty files. Previously this was broken and only worked for the owncloud filesystem as it bypasses the semantics of the InitiateFileUpload call to touch a local file.
https://github.com/cs3org/reva/pull/2055
Implemented the removal of share references when a share gets declined. Now when a user
declines a share it will no longer be listed in their Shares
directory.
https://github.com/cs3org/reva/pull/1991
Removes superfluous Writeheader on file upload and therefore removes the error message “http: superfluous response.WriteHeader call from github.com/cs3org/reva/internal/http/interceptors/log.(*responseLogger).WriteHeader (log.go:154)”
https://github.com/cs3org/reva/pull/2030
The underlying app is not WOPI-compliant nor it is supported by the WOPI bridge extensions
https://github.com/cs3org/reva/pull/2034
https://github.com/cs3org/reva/pull/1968
Adds a new http service which will create an archive (platform dependent, zip in windows and tar in linux) given a list of file.
https://github.com/cs3org/reva/issues/1698 https://github.com/cs3org/reva/pull/2066
Added ldap filter escaping to increase the security of reva.
https://github.com/cs3org/reva/pull/2042
Adds a new authentication method used to impersonate users, using a shared secret, called api-key.
https://github.com/cs3org/reva/pull/2028
Adds Nextcloud as a user backend (Nextcloud drivers for ‘auth’ and ‘user’). Also adds back the Nextcloud storage integration tests.
https://github.com/cs3org/reva/pull/2043
https://github.com/cs3org/reva/issues/1986 https://github.com/cs3org/reva/pull/2006
We added a new backend for the userprovider that is backed by an owncloud 10 database. By default
the user_id
column is used as the reva user username and reva user opaque id. When setting
join_username=true
the reva user username is joined from the oc_preferences
table
(appid='core' AND configkey='username'
) instead. When setting
join_ownclouduuid=true
the reva user opaqueid is joined from the oc_preferences
table
(appid='core' AND configkey='ownclouduuid'
) instead. This allows more flexible
migration strategies. It also supports a enable_medial_search
config option when
searching users that will enclose the query with %
.
https://github.com/cs3org/reva/pull/1994
https://github.com/cs3org/reva/pull/1971
Updated the CS3 API to include the new share grantee filter and added utility methods for creating share filters. This will help making the code more concise.
https://github.com/cs3org/reva/pull/2044
The new Manager role is equivalent to a Co-Owner with the difference that a Manager can create grants on the root of the Space. This means inviting a user to a space will not require an action from them, as the Manager assigns the grants.
https://github.com/cs3org/reva/pull/2065
In order for clients to be aware of the new spaces feature we need to enable the spaces
flag on
the capabilities’ endpoint.
https://github.com/cs3org/reva/pull/2015
DecomposedFS is aware now of the concept of Spaces, and supports for creating them.
https://github.com/cs3org/reva/pull/2041
Earlier we could only use the collector URL directly, but since an agent can be deployed as a sidecar process it makes much more sense to use it instead of the collector directly.
https://github.com/cs3org/reva/pull/2029