Sun ONE Portal Server, Secure Remote Access 6.1 Installation Guide |
Chapter 4
Installing SSL CertificatesThis chapter provides details on installing SSL certificates after installing Sun ONE Portal Server, Secure Remote Access.
This chapter includes the following sections:
Overview of SSL CertificatesAn SSL certificate provides encryption and decryption capabilities using a public and private key pair. If you choose to install the certificate during installation, a self-signed certificate is generated and installed when you install the gateway. You can replace the installed certificate with another one that you generate or obtain anytime after installation. If you chose not to install the certificate during installation, you can generate and install a self-signed certificate, or a certificate that has been purchased from some certificate authority (CA), at a later point in time.
Secure Remote Access provides a tool named certadmin that you can use to manage the SSL certificates.
See the chapter, “Working With Certificates” in the Sun ONE Portal Server, Secure Remote Access 6.1 Administrator’s Guide for more information.
Generating Self-Signed CertificatesYou need to generate certificates for SSL communication between each server and gateway component.
To Generate a Self-Signed Certificate After Installation
The Certificate Administration menu is displayed.
- If you answer as y, the script prompts you to enter organization-specific information, token name and the certificate name.
What is the fully-qualified DNS name of this host? [host_name.domain_name]
What is the name of your organization (ex: Company)? []
What is the name of your organizational unit (ex: division)? []
What is the name of your City or Locality? []
What is the name (no abbreviation please) of your State or Province? []
What is the two-letter country code for this unit? []
Token name is needed only if you are not using the default internal (software) cryptographic module, for example, if you want to use a crypto card (Token names could be listed using: modutil -dbdir /etc/opt/SUNWps/cert -list); Otherwise, just hit Return below.
Please enter the token name []
Enter the name you like for this certificate:
- If you answer as n to the question "Do you want to keep the existing certificate database files?", the original certificate directory is backed up, and the script asks you for organization-specific information, token name, and certificate name as explained earlier.
You are also asked for a passphrase. A passphrase is required because a new set of certificate, key and encryption module database files will be created. The passphrase is stored in the .jsspass file under /etc/opt/SUNWps/cert.
A self-signed certificate is generated and the prompt returns.
- Restart the gateway for the certificate to take effect.
To restart the gateway, type the following command:
InstallDir/SUNWps/bin/gateway -n new profile name start
Installing Certificates From a Certificate AuthorityInstalling certificates from a Certificate Authority (CA) involves the following procedures:
Generating a Certificate Signing Request (CSR)
Before you can order a certificate from a CA, you need to generate a certificate signing request which will contain the information that is required by the CA.
To Generate a CSR
- As root, run the certadmin script:
InstallDir/SUNWps/bin/certadmin -n profilename
The Certificate Administration menu is displayed.
1) Generate Self-Signed Certificate
2) Generate Certificate Signing Request (CSR)
3) Add Root CA Certificate
4) Install Certificate From Certificate Authority (CA)
5) Modify Trust Attributes of Certificate (e.g., for PDC)
6) List Root CA Certificates
7) List All Certificates
8) Quit
choice: [8] 2
- Type 2 on the menu to generate a certificate signing request (CSR).
The script prompts you for organization-specific information, web master’s email and phone number, and token name.
Ensure that you specify the fully-qualified DNS name of the host.
What is the fully-qualified DNS name of this host? [snape.sesta.com]
What is the name of your organization (ex: Company)? []
What is the name of your organizational unit (ex: division)? []
What is the name of your City or Locality? []
What is the name (no abbreviation please) of your State or Province? []
What is the two-letter country code for this unit? []
What is the email address of the admin/webmaster for this server [] ?
What is the phone number of the admin/webmaster for this server [] ?
Token name is needed only if you are not using the default internal (software) cryptographic module, for example, if you want to use a crypto card (Token names could be listed using: modutil -dbdir /etc/opt/SUNWps/cert -list); Otherwise, just hit Return below.
Please enter the token name []
- Type all the required information.
A CSR is generated and stored in the file /tmp/csr.hostname. The CSR is also printed on the screen. You can directly copy and paste the CSR when you order a certificate from a CA.
Ordering a Certificate from a CA
After generating a certificate signing request (CSR), you need to order the certificate from the CA using the CSR.
To Order a Certificate
- Go to the Certificate Authority’s web site and order your certificate.
- Provide the CSR obtained from Generating a Certificate Signing Request (CSR), as requested by the CA. Provide other information if requested by the CA.
You will receive your certificate from the CA. Save it in a file. Include the "BEGIN CERTIFICATE" and "END CERTIFICATE" lines with the certificate in the file.
Installing a Certificate from the CA
Using the certadmin script, install the certificate obtained from the CA in your local database files in /etc/opt/SUNWps/cert.
To Install a Certificate
- As root, run the certadmin script.
InstallDir/SUNWps/bin/certadmin -n profilename
The Certificate Administration menu is displayed.
1) Generate Self-Signed Certificate
2) Generate Certificate Signing Request (CSR)
3) Add Root CA Certificate
4) Install Certificate From Certificate Authority (CA)
5) Modify Trust Attributes of Certificate (e.g., for PDC)
6) List Root CA Certificates
7) List All Certificates
8) Quit
choice: [8] 4
- Type 4 on the menu to install your certificate from the CA.
The script asks you to enter the certificate file name, certificate name, and the token name.
What is the name (including path) of file that contains the certificate?
Please enter the token name you used when creating CSR for this certificate []
- Supply all the required information.
The certificate is installed in /etc/opt/SUNWps/cert, and the screen prompt returns.
- Restart the gateway for the certificate to take effect:
InstallDir/SUNWps/bin/gateway -n profile name start
Installing a Root CA CertificateIf a client site presents a certificate signed by a CA that is unknown to the gateway certificate database, the SSL handshake will fail.
To prevent this, you need to import a root CA certificate into the certificate database. This ensures that the CA becomes known to the gateway.
Browse to the CA’s website and obtain the root certificate for that CA. You need to specify the filename and path of the root CA certificate when you run the certadmin utility.
To Import a Root CA Certificate
- As root, run the certadmin script.
InstallDir/SUNWps/bin/certadmin -n profilename
The Certificate Administration menu is displayed.
1) Generate Self-Signed Certificate
2) Generate Certificate Signing Request (CSR)
3) Add Root CA Certificate
4) Install Certificate From Certificate Authority (CA)
5) Modify Trust Attributes of Certificate (e.g., for PDC)
6) List Root CA Certificates
7) List All Certificates
8) Quit
choice: [8] 3
- Choose option 3 on the certificate administration menu.
- Enter the name of the file that contains the root certificate and enter the name for the certificate.
The root CA certificate is added to the certificate database.
Note
Certificate details can be viewed using the gwcertutil tool. This is a wrapper for the certutil tool provided by NSS/JSS.
- Refer to the section “Modifying the Trust Attributes of a Certificate” in Chapter 6 in the Sun ONE Portal Server, Secure Remote Access 6.1 Administrator’s Guide, for details.