IBM Aspera Faspex gives you the ability to allow non-registered users
to request accounts on the Faspex login page. This relieves the workload of admins
and managers. You must ensure that proper security settings have been put into place
before allowing self-registration.
-
The self-registration feature is turned off by default. Go to and find the Registrations section.
-
From the Self registration drop down menu, choose
between three options:
- None: Self-registration is not allowed.
- Moderated: An admin must approve the account
before it is created.
- Unmoderated: Once a user registers an account,
the account is automatically created.
If you allow self-registration, Aspera recommends you use the
Moderated setting for security purposes.
Warning: If self-registration is enabled, a user can use it to find
out whether a certain account exists on the server. If a user attempts to
self-register a duplicate account, then the user receives a prompt stating
that the user already exists.
-
Configure the moderation settings in the table below:
Configuration |
Description |
Terms of service |
If text is set, Faspex requires users to accept the terms of
service in order to register an account |
Notify the following emails to
approve |
The email addresses Faspex notifies for moderation. This option
is only available if you are using the Moderated self-registration
setting Note: These email addresses are not validated against
existing Faspex admins or managers, but only admins and managers
can approve account requests.
|
Block the following email domains from
self-registering |
New users are not allowed to register accounts using emails
from these email domains |
Require external users to
register |
Require external users to register a Faspex account to download
packages |
Registration instructions |
Text that appears above the Create an
account button on the Faspex login page |
Self-registered users are allowed to send packages
to one another |
Self-registered users can send packages to other
self-registered users. |
-
Click Update to save changes.
-
(Optional) To prevent a self-registered account from having the same email
address as a full Faspex user, admins can add a special option to
faspex.yml.
You find
faspex.yml in the following directory:
/opt/aspera/faspex/config/faspex.yml
Inside
faspex.yml, within the Production section, paste
the following option and set it to
true
:
EnforceSelfRegisteredUserEmailUniqueness: true
If users are allowed to self-register, they see the option to Create an
account on the login page. After a user clicks this button and
completes the form, admins are required to Approve or
Deny the account. For more information on approving or
denying accounts, see Approving or Denying Pending Registrations.
After a user self-registers, the new account inherits the permissions of the
configured template user and automatically becomes a member of designated
workgroups. To configure the template user, go to Accounts > Pending
Registrations and click the template user
link. For more information about configuring the template user, see Configure Self-Registration Template User.