Cisco 11503 - CSS Content Services Switch Configuration Manual page 69

Chapter 3 Configuring SSL Certificates and Keys
Generating Certificates and Private Keys in the CSS
AkEAqHXjtQUVXvmo6tAWPiMpe6oYhZbJUDgTxbW4VMCygzGZn2wUJTgLrifDB6N3
v+1tKFndE686BhKqfyOidml3wQIDAQABoAAwDQYJKoZIhvcNAQEEBQADQQA94yC3
4SUJJ4UQEnO2OqRGLOZpAElc4+IV9aTWK6NmiZsM9Gt0vPhIkLx5jjhVRLlb27Ak
H6D5omXa0SPJan5x
-----END CERTIFICATE REQUEST-----
CSS11503(config)#
The ssl gencsr command generates the CSR in PKCS10 encoded in PEM format
and outputs it to the screen. Most major Certificate Authorities have web-based
applications that require you to cut and paste the certificate request to the screen.
If necessary, you can also cut and paste the certificate to a file. Note that the CSR
is not saved in the CSS.
If you require a global site certificate that allows 128-bit encryption for
Note
export-restricted browsers, apply for a StepUp/SGC or chained certificate from
the Certificate Authority. After you receive the certificate, you must prepare it for
use with the CSS. For more information, see the "Preparing a Global Site
Certificate" section.
After submitting your CSR to the Certificate Authority (CA), you will receive
your signed certificate between one to seven business days. When you receive
your CSR, import the CSR to the CSS and then associate it. For information on
importing the CSR, see the "Importing or Exporting Certificates and Private
Keys" section. For information on associating it, see the "Associating Certificate
and Private Key Files with Names" section.
While you are waiting to receive your signed certificate, you can test your CSR
file by creating a temporary certificate by generating a CSR and signing it with
your own private key. While this produces a valid certificate, most browsers flag
the certificate as signed by an unrecognized signing authority. To generate a
temporary certificate, see the "Generating a Self-Signed Certificate" section.
Cisco Content Services Switch SSL Configuration Guide
3-9
OL-5655-01