Access keys
These procedures cover the creation of primary and sub-access keys that allow you to
assign access to and delegate management of content in your organization workspaces, shared folders,
and cloud storage. Also in this section, learn about "SSH bypass keys" that are delivered with
Aspera Connect, the transfer client that powers transfers between user desktops and storage.
Primary access keys and sub-access keys
You must use a primary access key to share transfer access outside your AoC organization, such as with a vendor or other collaborator, or with a downstream on-prem application like Aspera Faspex, Shares, or Console. Use a sub-access key to share transfer access inside your AoC org, such as when delegating access and management tasks to a workspace manager.
Create a sub-access key to a workspace
As an administrator with the primary access key, you can generate sub-access key/secret pairs to use as transfer and access credentials for a folder in your cloud storage.
Create a sub-access key to a shared folder
As an administrator with the primary access key, you can generate sub-access key/secret pairs to use as transfer and access credentials for a folder in your cloud storage.
Create a sub-access key to a cloud storage folder
As an administrator with the primary access key, you can generate sub-access key/secret pairs to use as transfer and access credentials for a folder in your cloud storage.
Tracking your node access credentials
Logging in to a transfer server node with access credentials gives the user full access to the content there. AoC never stores the credentials, so it is imperative that you track and store them according to your site's established security practices.
FASP security: Aspera Connect transfer client authorized keys and aspshell
Aspera Connect client uses "SSH bypass" keys. Those keys are delivered with the Aspera Connect client. They allow the client to start a FASP session without requiring a password, while security is implemented on protocol level with a security "token". The associated public keys are enhanced with OpenSSH specific stanza that forces the use of a compatible secure environment: aspshell and token authorization. This article explains how it works.