IBM Aspera HST Admin Manual page 274

• Browsing, listing, creating, renaming, or deleting contents.
These instructions explain one way to change a user account or active directory user account so that it uses the
aspshell; there may be other ways to do so on your system.
Run the following command to change the user login shell to aspshell:
# sudo usermod -s /bin/aspshell username
Confirm that the user's shell updated by running the following command and looking for /bin/aspshell at
the end of the output:
# grep username /etc/passwd
username:x:501:501:...:/home/username:/bin/aspshell
Note: If you use OpenSSH, sssd, and Active Directory for authentication: To make aspshell the default
shell for all domain users, first set up a local account for server administration because this change affects all
domain users. Then open /etc/sssd/sssd.conf and change default_shell from /bin/bash to /
bin/aspshell.
5. Set the IBM Aspera Connect public SSH key as an authorized key for the transfer user and ensure that they own
the file.
a) Create the .ssh directory in the user's home folder.
# mkdir /home/aspera_user_1/.ssh/
b) Copy the Connect public SSH key into .ssh and rename it authorized_keys (or append the public key
to authorized_keys if the file already exists).
# cp /opt/aspera/var/aspera_tokenauth_id_rsa.pub /home/
aspera_user_1/.ssh/authorized_keys
c) Ensure that .ssh and .ssh/authorized_keys are owned by the user.
# chown -R aspera_user_1:aspera_user_1 /home/aspera_user_1/.ssh
# chmod 600 /home/aspera_user_1/.ssh/authorized_keys
# chmod 700 /home/aspera_user_1
# chmod 700 /home/aspera_user_1/.ssh
6. Associate the Aspera transfer user with a Node API username and password.
For example, to assign Node API credentials to user aspera_user_1, run the following command:
# /opt/aspera/bin/asnodeadmin -a -u node_api_username -p node_api_passwd -
x aspera_user_1
7. (Optional) Change HTTPS port and/or SSL certificate.
The Aspera Node API provides an HTTPS interface for encrypted communication between node machines (on
port 9092, by default). To modify the HTTPS port, see
277. For information on maintaining and generating a new SSL certificate, see
on page 284.
8. Configure other Node API settings.
• If you want to query transfers by using GET /ops/transfers or to retrieve usage data by using GET /usage,
enable activity logging on the node by running the following command:
# asconfigurator -x "set_server_data;activity_logging,true"
Configuring the IBM Aspera NodeD Service
Setting up SSL for your Nodes
| Set up HST Server for Node API | 274
on page