Road Map Of Aspera Shares
IBM Aspera Shares-1.9.15
You can encrypt database passwords with the Aspera: encrypt_database_password rake task. To decrypt passwords, you can use the aspera:decrypt_database_passwords rake task. (AS-88)
Shares displays the current patch level in the footer. (AS-411) and you can allow websites fronting Shares to handle authentication for Shares. (AS-247 CIM-1784)
Upgraded Nginx to 1.18.0. (AS-429 CIM-3352)
Upgraded OpenSSL to version 1.1.1. (AS-457)
AS-468 – Upgraded ruby-saml gem to version 1.11.0.
Shares now supports RHEL 8 and Centos 8. (AS-465)
Added HTTP headers to responses. (AS-463)
Implemented security hardening measures. (AS-359)
IBM Aspera Shares-126.96.36.199
Intuitive Shares web interface provides secure access to a consolidated, location independent view of all content to which a user is authorized.
The administrator role has complete control over user, group, and directory service access to content and can define granular permission settings over all end-user operations such as browsing, uploading, downloading, making new directories, renaming or deleting files and directories
Transfers initiated through the Shares web interface are managed by the Aspera Connect Plug-in — users do not need to have a native client application installed.
Transfers are powered by Aspera’s unique FASP protocol. Attachments are sent securely at high speed, regardless of file size, distance, or network.
IBM Aspera Shares-1.9.14
Shares email address validation for new user accounts is now case-insensitive. For example, if there is an account with the email address email@example.com, Shares does not allow creation of a new account with the email USER@ibm.us.com.
You can now use a rake task to export user and group memberships (CIM-2166).You can now use the -t, –group-type option with the data: group: share_permissions rake task to distinguish if the group is from Active Directory or from SAML
IBM Aspera Shares-1.9.12
IBM Aspera Shares users may upload and download content to and from a share if they are authorized to do so by clicking the corresponding action buttons shown when browsing a share. Transfers are managed by IBM Aspera Connect Browser Plug-in.
You can transfer content from any share for which you have download permission to any share for which you have upload permission. Conversely, you can transfer content to any share for which you have upload permission from any share for which you have download permission.
IBM Aspera Shares-1.9.11
IBM Aspera Shares users may upload and download content to and from a share if they are authorized to do so by
clicking the corresponding action buttons shown when browsing a share. Transfers are managed by IBM Aspera
Connect Browser Plug-in
When initiating a transfer, Shares opens the transfer in the Connect Browser Plug-In transfer window.
Users with sufficient permissions can adjust file transfer speed by opening the Transfer Monitoring windows.
IBM Aspera Shares-1.9.10
The Manager Permissions page controls how managers of shares can administer users and groups of their shares. Admins can allow managers to administer users and groups through the Shares UI, through the Shares API, or both, by enabling or disabling the following options:
Allow managers to administer users and groups through UI
Allow default Allow managers to administer users and groups through API
These options are disabled by default.
In a common use case, admins may decide that managers should administer users solely through the API and disable access to the Shares UI
IBM Aspera shares 1.9.9
Administrators can use the manager permission to delegate the creation of shares and users to another user without giving that account full administration privileges. Like administrators, managers can view, edit, and remove share authorizations but only for shares that they manage. Assigning a user to a share as its manager gives that user administrative privileges for that share and all inherited subdirectories. If a user creates a new share within a managed share, the manager of the share has administrative rights to the new share.
Though a user with manager permissions effectively becomes the admin for that share, the following restrictions apply:
1.A manager cannot modify or delete the top-level share or any shares above it.
2.A manager cannot create a share at the same level of the first share.
3.For a manager to administer a group, the manager must have manager permissions for all of that group’s shares.
4.A manager cannot authorize new users or groups for shares the manager does not manage.
5.For a manager to change the password or email of a user, the manager must be a manager of all the shares that user is authorized to access.