Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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
Created by Guest
Created on Sep 20, 2024

Active Transfer SFTP Pre-Hooks Support

Enhancement in Active Transfer Server to support SFTP GET and PUT pre-hooks. This will enable the users to perform preparatory actions such as file validation, logging or other security checks, before the file transfer occurs.

  • Pre-hooks to be able to make an HTTP(s) call out to an external system via Integration Server service.

  • These hooks should be able to be called pre file transfer at the SFTP OPEN not at a CLOSE.

  • Pre-hooks should be able to validate at minimum context of the file path, the customer that is doing the transfer.

  • Other identifiers that would help link up an OPEN hook and a CLOSE hook. For example a unique transfer ID or something.

  • If the pre-hook says that the file path is not valid, then the response to the OPEN should be SSH_FX_PERMISSION_DENIED or similar.

Idea priority High
Needed By Quarter