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
Having trusted roots in a file in data directory isn't desirable at all from security point and management point of view.
Domino 12.0.2 introduces a new back-end for root certificates which are stored either in the Domino directory or certstore.nsf.
Some new functionality is already move to this new trust store for LibCurl functionality (which is also used by the Lotus Script class).
Functionality already using the new trusted root store:
- CertMgr URL Health Check (12.0.2+)
- MailScan/ICAP (12.0.2+)
- ODIC configuration by default uses cacerts.pem unless you explicitly specify a trusted root coming from certstore (14.0+)
- Domino 14.0 AutoUpdate (14.0+)
cerstore.nsf also contains usage categories for roots since Domino 12.0.2.
IMHO remaining callers like Lotus Script HTTP class should be also moved over to this new model which would make cacerts.pem obsolete.
The remaining question for Notes clients would be how to manage the certificates.
Probably pushing trusted roots to names.nsf locally via security policies would be an existing mechanism.
[ Daniel Nashed / https://blog.nashcom.de ]
So this is for outbound calls ? Instead of working with files on the servers disk, we would like to handle TLS certificates in the certificate manager. Would this work for you?