|
Home > Archive > Netware Webserver > May 2005 > Installing 3rd Party Certificate
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Installing 3rd Party Certificate
|
|
| jphillips@nospam.descominc.com 2005-04-25, 5:45 pm |
| I have done quite a bit of research trying to find the steps required to
install a 3rd party root certificate from Verisign onto a Netware 6.5
server, and then configure Apache to use this certificate instead of the
default "DNS Certificate" on port 443. However, there seems to be
conflicting information. One search produced the following link:
http://www.verisign.com.au/support/...ell/v00.shtml#1
The steps involoved here are basically using the existing private key to
generate a public key, the replacing the existing public key with a new one.
This link, however, talkes about creating new certificates, updating
autoexec.ncf, etc:
http://www.novell.com/coolsolutions/feature/9937.html
Anyway, I am running Groupwise 6.5.3 on a NetWare 6.5.2 server, and want
the Groupwise WebAccess page (running in Apache2) to be encrypted with a
certificate authenticated by Verisign.
Any help/links, etc. would be greatly appreciated.
Josh
| |
| Anders Gustafsson 2005-04-25, 5:45 pm |
| ,
> Anyway, I am running Groupwise 6.5.3 on a NetWare 6.5.2 server, and want
> the Groupwise WebAccess page (running in Apache2) to be encrypted with a
> certificate authenticated by Verisign.
The steps are:
1. Create a certificate (KMO)in C1, when asked specify an external CA
2. C1 creates a CSR (Cerrificate Signing Request) that you send to
Verisign
3. When you get it back, signed, you import it into the certificate, using
C1
4. Change the "SecureListen" line in httpd.conf to use the certificate
name you specified when creating.
- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop
Pedago, The Aaland Islands (N60 E20)
Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement
Using VA 5.51 build 315 on Windows 2000 build 2195
| |
| jphillips@nospam.descominc.com 2005-05-04, 5:45 pm |
| Well, it wasn't quite as easy as that. However, all steps are spelled out
in the following document:
http://www.novell.com/connectionmag...2/10/secure.pdf
Thanks.
Josh
> The steps are:
> 1. Create a certificate (KMO)in C1, when asked specify an external CA
> 2. C1 creates a CSR (Cerrificate Signing Request) that you send to
> Verisign
> 3. When you get it back, signed, you import it into the certificate,
using
> C1
> 4. Change the "SecureListen" line in httpd.conf to use the certificate
> name you specified when creating.
| |
| Anders Gustafsson 2005-05-05, 7:45 am |
| ,
> Well, it wasn't quite as easy as that. However, all steps are spelled out
> in the following document:
>
Excellent resource. I will keep that in mind. Note that this is specific to
VeriSign. Last time I used Digicert which has documentation on their website
for all platforms.
- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop
Pedago, The Aaland Islands (N60 E20)
Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement
Using VA 5.51 build 315 on Windows 2000 build 2195
|
|
|
|
|