|Connect Server Web UI Setup|
Set up the Apache Web Server to host the Web UI for IBM Aspera Connect Server.
With administrative account access (i.e., write/read permissions), open your Apache configuration file in a text editor. To locate this file, please refer to the table below for your specific OS.
|RedHat, Centos, Fedora||/etc/httpd/conf/httpd.conf|
Within this file, locate the ServerName section and verify that the server's name resolves correctly. Use one of the following examples to set the Connect Server domain name or IP address, respectively:
ServerName www.ConnectServerName.com ServerName 10.0.0.1
Locate the line that states UseCanonicalName and verify that it is set to off.
Add the following section at the end of the configuration file:
#BEGIN_ASPERA <Directory /opt/aspera/var/webtools> AllowOverride All Allow from all </Directory> <Directory /opt/aspera/var/webtools/scripts> AddHandler cgi-script .pl SetHandler cgi-script Options +ExecCGI AllowOverride All </Directory> ScriptAlias /aspera/scripts/ "/opt/aspera/var/webtools/scripts/" Alias /aspera/ "/opt/aspera/var/webtools/" #END_ASPERA
Your Apache web server must have both the cgi and the dir modules enabled. To do so, run the commands listed in the table below for your specific version of Apache.
|2.2|| Run the following commands to enable the requisite modules:
$ sudo a2enmod dir $ sudo a2enmod cgi $ sudo a2enmod cgid
Important: These commands do not work on RHEL or CentOS. For these versions of Linux, you must edit the Apache configuration file as described below for Apache 1.3 and 2.0.
|1.3, 2.0||In Apache's configuration file, add or un-comment the following lines:
LoadModule dir_module modules/mod_dir.so LoadModule cgi_module modules/mod_cgi.so
For instructions on generating an RSA Private Key, Certificate Signing Request (CSR) and optional self-signed certificate using OpenSSL, please refer to the topic Create an SSL Certificate (Apache). Then, once you have created your private key and Certificate (or you are using the unsigned Certificate provided by Aspera), please refer to the topic Enable SSL (Apache) for instructions on enabling SSL on your system.
SELinux (Security-Enhanced Linux), an access control implementation, may affect web UI access. For information on how to disable SELinux, see Disabling SELinux.
After modifying the Apache configuration file, save and close it. Then, based on your version of Apache, use the following commands to restart it:
$ /etc/init.d/apache restart
Note: This command does not work on RHEL or CentOS. You must use the command described below for Apache 1.3 and 2.0.
|Apache 1.3, 2.0||
$ /etc/init.d/httpd restart
Enabling system-level security allows the Web UI to accurately display the users' files and show or hide controls depending on users' permissions (this includes the delete and make directory functions). To enable system-level security, run the following command (as root) in a Terminal window:
$ sudo /opt/aspera/sbin/enablesecure enable
Once the script is executed, you will be prompted to input the name of the Apache user.
User running apache (default apache):
Based on your input, the script generates text similar to the following. Use visudoers to copy and paste the generated text into your /etc/sudoers file. In the following example output, apache is the account that is running Apache and /opt/aspera is the Aspera installation directory.
# BEGIN Aspera Connect Server # The user account that runs the web server will impersonate # the logged-in user to present that user's files and folders. Defaults env_keep += "SERVER_NAME REQUEST_URI REQUEST_METHOD REMOTE_USER QUERY_STRING CONTENT_LENGTH SESSION_ID CSRF_TOKEN" Defaults:apache !requiretty apache ALL=(ALL) NOPASSWD: /opt/aspera/var/webtools/scripts/aspera-dirlist.pl, SETENV: /opt/aspera/var/webtools/scripts/aspera-dirlist.pl # END Aspera Connect Server
To disable the secure permissions, run the enablesecure script again with the argument disable.
$ sudo /opt/aspera/sbin/enablesecure disable