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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portal, please send email describing the issue to for resolution. For more information about IBM's Ideas program visit



All ideas

Showing 1289 of 1289

Support jwt-bearer grant type for consumer API

We are build self-services for API providers and consumers by calling provider and consumer system APIs. To authenticate with the self-service, our users use our own enterprise OIDC user registry, which is used for provider and consumer API user r...
2 days ago in API Connect 0 Submitted

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 multi...
2 days ago in Aspera 0 Submitted

Bar file location and Deployment Timestamp for ACE Application

Can you please include bar file location and Deployment Timestamp for ACE Application in WEBUI and with mqsilist command like IIB.
3 days ago in App Connect 0 Submitted

multi-factor authentication (MFA)

Multi-factor authentication (MFA) is must have requirement in today's remote working model to securely validate user identity. Allowing AHST/Aspera Share UN/PW authentication doesn't seems to be an adequate security.
3 days ago in Aspera 0 Submitted

Faspex: Delete files stored on remote sources from expired/deleted packages

Currently, deleting faspex packages older than x days does not delete files on packages created with a remote source. So, they are held indefinitely on storage, needlessly taking up capacity.This would be very useful from a storage management pers...
4 days ago in Aspera 0 Submitted

APIM UI customized environment title

We are using APIC manager UI on daily basis in many different environments and platforms.It is easy to get confused what platform you're in fact operating on as they all looks the same, only by checking catalogs names or url can help but they stil...
5 days ago in API Connect 0 Under review

Install QRADAR

Hi we are been asked about install the QRADAR application in ours appConnect applications servers.It was opened a ticket to the support (TS005744542) The support told us in this ticket, that is not possible.With this answer we return to security t...
9 days ago in App Connect 1 Submitted

Headless Aspera Connect

We currently have Aspera Connect running 24/7 on a virtual machine to run all our automated transfers. Allowing Connect to run in a headless mode would better fit this use case. We currently need to keep a user logged into the local console sessio...
11 days ago in Aspera 2 Needs more information

Possibility to onboard users with different user registries including the ability to have a Sign-up page that defaults to the correct one dependent on audience.

Due to that we today use three different user registries depending on type of user we would like to be able to invite users in Developer’s Portal to the correct user registry. The three types of users we have identified so far are Administrators, ...
11 days ago in API Connect 0 Under review

Different invitation templates depending on the targeted audience in developer’s portal.

Due to that we today use three different user registries depending on type of user we would like to have different invitation templates depending on user type. Today when inviting users in developer’s portal you are only able to have one common em...
11 days ago in API Connect 0 Under review