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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
We would like to use SSL mutual authentication on our broker environment. We are using a central (company) CA that both client and server has connection to. The client has a client certificate; the server a server certificate. Now we would like to specify DN matching rules (which is possible in WebSphere MQ) to specify that only the client with a certificate that maches our rules are allowed access to our https connection.
According to Rao Nanduri rnanduri@us.ibm.com:
The default trust manager used by JSSE does not provide any option to distinguish/verify the clients based on specific DN. The authentication will only validate if the certificate is present in the truststore.
Message Broker has an option like host name checking in HTTP nodes which does a check on the distinguished name and the URL, but that doesn't serve the purpose for you.
JSSE Development team indicated that you would need to write your own trustmanager to do the verification you need on the certificate.
Please refer to the below API documentation about trust manager:
http://publib.boulder.ibm.com/infocenter/java7sdk/v7r0/index.jsp?topic=%2Fcom.ibm.java.security.component.doc%2Fsecurity-component%2Fjsse2Docs%2Fx509trustmanager.html
I would prefer not to write our own custom trust maanger but to just specify a DN matching rule.
Idea priority | Medium |
RFE ID | 35426 |
RFE URL | |
RFE Product | IBM App Connect Enterprise (formerly IBM Integration Bus) |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
RFE Review. Apologies for the length of time this RFE has been in the status of Under Consideration. We agree with the enhancement request idea that the ability to apply DN matching rules would bring improvement to the product. Status of the RFE is updated to Uncommitted Candidate.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - Integration
Product - IBM Integration Bus (WebSphere Message Broker) - IIB
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Connectivity and Integration
Product - IBM Integration Bus (WebSphere Message Broker) - IIB