|Aspera Sync / Running async|
Aspera nodes that require access key authentication (ATCM, ATS) can be used as synchronization endpoints by configuring the async database on the node and authenticating the async session with a Basic token. A Basic token requires a docroot on the server and allows access to all files in the docroot.
> asconfigurator -x "set_node_data;async_db_dir,filepath"
> asconfigurator -x "set_user_data;user_name,username;absolute,filepath"
ATS: In Aspera Client, click Connections to open the Connection Manager window. Click the button. Select Create a connection from a new ATS Access Key and click OK. Enter the following information:
Click OK. The Aspera Client automatically launches your browser and prompts you for your Aspera ID credentials (your ATS login). The ATS access key that is generated is not displayed after you add the connection; to retrieve your ATS access key and secret key, click Tools > Manage ATS and search for the access key by name.
Record the Access Key ID and secret for use in the next step.
> base64.exe infile outfile
The basic auth token in the outfile looks similar to the following:
Open the file and delete any line breaks so that the token text is one continuous string.
> async -N atcm_sync -d /images -r email@example.com:/data/images -K push -W "Basic ZGlEZXVGTGNwRzlJWWRzdnhqMFNDcTRtT29oTkpUS3ZwNVEyblJXakRnSUE6YXNwZXJh"
If you are synchronizing with an ATC node, specify its location as its IP address, rather than the DNS name, to ensure that the file is transferred to the correct node.