|Configuring for Other Aspera Products|
The steps below show how to set up IBM Aspera Connect Server as a transfer server for IBM Aspera Shares. The procedure assumes you have already set up your Shares application. For general information on setting up a transfer server (using the Node API), see Managing the Node API.
Follow the instructions in Standard Installation to install Connect Server either locally (on the same host as Shares) or remotely.
The steps below must be performed with administrator permissions.
> asnodeadmin -a -u node_api_username -p node_api_passwd -x aspera_user_1
Adding, modifying, or deleting a node user triggers automatic reloading of the configuration and license files, as well as the user database.
After you've created the operating system account, set up this user in Connect Server. For instructions on setting up a user, see Setting Up Users.
For example, if the file transfer user is aspera_user_1, the standard location for the public key is in the user's home folder, as follows:
The Aspera-provided key file is located in:
C:\Program Files [(x86)]\Aspera\Enterprise Server\var\aspera_tokenauth_id_rsa.pub
Open a command prompt window and run the following commands to create the user's public key folder:
> cd user_home_folder > md .ssh
Use a text editor to create the following file (with no file extension), if the file does not already exist:user_home_folder\.ssh\authorized_keys
Copy the contents of aspera_tokenauth_id_rsa.pub to the authorized_keys file. Update the folder permissions in Windows Explorer by right-clicking the .ssh folder, selecting Properties, and then selecting the Security tab. Here, you can set permissions to read, write, and execute (full control).
<central_server> <persistent_store>enable</persistent_store> </central_server> <server> <server_name>server_ip_or_name</server_name> </server> <http_server> <http_port>8080</http_port> <enable_http>1</enable_http> <https_port>8443</https_port> <enable_https>1</enable_https> </http_server>
Whenever you change these settings, you must restart asperacentral and asperanoded.
To restart these services, click Control Panel > Administrative Tools > Services, right-click Aspera Central and Aspera NodeD, and click Restart.
<user> <name>aspera_user_1</name> <authorization> <transfer> <in> <value>token</value> </in> <out> <value>token</value> </out> </transfer> <token> <encryption_key>gj5o930t78m34ejme9dx</encryption_key> </token> </authorization> <file_system> ... ... </file_system> </user>
Alternatively, you can configure token-authorization settings in a <group> section to be applied to all users in the group. Or, you can configure the settings in the <default> section to apply them globally for all users.
For additional details on configuring token authorization, see Setting Up Token Authorization.