There are a couple of use-cases where importing certificates into a person document are important. Beside this Lotus Script method the only other method would be the C-API (SECNABAddCertificate() which only supports DER format by the way).
Now that CertMgr and certstore.nsf full supports PEM format, it would be very helpful if this function would also take PEM as an input in addition to KYR.
I just had to help another partner trying to integrate a solution to import certs for client certificates for authentication into person documents.
This isn't the first integration I had to build for customers as well.
Adding PEM support to this function would help to build simple and stable integrations not using LS2CAPI.
Manually creating an Adminp request would not work, because the certificate format in Adminp isn't exposed.
There are two levels of enhancing the existing functionality I could imagine:
Only improve the AddInternetCertificateToUser() and generate the Adminp request in the back-end.
Also add PEM support for Proxy action 44 by allowing an alternate format in PEM (current field: ProxyUserCertificate, could be e.g. ProxyUserCertificatePEM).
[ Daniel Nashed / https://blog.nashcom.de ]