How to connect Drive to a standalone Enterprise Server

Description

Drive is a transfer client application designed to connect you to a Shares or Faspex server. While not a common setup, users can also connect Drive to a standalone Enterprise Server that is not running with Shares or Faspex.

Prerequisites

In order to connect Drive to Enterprise Server, your Enterprise Server license must be enabled for Drive.

To verify this, run the following command:

# ascp -A

On the Enabled settings line, make sure drive is listed:

Enabled settings: connect, mobile, drive

Instructions

1. Make sure you have a transfer user configured in aspera.conf with a valid docroot that will be used by Drive to transfer and sync with. For more details on configuring a transfer user, see the Enterprise Server product documentation.

2. On your Enterprise Server machine, create a Node API user that will be associated to your transfer user.

You can create a Node API user with the following command:

Linux
# /opt/aspera/bin/asnodeadmin -a -u node_user -p node_password -x transfer_user

Windows
> asnodeadmin.exe -a -u node_user -p node_password -x transfer_user

Mac
$ /Library/Aspera/bin/asnodeadmin -a -u node_user -p node_password -x transfer_user

3. Configure public key authentication.

Add the public key provided by your ES installation to your transfer user’s authorized_keys file.

If it does not exist, create the .ssh folder in your transfer user’s home directory:

# mkdir path/to/home_directory/.ssh

Copy the public key with the following command:

Linux
# cat /opt/aspera/var/aspera_id_dsa.pub >> path/to/home_directory/.ssh/authorized_keys

Windows
> type C:\Program Files (x86)\Aspera\Enterprise Server\var\aspera_id_dsa.pub >> path\to\home_directory\.ssh\authorized_keys

Mac
$ cat /Library/Aspera/var/aspera_id_dsa.pub >> path/to/home_directory/.ssh/authorized_keys

4. (For Linux and Mac) Set the correct permissions and ownership on your transfer server’s SSH directories.

# chmod 600 .ssh/authorized_keys
# chmod 700 .ssh

5. Configure aspera.conf.

The easiest way to configure aspera.conf is with the command-line tool asconfigurator.

Run the following command and substitute a key of your choice to set a token encryption key (it should be a long, random string):

# asconfigurator -x "set_node_data;token_encryption_key,your_key"

Run the following command to set your server hostname or IP address:

# asconfigurator -x "set_server_data;server_name,your_server"

Save the file.

6. Restart Aspera services

Linux
# service asperanoded restart # service asperacentral restart

Mac
$ sudo launchctl stop com.aspera.asperanoded
$ sudo launchctl start com.aspera.asperanoded
$ sudo launchctl stop com.aspera.asperacentral
$ sudo launchctl start com.aspera.asperacentral

Windows
> sc stop asperanoded
> sc start asperanoded

On Windows, go to Control Panel > Administrative Tools > Services. Locate and select Aspera Central and click Start on the left.

7. Create a Drive account

In Drive’s preferences, create a new account.

In the server address box, enter your server’s address with port 9092 as below:

my_server.com:9092

For the username and password, use the Node API credentials you created in step 2.

8. You have now finished connecting Drive to your standalone Enterprise Server.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk