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 (https://ideas.ibm.com).
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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.
Do not place IBM confidential, company confidential, or personal information into any field.