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
When using an SSL client profile configured with an unacceptable client certificate to connect to an HTTPS endpoint with url-open, the HTTPS endpoint rejects the client certificate as part of the SSL handshake, as expected. However, the “statuscode” value indicates “5” (Connection Error) vs. the expected “7” (Error with SSL connection.)
The documentation for url-open (https://www.ibm.com/support/knowledgecenter/en/SS9H2Y_7.6.0/com.ibm.dp.doc/url-open_generic_element.html) doesn't provide descriptions about the nature of SSL errors that would be reported as statuscode “7” or what might be classified as a connection error (“5”).
We would like to have a status code response from url-open that allowed us to distinguish between actual connection errors (e.g. no route to host) vs. credential errors (e.g. client certificate rejected during TLS handshake).
Idea priority | Medium |
RFE ID | 134720 |
RFE URL | |
RFE Product | IBM DataPower Gateways |
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.
I had this error with FireFox... The solution that worked for me is here: http://talk.manageiq.org/t/solved-firefox-performing-a-tls-handshake-is-slow/3046/6
For me it would sometimes connect, then never connect until I renamed the FireFox Cert DB file. then viola, the admin console came up immediatedly when accessed.