From HEXONET Wiki
Line 93: | Line 93: | ||
'''Order certificate providing the domain name only''' | '''Order certificate providing the domain name only''' | ||
<br> | <br> | ||
− | The contact data is retrieved from the WHOIS. The private key and CSR are created automatically. | + | The contact data is retrieved from the WHOIS. The private key and CSR are [[New_SSL_API_CSR_Creation|created automatically]]. |
<pre> | <pre> | ||
[COMMAND] | [COMMAND] | ||
Line 104: | Line 104: | ||
'''Order certificate with contact handles''' | '''Order certificate with contact handles''' | ||
<br> | <br> | ||
− | The private key and CSR are created automatically. | + | The private key and CSR are [[New_SSL_API_CSR_Creation|created automatically]]. |
<pre> | <pre> | ||
[COMMAND] | [COMMAND] | ||
Line 137: | Line 137: | ||
'''Order certificate with your own private key''' | '''Order certificate with your own private key''' | ||
<br> | <br> | ||
− | The CSR is created automatically using the provided private key. | + | The CSR is [[New_SSL_API_CSR_Creation|created automatically]] using the provided private key. |
<pre> | <pre> | ||
[COMMAND] | [COMMAND] | ||
Line 156: | Line 156: | ||
'''Order certificate where you tell us exactly what contact data to put into the CSR''' | '''Order certificate where you tell us exactly what contact data to put into the CSR''' | ||
<br> | <br> | ||
− | The CSR is created automatically using the contact data provided in csrcontact0. | + | The CSR is [[New_SSL_API_CSR_Creation|created automatically]] using the contact data provided in csrcontact0. |
<pre> | <pre> | ||
[COMMAND] | [COMMAND] |
Revision as of 11:56, 8 April 2016
Why use the new SSL API?
With the new SSL API you can:
- Order SSL certificates without having to provide contact data - given the domain name, we will retrieve the required contact information from the WHOIS
- Order SSL certificates without having to create a CSR first - we take care of this for you
- Order SSL certificates using contact handles - just like in domain commands
- Use advanced validation methods - instead of confirming emails, you can prove that you have control over a domain by a simple DNS or web content modification
How to use the new SSL API?
You can do that right away. Just make use of the new command parameters described below.
SSL certificate |
---|
COMODO_ESSENTIALSSL |
COMODO_INSTANTSSL |
COMODO_INSTANTSSL_PRO |
COMODO_PREMIUMSSL |
COMODO_PREMIUMSSL_WILDCARD |
COMODO_EVSSL |
COMODO_UCC |
GEOTRUST_QUICKSSLPREMIUM |
GEOTRUST_RAPIDSSL |
GEOTRUST_RAPIDSSL_WILDCARD |
SYMANTEC_SECURESITE |
SYMANTEC_SECURESITEPRO |
SYMANTEC_SECURESITEEV |
SYMANTEC_SECURESITEPROEV |
THAWTE_SSL123 |
THAWTE_SSLWEBSERVER |
THAWTE_SSLWEBSERVEREV |
THAWTE_SSLWEBSERVER_WILDCARD |
All new parameters
[COMMAND] command = CreateSSLCert sslcertclass = <CLASS> period = <INT> ownercontact0 = <CONTACT> admincontact0 = <CONTACT> techcontact0 = <CONTACT> billingcontact0 = <CONTACT> csrcontact0 = <CONTACT> domain# = <DOMAIN> validation# = EMAIL | DNSZONE | URL validationemail# = <EMAIL> csr# = <TEXT> pem# = <TEXT> EOF
[RESPONSE] CODE=200 DESCRIPTION=Command completed successfully PROPERTY[SSLCERTID][0]=<SSLCERTID>
Order certificate providing the domain name only
The contact data is retrieved from the WHOIS. The private key and CSR are created automatically.
[COMMAND] command = CreateSSLCert sslcertclass = <CLASS> domain0 = <DOMAIN> EOF
Order certificate with contact handles
The private key and CSR are created automatically.
[COMMAND] command = CreateSSLCert sslcertclass = <CLASS> domain0 = <DOMAIN> ownercontact0=<CONTACT> admincontact0=<CONTACT> techcontact0=<CONTACT> billingcontact0=<CONTACT> EOF
Order certificate with your own CSR
The domain is retrieved from the provided CSR.
[COMMAND] command = CreateSSLCert sslcertclass = <CLASS> ownercontact0=<CONTACT> admincontact0=<CONTACT> techcontact0=<CONTACT> billingcontact0=<CONTACT> csr0 = -----BEGIN CERTIFICATE REQUEST----- csr1 = ... ... EOF
Order certificate with your own private key
The CSR is created automatically using the provided private key.
[COMMAND] command = CreateSSLCert sslcertclass = <CLASS> domain0 = <DOMAIN> ownercontact0=<CONTACT> admincontact0=<CONTACT> techcontact0=<CONTACT> billingcontact0=<CONTACT> pem0 = -----BEGIN RSA PRIVATE KEY----- pem1 = ... ... EOF
Order certificate where you tell us exactly what contact data to put into the CSR
The CSR is created automatically using the contact data provided in csrcontact0.
[COMMAND] command = CreateSSLCert sslcertclass = <CLASS> domain0 = <DOMAIN> ownercontact0=<CONTACT> admincontact0=<CONTACT> techcontact0=<CONTACT> billingcontact0=<CONTACT> csrcontact0=<CONTACT> EOF
Order certificate with plain contact data
This works just like for domains.
[COMMAND] command = CreateSSLCert sslcertclass = <CLASS> domain0 = <DOMAIN> ownercontact0organization = <TEXT> | <NULL> ownercontact0firstname = <TEXT> | <NULL> ownercontact0lastname = <TEXT> | <NULL> ownercontact0street = <TEXT> | <NULL> ownercontact0city = <TEXT> | <NULL> ownercontact0state = <TEXT> | <NULL> ownercontact0zip = <TEXT> | <NULL> ownercontact0country = <TEXT> | <NULL> ownercontact0phone = <TEXT> | <NULL> ownercontact0fax = <TEXT> | <NULL> ownercontact0email = <TEXT> | <NULL> ownercontact0title = <TEXT> | <NULL> EOF