The following sections list the changes in reva 1.24.0 relevant to reva users. The changes are ordered by importance.
Currently, the viewMode passed on /app/open is taken without validating the actual user’s permissions. This PR fixes this.
https://github.com/cs3org/reva/pull/3805
A bug was preventing setting some capabilities (ResharingDefault and DenyAccess) for files sharing from the configuration file
https://github.com/cs3org/reva/pull/3771
https://github.com/cs3org/reva/pull/3749
https://github.com/cs3org/reva/pull/3723
In a read only share, a stat could fail, beacause the EOS storage driver was not able to create the version folder for a file in case this did not exist. This fixes this bug impersonating the owner of the file when creating the version folder.
https://github.com/cs3org/reva/pull/3765
In a read-only share, while listing a folder, for resources not having a version folder, the returned resource id was wrongly the one of the original file, instead of the version folder. This behavior has been fixed, where the version folder is always created on behalf of the resource owner.
https://github.com/cs3org/reva/pull/3786
https://github.com/cs3org/reva/pull/3787
I’ve fixed Makefile using sh which is defaulted to dash in ubuntu, dash doesn’t support [[ ...
]]
syntax and Makefile would throw /bin/sh: 1: [[: not found
errors.
https://github.com/cs3org/reva/issues/3773 https://github.com/cs3org/reva/pull/3780
https://github.com/cs3org/reva/pull/3873
In the EOS storage driver, the remove acl operation was a no-op. After removing a share, the recipient of the share was still able to operate on the shared resource. Now this has been fixed, removing correctly the ACL from the shared resource.
https://github.com/cs3org/reva/pull/3794
https://github.com/cs3org/reva/pull/3838
https://github.com/cs3org/reva/pull/3878
https://github.com/cs3org/reva/issues/3810 https://github.com/cs3org/reva/pull/3813
https://github.com/cs3org/reva/pull/3770
https://github.com/cs3org/reva/pull/3852
https://github.com/cs3org/reva/issues/3858 https://github.com/cs3org/reva/pull/3859
https://github.com/cs3org/reva/issues/3846 https://github.com/cs3org/reva/pull/3847
https://github.com/cs3org/reva/issues/3864 https://github.com/cs3org/reva/pull/3869
https://github.com/cs3org/reva/pull/3762
Sharing can be disable in the user share provider for some paths, but the storage provider was
still sending the sharing permissions for those paths. This adds a config option in the storage
provider, minimum_allowed_path_level_for_share
, to disable sharing permissions for
resources up to a defined path level.
https://github.com/cs3org/reva/pull/3717
Currently it is only possible to restore a file version, replacing the actual file with the selected version. This allows an user to download a version file, without touching/replacing the last version of the file
https://github.com/cs3org/reva/pull/3766
We’ve added support for compiling reva with static linking enabled. It’s possible to do so with
the STATIC
flag: make revad STATIC=true
https://github.com/cs3org/reva/pull/3733
We’ve added support to tag eos traffic
https://github.com/cs3org/reva/pull/3778
Expose the expected WebDAV endpoint for OCM by OC10 and Nextcloud as described in https://github.com/cs3org/OCM-API/issues/70#issuecomment-1538551138 to allow reva providers to participate to mesh.
https://github.com/cs3org/reva/issues/3855 https://github.com/cs3org/reva/pull/3868
https://github.com/cs3org/reva/pull/3719
The OCM tutorial in the doc was missing the example on how to access the received resources. Now the tutorial contains all the steps to access a received resource using the WebDAV protocol.
https://github.com/cs3org/reva/pull/3783
Several new flags, like site infrastructure and service status, are now gathered and exposed by Mentix.
https://github.com/cs3org/reva/pull/3750
The OIDC auth driver supports now multiple issuers. Users of external providers are then
mapped to a local user by a mapping files. Only the main issuer (defined in the config with
issuer
) and the ones defined in the mapping are allowed for the verification of the OIDC
token.
https://github.com/cs3org/reva/pull/3839
This PR implements the new OCM v1.1 specifications for the /ocm-provider endpoint.
https://github.com/cs3org/reva/pull/3772
https://github.com/cs3org/reva/pull/3619
Following cs3org/cs3apis#206, we add the fields to ensure backwards compatibility with OCM
v1.0. However, if the protocol.options
undocumented object is not empty, we bail out for
now. Supporting interoperability with OCM v1.0 implementations (notably Nextcloud 25) may
come in the future if the undocumented options are fully reverse engineered. This is reflected
in the unit tests as well.
Also, added viewMode to webapp protocol options (cs3org/cs3apis#207) and adapted all SQL code and unit tests.
https://github.com/cs3org/reva/pull/3757
https://github.com/pondersource/sciencemesh-php/issues/166 https://github.com/cs3org/reva/pull/3695
https://github.com/cs3org/reva/pull/3722
For lightweight accounts
GetMembers
method in the group driver * Reduced network
transfer size by requesting only needed fields for GetMembers
methodhttps://github.com/cs3org/reva/pull/3821
When generating and listing OCM tokens
To enhance user expirience, instead of only sending the token, we send directly the URL for accepting the invitation workflow.
https://github.com/cs3org/reva/pull/3724
New type of service (along with http and grpc) which does not have a listening server. Useful for the notifications service and others in the future.
https://github.com/cs3org/reva/pull/3824