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 Not under consideration
Workspace Aspera Ideas
Created by Guest
Created on Mar 11, 2022

Directory Service support for Node API

All our HSTS transfer users are authenticated via Active Directory, because we like centralized user management. Sometimes we need to create Node API users for integrations with external parties and associate them with transfers users. Those Node API users have their own usernames and password that are stored locally on the HSTS. It would be good if we could authenticate those users via a directory service as well to avoid any local user accounts on the HSTS.

Idea priority Low
  • Admin
    Brian Din
    Mar 15, 2022
    The Node API supports authorization through JWT based bearer 
    tokens. Rather than using Basic Authentication, configure your
    node users with a public key, then use your Active Directory based infrastructure to sign a JWT payload that the Node API can
    validate and then allow authorization.