Integration
This is an IBM Automation portal for Integration 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.
Concerning the previous CRL related comment, the RFE expectation would be to allow configuration update of objects within the API Connect domain only (not make any configuration amendments within the DataPower Gateway "default" domain, i.e. an additional manual configuration would be required to enable the "default" domain CRL object outside of what the RFE will deliver).
In a similar vein, in relation to the previous comment regarding the limited capability within the Management component Cloud Manager Console to set the granular settings of a 'Crypto Validation Credential' object (through Truststore or other configuration settings), the company also has a requirement to set the 'Require CRL' parameter to 'on' as opposed to its default deployed setting of 'off'.
As per the indication above, when creating TLS profiles within the Management CMC, there's presently no capability to define granular configuration settings for many associated parameters, such as the 'signature algorithms' setting in this particular instance.
Another example of granular configuration that is missing from TLS profile configuration on the CMC is the ability to set a 'Crypto Validation Credential' object's 'Certificate Validation Mode' setting, which by default is set and deployed as option "Match exact certificate or immediate issuer", whereas our company has a security compliance requirement to set this as option "Full certificate chain checking (PKIX)".