pre-release B2SAFE irods-eudat-b2safe-4.3.0-2 configuration conversion and configs

[cookie33]

when upgrading b2safe from 4.2 to 4.3 it uses a json config file. to install the system. There is a supplied program to do this conversion. There are several problems with it:

• the convert script did not strip “iRODS” from the “irods_dir” in the install.json config file. This is the directory for iRODS 4.1.x. This needs to be fixed.

• “server_api_reg" and “server_api_pub" need to be filled in in the install.json. There is no warning/message about it. This needs to be fixed.

• "handle_users" and/or “handle_groups" need to be filled in properly in the install.json. This is being enforced using the “msi_pid” microservices. This needs to be in the install.txt or conversion script.

• the “msi_pid” microservice can not use the mentioned CA. It needs to be adapted to for instance in the install.json config file:
  "handle_https_verify": "/etc/pki/ca-trust/source/anchors/TERENA-SSL-CA-3.pem”,
  This needs to be mentioned. The error which happens if this is not set can be seen in the iRODS logfiles.

• we need to update /etc/irods/irods_pid.json in the lookup section. It has to use: “URL_IRODS_PREFIX" in stead of “URL_WEBDAV_PREFIX”. This because we do not use the http api.