Thanks for the explanation. So it looks like i am missing something.
When try to "import" the files they provided under "server/client", it
"No request key is found for the certificate. If you are trying to
receive the signed certificate, you must be using the same certificate
store that was used when the certificate was requested. If this is a CA
certificate, you should use the function for importing a CA."
On 8/12/2014 8:45 PM, Scott Klement wrote:
Certificate Authority certificates are imported to control which
certificates your application will "trust". The hackers, identity
thieves, etc know how to use SSL, too... so how do you know who you
can trust? A certificate authority (CA) is a company who checks
people to make sure they are legit before signing their certificates.
Anyone whos certificate is proven signed by that certificate authority
is therefore trustable. This is why you install CA certificates.
You cannot assign a CA certificate to one of your applications. That
would be telling the world that you *are* the CA (instead of simply
trusting certificates from the CA.)
You will need to first install the CA certificates that you got from
NetSol so that the system will trust them, then install the client or
server certificates that they signed for you to use.
On 8/12/2014 6:48 PM, tim.dclinc@xxxxxxxxx wrote:
still working on trying to get ssl working on my ibm http server.
i received files from network solutions (*.cer extensions).
I opened DCM and imported them as a "Certificate Authority CA".
When i try to "Assign certificate", its looking for a "server or client"
certificate type not "certificate Authority".
How do i import what network solutions provided into a "server or
client" certification type?