Cloud Platform
This is an IBM Automation portal for Cloud Platform 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 (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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
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());
Customer (IBM Tech Sales) is requesting any ETA. Any idea ?
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