Skip to content

Releases: cs3org/reva

v1.0.0

28 Jul 09:01
@labkode labkode
v1.0.0
8c8cac8
Compare
Choose a tag to compare
v1.0.0

Changelog for reva 1.0.0 (2020-07-28)

The following sections list the changes in reva 1.0.0 relevant to
reva users. The changes are ordered by importance.

Summary

  • Fix #941: Fix initialization of json share manager
  • Fix #1006: Check if SMTP credentials are nil
  • Chg #965: Remove protocol from partner domains to match gocdb config
  • Enh #986: Added signing key capability
  • Enh #922: Add tutorial for deploying WOPI and Reva locally
  • Enh #979: Skip changelog enforcement for bot PRs
  • Enh #965: Enforce adding changelog in make and CI
  • Enh #1016: Do not enforce changelog on release
  • Enh #969: Allow requests to hosts with unverified certificates
  • Enh #914: Make httpclient configurable
  • Enh #972: Added a site locations exporter to Mentix
  • Enh #1000: Forward share invites to the provider selected in meshdirectory
  • Enh #1002: Pass the link to the meshdirectory service in token mail
  • Enh #1008: Use proper logging for ldap auth requests
  • Enh #970: Add required headers to SMTP client to prevent being tagged as spam
  • Enh #996: Split LDAP user filters
  • Enh #1007: Update go-tus version
  • Enh #1004: Update github.com/go-ldap/ldap to v3
  • Enh #974: Add functionality to create webdav references for OCM shares

Details

  • Bugfix #941: Fix initialization of json share manager

    When an empty shares.json file existed the json share manager would fail while trying to
    unmarshal the empty file.

    #941
    #940

  • Bugfix #1006: Check if SMTP credentials are nil

    Check if SMTP credentials are nil before passing them to the SMTPClient, causing it to crash.

    #1006

  • Change #965: Remove protocol from partner domains to match gocdb config

    Minor changes for OCM cross-partner testing.

    #965

  • Enhancement #986: Added signing key capability

    The ocs capabilities can now hold the boolean flag to indicate url signing endpoint and
    middleware are available

    #986

  • Enhancement #922: Add tutorial for deploying WOPI and Reva locally

    Add a new tutorial on how to run Reva and Wopiserver together locally

    #922

  • Enhancement #979: Skip changelog enforcement for bot PRs

    Skip changelog enforcement for bot PRs.

    #979

  • Enhancement #965: Enforce adding changelog in make and CI

    When adding a feature or fixing a bug, a changelog needs to be specified, failing which the build
    wouldn't pass.

    #965

  • Enhancement #1016: Do not enforce changelog on release

    While releasing a new version of Reva, make release was failing because it was enforcing a
    changelog entry.

    #1016

  • Enhancement #969: Allow requests to hosts with unverified certificates

    Allow OCM to send requests to other mesh providers with the option of skipping certificate
    verification.

    #969

  • Enhancement #914: Make httpclient configurable

    • Introduce Options for the httpclient (#914)

    #914

  • Enhancement #972: Added a site locations exporter to Mentix

    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.

    #972

  • Enhancement #1000: Forward share invites to the provider selected in meshdirectory

    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.

    sciencemesh/sciencemesh#139
    #1000

  • Enhancement #1002: Pass the link to the meshdirectory service in token mail

    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.

    sciencemesh/sciencemesh#139
    #1002

  • Enhancement #1008: Use proper logging for ldap auth requests

    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.

    #1008

  • Enhancement #970: Add required headers to SMTP client to prevent being tagged as spam

    Mails being sent through the client, specially through unauthenticated SMTP were being
    tagged as spam due to missing headers.

    #970

  • Enhancement #996: Split LDAP user filters

    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.

    #996

  • Enhancement #1007: Update go-tus version

    The lib now uses go mod which should help golang to sort out dependencies when running go mod tidy.

    #1007

  • Enhancement #1004: Update github.com/go-ldap/ldap to v3

    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
    go-ldap/ldap#129 (comment)

    #1004

  • Enhancement #974: Add functionality to create webdav references for OCM shares

    Webdav references will now be created in users' shares directory with the target set to the
    original resource's location in their mesh provider.

    #974

Assets 18
Loading

v0.1.0

18 Mar 14:14
@labkode labkode
v0.1.0
bc0884d
Compare
Choose a tag to compare
v0.1.0

Changelog for reva 0.1.0 (2020-03-18)

The following sections list the changes in reva 0.1.0 relevant to
reva users. The changes are ordered by importance.

Summary

  • Enh #402: Build daily releases
  • Enh #416: Improve developer experience
  • Enh #468: remove vendor support
  • Enh #545: simplify configuration
  • Enh #561: improve the documentation
  • Enh #562: support home storages

Details

  • Enhancement #402: Build daily releases

    Reva was not building releases of commits to the master branch. Thanks to @zazola.

    Commit-based released are generated every time a PR is merged into master. These releases are
    available at: https://reva-releases.web.cern.ch

    #402

  • Enhancement #416: Improve developer experience

    Reva provided the option to be run with a single configuration file by using the -c config flag.

    This PR adds the flag -dev-dir than can point to a directory containing multiple config files.
    The reva daemon will launch a new process per configuration file.

    Kudos to @refs.

    #416

  • Enhancement #468: remove vendor support

    Because @dependabot cannot update in a clean way the vendor dependecies Reva removed support
    for vendored dependencies inside the project.

    Dependencies will continue to be versioned but they will be downloaded when compiling the
    artefacts.

    #468
    #524

  • Enhancement #545: simplify configuration

    Reva configuration was difficul as many of the configuration parameters were not providing
    sane defaults. This PR and the related listed below simplify the configuration.

    #545
    #536
    #568

  • Enhancement #561: improve the documentation

    Documentation has been improved and can be consulted here: https://reva.link

    #561
    #545
    #568

  • Enhancement #562: support home storages

    Reva did not have any functionality to handle home storages. These PRs make that happen.

    #562
    #510
    #493
    #476
    #469
    #436
    #571

Assets 18
Loading

v0.0.1

24 Oct 16:20
@labkode labkode
v0.0.1
29b013f
Compare
Choose a tag to compare
v0.0.1

Changelog for Reva 0.0.1 (2019-10-24)

The following sections list the changes in Reva 0.0.1 relevant to
Reva users. The changes are ordered by importance.

Summary

  • Enh #334: Create release procedure for Reva

Details

  • Enhancement #334: Create release procedure for Reva

    Reva did not have any procedure to release versions. This PR brings a new tool to release Reva
    versions (tools/release) and prepares the necessary files for artefact distributed made
    from Drone into Github pages.

    https://github.com/reva/reva/pull/334

Assets 18
Loading