Create a self-signed certificate.
When you create the self-signed certificate, specify the name of the key pair you generated in the previous step.
A server certificate attests to the identity of your organization and contains the public key of the key pair you specify when creating the certificate. When a web browser initiates a transmission using SSL, your web server transmits the server certificate to the web browser. As a result, your public key is transmitted to the web browser.
To run SSL in production, use a certificate you obtain from a certificate authority. Use the self-signed certificate to test SSL and to ensure VM:Webgateway is set up correctly to use SSL Feature while you wait for the certificate from the certificate authority.
Note: On web browsers that support SSL, the public keys of well-known certificate authorities are preloaded. This allows web browsers to validate certificates that are signed by well-known certificate authorities. Because you are using a self-signed certificate, the web browser does not have the public key for your certificate and cannot validate the certificate. When web browser users testing SSL request data, the response varies based on the web browser being used. Some web browsers will automatically prompt a web browser user to load a certificate when they enter a URL for a file for which the web browser requires a certificate. Other web browsers require web browser users to load the self-signed certificate to the web browser themselves before attempting to view a file that requires validation using the certificate.
