Tool
tool
Reads:
9362
Score:
license:
GPLv2The Certificate Creation script recreates the certificates on OES1 and OES2 servers using a Personal Information Exchange File. With an additional parameter it will also restart all the necessary services. The following information is obtained in the script execution process.
Platforms Supported:
32 and 64 bit OES1 and OES2 are currently supported.
Script Process:
- The following files are backed up with the date and time appended.
/etc/ssl/servercerts/servercert.pem /etc/ssl/servercerts/serverkey.pem /var/lib/novell-lum/x.x.x.x.der /etc/opt/novell/SSCert.pem //OES1 /etc/opt/novell/certs/SSCert.pem //OES2
- Creation of new Certificates
/etc/ssl/servercerts/serverkey.pem /etc/ssl/servercerts/servercert.pem /etc/opt/novell/SSCert.pem //OES1 /etc/opt/novell/SSCert.der //OES1 /etc/opt/novell/certs/SSCert.pem //OES2 /etc/opt/novell/certs/SSCert.der //OES2 /var/lib/novell-lum/x.x.x.x.der
- Reloads services (optional)
owcimond nldap namcd apache2
Installation Instructions:
- Download certificate-creation.tgz
- Open a Terminal window and type “su”
- Enter root’s password
- Extract the script from the tarball
#tar –xzvf certificate-creation.tgz - Make the script executable.
#chmod 755 certificate-creation.sh - Export the Personal Information Exchange File using iManager.
- In iManager, go to Directory Administration -> Modify Object
- Select the SSL CertificateDNS - YourServerName certificate object, which by default is in the same eDirectory context as your server object and click OK
- Go to the Certificates tab of the certificate object and click Validate. It should come back as Valid. If not, there is something wrong with your Certificate Authority and you should rectify this problem and regenerate the certificates before continuing.
- Select Export.
- Select "Export private key" and "Include all certificates in the certification path if available."
- Assign the private key a password. This will be used to protect the private key while it is being transferred. This password will be removed in a future step.
- Save the resulting pkcs12 file (Personal Information Exchange format) to a secure location on your server. The default file name is cert.pfx
- Run the certificate-creation.sh script
#./certificate-creation.sh -f /directory/fileName.pfx -c -r
Fixes and Enhancements:
-
Version 1.1
- The script will now check if your are root
- OES2 x86_64 is now supported
- A relative path to the .pfx file can now be used.
Note: Using a –h will display other parameter options if desired. The most recent version (1.1) no longer requires the full path to the ".pfx file
| Attachment | Size |
|---|---|
| certificate-creation-1.1.tgz | 2.79 KB |
Related Articles
- Client Certificate Generation
- How to SSLize User Application on JBoss using eDirectory's Certificate Authority for Linux
- Solving the iManager 'Service Not Available' Message
- Configuring NetStorage on Novell Cluster Services using OES2 SP1 Linux, with Third-Party External Certificates
- Importing a Thawte Certificate into eDirectory






10