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
If you would like to distribute a 3rd party X509 email certificate to your users, there are two methods:
a) the end user creating a Certificate Signing Request - this can only be done with a private key, so it must be done by the user
b) admins can create a new keypair, which will then be used to create a CSR. However, the keypair needs to be merged back into the user's ID file - and again this is an action that only the user can do.
Without the password you can not change the contents of the user ID file, so distributing a new x509 cert can not be done by just uploading it to the DominoDirectory.
However, the Domino CA process can very well be used to issue X509 certs to existing users. Distributing 3rd party key material without involving the user requires more than just an @function.