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,
Post an idea
Upvote ideas that matter most to you
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 portal, please send email describing the issue to email@example.com for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.
Create a means for WMB to check certificate revocation
We are using Broker with a SOAP Input node which is configured to use HTTPS, with clientAuth set to true. As well as checking the client certificate we also need to check whether the client's certificate has been revoked i.e. whether it appears in a CRL (certificate Revocation List). We came across some documentation about setting the Java properties com.ibm.jsse2.checkRevocation and com.ibm.security.enableCRLDP to enable CRL checking (See http://www.ibm.com/developerworks/java/jdk/security/50/secguides/jsse2Docs/JSSE2RefGuide.html) and have tried this with Broker. This worked, and checked CRLs, but only when the Broker acts as a client, such as when using the TFIM STS interface. But it didn't work when the Broker acts as a server, as in receiving a request at a SOAP Input node.
Do not place IBM confidential, company confidential, or personal information into any field.