SSL Certificate

• URL:https://<sslCertificates-url>/<cert_name>
  
• Required Capability:Administrator
• Version Introduced:10.8

Description

A certificate represents a key pair that has been digitally signed and acknowledged by a Certifying Authority (CA). It is the most fundamental component in enabling SSL on your server. This resource returns information on an individual certificate. New self-signed certificates created by the Generate Certificate operation are added to the keystore. In order for browsers and other HTTP client applications to trust the SSL connection on the server, these certificates must be digitally signed by a CA and then imported into the keystore.

Note:

Typically, certificates are bound to a machine name. Therefore, if the name of the machine changes, you need re-generate the certificate.

This resource provides information on an individual certificate, as well as provide access to a Export , Delete , Generate CSR, and Import Signed Certificate operations.

Note:

Even though a self-signed certificate can be used to enable SSL, it is recommended that you use a self-signed certificate only on staging or development servers.

Request parameters

Parameter	Details
f	The response format. The default response format is html. Values: html | json

Example usage

Below is a sample request URL for an individual certificate resource:

https://machine.domain.com/webadaptor/admin/machines/MACHINE.DOMAIN.COM/sslcertificates/selfSignedCertificate?f=json

JSON Response syntax

{
  "Alias name": "<alias>",
  "Creation date": "<creation date>",
  "Entry type": "PrivateKeyEntry",
  "Certificate chain length": "1",
  "Certificate[1]": "",
  "Owner": "<certificate owner information>",
  "Issuer": "<certificate issuer information>",
  "Serial number": "<serial number>",
  "Valid from": "<date range for certificate validity>",
  "Certificate fingerprints": "",
  "MD5": "<MD5 fingerprint>",
  "SHA1": "<SHA1 fingerprint>",
  "SHA256": "<SHA256 fingerprint>",
  "Signature algorithm name": "<signature algorithm>",
  "Version": "3"
}

JSON Response example

{
  "Alias name": "myselfsignedcertificate",
  "Creation date": "Feb 10, 2015",
  "Entry type": "PrivateKeyEntry",
  "Certificate chain length": "1",
  "Certificate[1]": "",
  "Owner": "CN=SERVER.COMPANY.COM, O=SelfSignedCertificate",
  "Issuer": "CN=SERVER.COMPANY.COM, O=SelfSignedCertificate",
  "Serial number": "80d1993",
  "Valid from": "Tue Feb 10 10:40:41 PST 2015 until: Thu Dec 19 10:40:41 PST 2047",
  "Certificate fingerprints": "",
  "MD5": "79:CC:28:90:1C:1E:EC:CE:6A:A6:8F:DA:53:96:A9:41",
  "SHA1": "BD:E9:D1:A9:20:92:C7:00:CF:CA:1D:A2:C4:29:C9:65:2D:DF:26:21",
  "SHA256": "0B:B4:7C:6D:79:33:DD:7F:90:A5:50:F0:95:7E:6F:98:6E:45:6A:7B:7E:E0:5B:F7:A3:DB:2B:62:C7:5C:F4:1D",
  "Signature algorithm name": "SHA256withRSA",
  "Version": "3"
}