|
Paul,
The IT Jungle article reference by Paul F. seems to address the issue of
"importing" a certificate from a trusted authority (GoDaddy in your case).
I have not used GoDaddy certificates, so your mileage may vary. Please let
us know if you are able to import it using Joe Hertvik's article.
After that, return to the HTTP Admin GUI. Use the "Security" link to
"Enable" SSL and associate it with a "Server certificate application name".
Apply your changes. Somehow that creates an application reference that
enables the Digital Certificate Manager to "assign" the certificate to.
However, you'll need to return to the DCM and "assign" it to that HTTP
application name, to complete the link. I like to view the resulting HTTP
Configuration file up in the GUI text editor to review it.
-Nathan
----- Original Message -----
From: Paul Therrien <ptherrien@xxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Cc:
Sent: Tuesday, April 23, 2013 12:28 PM
Subject: RE: SSL and public facing web site on the i
Nathan,
The desire for SLL is exactly as you state - to encrypt communications of
user ids and passwords and company data.
The issue that I feel I am having with SSL is my lack of understanding of
how to setup the web server with our public certificate.
When I attempt to install the CA certificate on the I, I get the following
error from the Digital Certificate Manager:
"An error occurred during certificate validation. The issuer of the
certificate may not be in the certificate store or the issuer may not be
enabled. "
There are 2 .crt files to install one appears to be the Certificate for
the CA and the other is the certificate for our domain.
The big issue is my lack of understanding - both of the SSL installation
and the Apache configuration.
Paul
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.