Skip to Main Content
Cloud Platform

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 portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Delivered
Created by Guest
Created on Oct 28, 2021

Allow customer to configure a trust store for the cve-monitor https connection.

Allow customer to configure a trust store for the cve-monitor https connection. This will require an operator change to allow a trust store Secret to be mounted and a change to cve-monitor to use that trust store in the SSLContext for the https connection.

Idea priority High
  • Guest
    Dec 8, 2021

    More detail about the requirements

    1. Allow customization of environment variable JVM_OPTS in the cve-monitor pod

    To invoke the proxy server by a java application, some system properties have to be configured via environment variable JVM_OPTS. They could be stored in a ConfigMap or Secret

    - name: JVM_OPTS

    value: >-

    -Djava.util.logging.config.file=/opt/ibm/wasintops/logging.properties

    -Djdk.http.auth.tunneling.disabledSchemes=""

    -Djdk.http.auth.proxying.disabledSchemes=""

    -Dhttps.proxyHost=

    -Dhttps.proxyPort=

    -Dhttp.proxyHost=

    -Dhttp.proxyPort=

    -Dhttp.nonProxyHosts="*.cluster.local|*.svc|localhost|127.*|[::1]

    -Dhttp.proxyUser=" "

    -Dhttps.proxyUser=" "

    -Dhttp.proxyPassword=" "

    -Dhttps.proxyPassword=" "

    -Djavax.net.debug=all

    Notice that some proxy server uses NTLMv2 authentication protocol (which is supported by Apache HttpClient 5), additional properties such as the domain name and the hashed password would be required


    2. Include customer's CAs in the trust.p12 currently in Secret wsa-secure-truststore

    Some customer uses the proxy server as 'man-in-the-middle' to intercept outbound traffic and replace the certificate of www.ibm.com with a version signed by their own CA. Given it is unlikely to be a well-known CA, it has to be added to the trust.p12 to allow SSL connections with IBM.


    3. Modify the Apache HttpClient in the cve-monitor to use the customized trust.p12 in additional to the default cacerts

    The current implementation of cve-monitor only uses the cacerts from the JVM as the ssl trusted store. For Apache HttpClient 5, the following snippet will get control of SSL management to WAS

    //Obtain the WAS_SSocketFactory which is just the JVM default Socket Factory

    javax.net.ssl.SSLSocketFactory WAS_SSLFactory;

    WAS_SSLFactory=(javax.net.ssl.SSLSocketFactory)javax.net.ssl.SSLSocketFactory.getDefault();


    //Create Apache's SSLConnectionSocketFactory with the WAS_SSocketFactory

    //Note hostname verification was disabled

    SSLConnectionSocketFactory ApacheSSLSocketFactory;

    ApacheSSLSocketFactory = new SSLConnectionSocketFactory(WAS_SSLFactory,new NoopHostnameVerifier());



  • Guest
    Oct 29, 2021

    Customer (IBM Tech Sales) is requesting any ETA. Any idea ?

  • Guest
    Oct 28, 2021

    It is one of the key requirements of my client, please raise the priority to high. In order to implement this function, the following conditions are needed:

    1. Allow customization of environment variable JVM_OPTS in the cve-monitor pod

    2. Include customer's CAs in the trust.p12 currently in Secret wsa-secure-truststore

    3. Modify the apache http client in the cve-monitor to use the customized trust.p12 in additional to the default cacerts