Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

The keystore you just created does not yet contain any certificates nor key as depicted in the following figure. Also note the keystore is by default locked, that is the closed lock in the Available column. Once you create the certificate you will need to click on the lock to make that certificate available, you will be prompted with the passwords for the keystore and certificate.

To create a private key click on the keys on the keystore you just created and then click on Create Private Key. Enter valid data in the appropriate field data.

...

You now can use that certificate by configuring an HTTPS connector as described in Add new HTTPS listener. Remember to make the certificate and keystore available by clicking on the "lock".
For this example we have modified the existing TomcatWebSSLConnector JettySSLConnector, we specified the new keystore and password and saved the configuration.

For this configuration to take effect you need to restart the connector. Click on the stop link corresponding to the network listener you just updated, in this case JettySSLConnector, and then click on start. Now this connector is using the new keystore and certificate.

Image Added

If you now point your browser to that particular port you should see the server is using the certificate you created previously. For this example, as we are using the existing SSL connector, we point the browser to:

httphttps://localhost:8443Image Removed