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 Under review
Categories Inflight
Created by Guest
Created on Apr 29, 2026

Add the ability to generate and manage ED25519 SFTP user identity keys in Legacy Inflight

The current Legacy Inflight user interface does not provide an option to generate ED25519 key types. We request that this capability be enabled.

What is your industry? Retail
How will this idea be used?

This option is useful when using key based authentication with key type Ed25519

  • Admin
    Manoj Panda
    May 5, 2026

    Thank you @Guest

  • Guest
    May 5, 2026

    Scope of support

    Is the expectation limited to key generation in the UI, or should Legacy Inflight also support importing externally generated ED25519 keys?

    Response : Both

     

    Usage context

    Is ED25519 required for new SFTP users only, or should existing users be able to rotate to ED25519 keys?

    Response : Both

    Backward compatibility

    Are there any environments, partners, or servers where ED25519 would not be supported and need to coexist with RSA/DSA/ECDSA keys?

    Response : Yes

    The solution should allow coexistence with existing key types (RSA, DSA, ECDSA) to ensure backward compatibility with environments or partners that do not yet support ED25519. The key type used should remain partner‑specific and configurable.

    Lifecycle management

    Should the UI also support key rotation, regeneration, and deletion for ED25519 keys, similar to other key types?

    Response : Yes, It should support all the key related operations via Inflight UI.

    Compliance or mandate

    Is this driven by a customer security standard, regulatory requirement, or corporate cryptography policy?

     

    Response : In case of Electrolux, It's the partner security standard. 

  • Admin
    Manoj Panda
    May 4, 2026

    Dear Lokesh,

    Thank you for submitting this enhancement request and highlighting a clear functional gap in Legacy Inflight. We appreciate you calling out the need in a direct and focused way.

    This RFE points out that the Legacy Inflight UI does not currently support generating ED25519 SFTP user identity keys, despite ED25519 being a modern, widely adopted key type for key‑based authentication. As customers increasingly standardize on ED25519 for improved security and compatibility, the lack of native generation support forces them to rely on external tooling or legacy key types, creating friction and inconsistency in secure onboarding and operations.

    Enabling ED25519 key generation within Legacy Inflight would improve security posture, align with current SFTP best practices, and simplify user and key management for customers already using ED25519‑based authentication.

    To properly scope and assess this request, the PM should clarify:

    1. Scope of support

      • Is the expectation limited to key generation in the UI, or should Legacy Inflight also support importing externally generated ED25519 keys?

    2. Usage context

      • Is ED25519 required for new SFTP users only, or should existing users be able to rotate to ED25519 keys?

    3. Backward compatibility

      • Are there any environments, partners, or servers where ED25519 would not be supported and need to coexist with RSA/DSA/ECDSA keys?

    4. Lifecycle management

      • Should the UI also support key rotation, regeneration, and deletion for ED25519 keys, similar to other key types?

    5. Compliance or mandate

      • Is this driven by a customer security standard, regulatory requirement, or corporate cryptography policy?

    These clarifications will help ensure ED25519 support is implemented in a way that is secure, usable, and consistent with existing Inflight key‑management behavior.

    Thanks again for raising this targeted and relevant enhancement request—we value your feedback and partnership in continuing to modernize the platform.

    —
    Manoj Panda
    Senior Product Manager
    IBM Sterling