Skip to Main Content

This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Functionality already exists
Workspace Aspera Ideas
Created by Guest
Created on Jun 11, 2021

Aspera HSTS and Server-side EAR - configuring for only certain paths

Looking to configure HSTS so that only certain paths are to be encrypted with server-side EAR while other paths are not.

For example, in a Faspex situation, where you have a configured node, with a particular docroot (say \data), you can have multiple shares configured on the same node (\faspex1 and \faspex2). If we want the files written to one share to have server-side ear, but others to not, that is not currently possible.



For example, \data\faspex1 might be a general faspex share where you might want server-side EAR, while \data\faspex2 might be a share for a specific workgroup/dropbox where the files need to be accessed unencrypted from a back-end share and therefore you can't have server-side EAR in place.

Idea priority Medium
  • Guest
    Jun 22, 2021

    The request here is to encrypt only certain doc paths for the SAME user.

    In the context of Faspex for example, a node is configured for a user, so setting up separate users is not possible, at least not without creating completely different nodes for each of the shares, and this would result in issues with the monitoring of the nodes because now the same servers would be monitored multiple times.

  • Admin
    Brian Din
    Jun 21, 2021

    This can be accomplished with HSTS docroots. Multiple users can have the same docroot.