The following sections list the changes in reva 1.0.0 relevant to reva users. The changes are ordered by importance.
When an empty shares.json file existed the json share manager would fail while trying to unmarshal the empty file.
https://github.com/cs3org/reva/issues/941 https://github.com/cs3org/reva/pull/940
Check if SMTP credentials are nil before passing them to the SMTPClient, causing it to crash.
https://github.com/cs3org/reva/pull/1006
Minor changes for OCM cross-partner testing.
https://github.com/cs3org/reva/pull/965
The ocs capabilities can now hold the boolean flag to indicate url signing endpoint and middleware are available
https://github.com/cs3org/reva/pull/986
Add a new tutorial on how to run Reva and Wopiserver together locally
https://github.com/cs3org/reva/pull/922
Skip changelog enforcement for bot PRs.
https://github.com/cs3org/reva/pull/979
When adding a feature or fixing a bug, a changelog needs to be specified, failing which the build wouldn’t pass.
https://github.com/cs3org/reva/pull/965
While releasing a new version of Reva, make release was failing because it was enforcing a changelog entry.
https://github.com/cs3org/reva/pull/1016
Allow OCM to send requests to other mesh providers with the option of skipping certificate verification.
https://github.com/cs3org/reva/pull/969
Enhancement #914: Make httpclient configurable
https://github.com/cs3org/reva/pull/914
Mentix now offers an endpoint that exposes location information of all sites in the mesh. This can be used in Grafana’s world map view to show the exact location of every site.
https://github.com/cs3org/reva/pull/972
Added a share invite forward OCM endpoint to the provider links (generated when a user picks a target provider in the meshdirectory service web interface), together with an invitation token and originating provider domain passed to the service via query params.
https://github.com/sciencemesh/sciencemesh/issues/139 https://github.com/cs3org/reva/pull/1000
Currently, we just forward the token and the original user’s domain when forwarding an OCM invite token and expect the user to frame the forward invite URL. This PR instead passes the link to the meshdirectory service, from where the user can pick the provider they want to accept the invite with.
https://github.com/sciencemesh/sciencemesh/issues/139 https://github.com/cs3org/reva/pull/1002
Instead of logging to stdout we now log using debug level logging or error level logging in case the configured system user cannot bind to LDAP.
https://github.com/cs3org/reva/pull/1008
Mails being sent through the client, specially through unauthenticated SMTP were being tagged as spam due to missing headers.
https://github.com/cs3org/reva/pull/970
The current LDAP user and auth filters only allow a single %s
to be replaced with the relevant
string. The current userfilter
is used to lookup a single user, search for share recipients
and for login. To make each use case more flexible we split this in three and introduced
templates.
For the userfilter
we moved to filter templates that can use the CS3 user id properties
{{.OpaqueId}}
and {{.Idp}}
: ``` userfilter =
“(&(objectclass=posixAccount)(|(ownclouduuid={{.OpaqueId}})(cn={{.OpaqueId}})))”
We introduced a new `findfilter` that is used when searching for users. Use it like this: ```
findfilter =
"(&(objectclass=posixAccount)(|(cn={{query}}*)(displayname={{query}}*)(mail={{query}}*)))"
Furthermore, we also introduced a dedicated login filter for the LDAP auth manager: loginfilter = "(&(objectclass=posixAccount)(|(cn={{login}})(mail={{login}})))"
These filter changes are backward compatible: findfilter
and loginfilter
will be
derived from the userfilter
by replacing %s
with {{query}}
and {{login}}
respectively. The userfilter
replaces %s
with {{.OpaqueId}}
Finally, we changed the default attribute for the immutable uid of a user to
ms-DS-ConsistencyGuid
. See
https://docs.microsoft.com/en-us/azure/active-directory/hybrid/plan-connect-design-concepts
for the background. You can fall back to objectguid
or even samaccountname
but you will run
into trouble when user names change. You have been warned.
https://github.com/cs3org/reva/pull/996
The lib now uses go mod which should help golang to sort out dependencies when running go mod
tidy
.
https://github.com/cs3org/reva/pull/1007
In the current version of the ldap lib attribute comparisons are case sensitive. With v3
GetEqualFoldAttributeValue
is introduced, which allows a case insensitive comparison.
Which AFAICT is what the spec says: see
https://github.com/go-ldap/ldap/issues/129#issuecomment-333744641
https://github.com/cs3org/reva/pull/1004
Webdav references will now be created in users’ shares directory with the target set to the original resource’s location in their mesh provider.
https://github.com/cs3org/reva/pull/974