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 (

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
Created by Guest
Created on Jan 11, 2024

Weak Cipher in client certificate

Hi IBM Team,

One of our vendors are trying get connection to Sterling OMS using CURL command, they do have the certificate from DOM QA2 environment.

However when they try to get the connection, they are getting below issue.

$ openssl pkcs12 -info -in qa2.p12 -noout

Enter Import Password:

MAC: sha1, Iteration 100000

MAC length: 20, salt length: 20

PKCS7 Data

Shrouded Keybag: pbeWithSHA1And3-KeyTripleDES-CBC, Iteration 50000

PKCS7 Encrypted data: pbeWithSHA1And40BitRC2-CBC, Iteration 50000

The root cause of this is a weaker cipher used in the client certificate provided for accessing OMS.

They can run Node with legacy SSL support to get around this issue but I would recommend investigating a stronger cipher for the OMS TLS / HTTPS implementation.

This is happening in DOM QA2, could you please investigate on this issue as soon as possible.

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

IBM PMR: TS014940181

IBM Team asked us to create an idea request as this is not available in the product.

  • Admin
    Sampson Wong
    Feb 5, 2024

    The reason for the mismatch is due to openSSL version incompatibility. OpenSSL 1.x and openSSL 3.x. For the meantime due to a tech stack upgrade dependency IBM supports only openSSL 1.X so the client is using a newer openSSL 3.x they will be required to use --legacy option when generating certificate.

    Once IBM performs the java tech stack upgrade, the client can remove the legacy flag and run in full openSSL3 mode. (Exact date of the java upgrade, TBD)

    Marking this not in consideration.