Security

/opt/aspera/faspex/config/faspex.yml

Inside faspex.yml, paste the following (where StrongPasswordRegex is the password criteria as a regular expression and StrongPasswordRequirements is the description that appears to the user underneath the field):

StrongPasswordRegex: (?=.*[A-Z])(?=.*(\d|\W|_)).{7,} 
StrongPasswordRequirements: "Password must meet this criteria..." 

When set to Yes, prevents an Faspex user (even if they have permissions to send to all Aspera Faspex users) from being able to see the entire user directory. You can override this setting on a user-by-user basis by editing their permissions.

After a user self-registers (either moderated or unmoderated), his or her account will inherit the permissions of the configured template user and will automatically become members of designated workgroup(s). To configure the template user, go to Accounts > Pending Registrations > template user. To set the workgroups that newly created users will join, click the workgroups link. Although self-registered users are not allowed to send packages to other self-registered users, by default, you can modify this setting by marking the Self-registered users can send to one another checkbox.

/opt/aspera/faspex/config/faspex.yml

EnforceSelfRegisteredUserEmailUniqueness: true

A Public URL can be used by external senders to submit packages to both registered Aspera Faspex users and dropboxes. The benefit of using a Public URL is in the time-savings, such that external senders no longer need to be individually invited to submit a package (although that functionality still exists). When a Public URL is enabled and posted to a an email, instant message, website, etc., the following workflow occurs:

1. The external sender clicks the Public URL (which could be for either a dropbox or a registered Aspera Faspex user).
2. The sender is directed to page where he or she is asked to enter and submit an email address.
3. A private link is automatically emailed to the sender.
4. The sender clicks the private link and is automatically redirected to a dropbox or Aspera Faspex user package submission page.
5. Once the package is submitted through the private link, the dropbox or Faspex user receives it.

Thus, when the field Allow public URL is enabled (e.g. set to Allow), the Public URL feature is turned on for all Aspera Faspex dropboxes and registered users. If the Allow dropboxes to individually enable/disable their own public URLs checkbox is enabled as well, then individual dropboxes can override the server setting and turn off this feature. Individual Aspera Faspex users, on the other hand, can override the Public URL server setting for their own accounts by going to Preferences > Misc > Enable public URL and disabling the checkbox.

• Always: Always use EAR. When enabled, users will be required, on upload, to enter a password to encrypt the files on the server. Subsequently, recipients will be required to enter the password to decrypt protected files as they are being downloaded. Note that if a user elects to keep downloaded files encrypted, then they do not need to enter a password until they attempt to decrypt the files locally. This feature is not fully enforced unless the Aspera Faspex Server Administrator also updates the aspera.conf configuration file (which is not automatically modified by Aspera Faspex). The Administrator may update aspera.conf manually, as well as using the Aspera Enterprise Server™ GUI. For additional information, please refer to Note on Encryption at Rest.
• Never: (this is the default for new installations) Do not use EAR
• Optional: User may choose at send time whether to encrypt or not
• Allow dropboxes to have their own encryption settings: (off is the default for new installations) If this global setting is unchecked, you cannot set EAR for individual dropboxes. If checked, you can adjust EAR settings for each dropbox. Please see Create and Manage Dropboxes for details.