HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
I am facing the same problem at the moment. Wanting to use REST Services to access a server with a self signed certificate. It is not accessible from the internet, so my only option is to use a self signed certificate. Please either let the java and NotesHTTPRequest use the internet certificates from the Domino Directory.
We have been using the /local/notesdata/cacert.pem (joshua.mindwatering.com/SupportRef.nsf/all/620e3ea6a9b7fd398525862700234051!OpenDocument). It's manual; it works, but it's not good. Every Domino patch overwrites it, and every Domino app server has to be updated. My preferred options are to add to the new Certificate Store app, and alternately (not or) have the option for request.IgnoreSSLIssue = true. Just like we can do for the timeoutsec and the maximum redirects.
BTW: Why don't NotesHTTPRequest and Java just use the internet certificates from Domino directory? That would be the Domino way of doing things!
Turning off security features seams a very bad idea to me. I'd suggest a feature to store (additional) trusted certificates for NotesHTTPRequest right inside the NSF. That would solve the certificate deployment problem while keeping security features on.
Is there any news about this idea? It would be very helpful!