Released on 28.02.2019 as an update of StoRM v. 1.11.15.
This release introduces:
More information can be found in the StoRM WebDAV service installation and configuration guide and in the StoRM WebDAV support for Third Party Copy transfers guide.
Update the StoRM WebDAV package:
yum update storm-webdav
StoRM WebDAV 1.1.0 introduces changes in the template configuration file:
and in the configuration files for the logging facilities:
The new files provided by the updated packages must be used, which will show up as .rpmnew files (when there are local changes to the configuration), i.e.:
/etc/sysconfig/storm-webdav.rpmnew /etc/storm/webdav/logback.xml.rpmnew /etc/storm/webdav/logback-access.xml.rpmnew
We recommend that you backup your current configuration file:
cp /etc/sysconfig/storm-webdav /etc/syconfig/storm-webdav.bkp
And port the changes in such file to the new template:
cp /etc/sysconfig/storm-webdav.rpmnew /etc/syconfig/storm-webdav
Support for third-party transfers is implemented by supporting a COPY method request where the Source or Destination header points to a remote resource. In order to tell apart remote resources from local ones, StoRM webdav must be configured accordingly.
This is done via the
environment variables in
/etc/sysconfig/storm-wedav, which allow to define
for which hostnames (and aliases) the service is serving requests.
To support delegation without proxy certificates, StoRM WebDAV introduces token-based authorization via a local OAuth authorization server that can issue authorization tokens to clients authenticated with VOMS proxies.
Instructions on how to configure properly the authorization server are given in this document. The default configuration should work out of the box for non-replicated deployments, but be sure to
STORM_WEBDAV_REQUIRE_CLIENT_CERT=falseso that client certificate authentication is no longer required
Once the above actions have been performed, you can restart the service with the following command:
service storm-webdav restart
Check the the StoRM WebDAV installation and configuration guide for detailed installation and configuration information.
The following issues have been discovered, introduced with initial support for OAuth/OpenID Connect authentication and authorization:
The main consequence of the issues above is that the StoRM WebDAV service would
not start in case
iam-test.indigo-datacloud.eu is not reachable for some
To workaround this problem, include the following Java property setting:
in the value of the STORM_WEBDAV_JVM_OPTS envirornment variable in the StoRM WebDAV sysconfig file:
STORM_WEBDAV_JVM_OPTS="-Xms256m -Xmx512m -Djava.io.tmpdir=/var/lib/storm-webdav/work -Doauth.issuers"
And restart the service.