Re: Installing SSL cert from network solutions via DCM issue

[Tim Bronski <tim.bronski@xxxxxxxxx>]

When you generate a CSR you create a private key and store that. You 
also produce a corresponding certificate to send and get signed by a CA. 
The private key never leaves the store. When you import the signed 
certificate DCM will try match that cert to the corresponding key that 
it has stored. If it finds it job done. On the other hand if you already 
have a certificate and private key in another product you can export it 
to import it elsewhere. This will usually require you adding a password 
(to protect the private key) and it will usually be output in a .pfx or 
.p12 file. Those extensions are synonymous. A pfx is just an encrypted 
wrapper for a certificate and key (usually). You can import this into DCM.


On 7/21/2017 3:17 PM, Bradley Stone wrote:
> Thanks for posting, Kevin.
>
> I read through and the only thing it seems is different is it's a PFX
> file with a password.  Do you know how that bypasses the need for a
> CSR?  I am curious.  :)
>
> I also don't think the OP had a pfx file, just the crt files from the issuer.
>
> On Fri, Jul 21, 2017 at 7:59 AM, Kevin Turner
> <kevin.turner@xxxxxxxxxxxxxx> wrote:
> > My notes from 2012 on how I import certificates that are not created via a CSR:  http://www.coraltreesystems.com/phpbb/viewtopic.php?f=4&t=1009&hilit=ssl
> Bradley V. Stone
> www.bvstools.com
> MAILTOOL Benefit #15: The ability to add a Footer to each email sent
> using an IFS stream file.