Skip to Main Content
Integration


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 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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Submitted
Workspace Aspera Ideas
Created by Guest
Created on Sep 26, 2025

Update Aspera Console Apache version or decouple Apache to allow component upgrades

I have recently upgraded to Aspera Console 3.4.7 on Windows as my InfoSec team have been complaining about the Apache version I was on when running Aspera Console 3.4.5 (2.4.62), however I was disappointed to see that 3.4.7 only includes an update of Apache to 2.4.63.

Our InfoSec team use Tenable's Nessus components to obtain system vulnerability data, and generate security vulnerability reports that I am expected to remedy, and this is flagging a number of vulnerabilties that are not remedied until 2.4.64.

My InfoSec team are asking when I'm going to be updating this component to remedy the problem, but unfortunately IBM has no timeline for this.... nor is there any option for me to move to a standalone Apache install, as it appears that Apache versions are tightly coupled to Aspera Console versions.

Is there an option to move to an (optional) decoupled approach where I could manage Apache version upgrades separately from Aspera Console versions?

Idea priority High