Request Packet Structure

A request XML packet installing an SSL certificate to Plesk certificate repository includes the install operation node:

<packet version="1.4.2.0">

<certificate>

   <install>

   ¡­

   </install>

</certificate>

</packet>

The install node does not have a separate data type, it is nested within type CertificateActionRequest (certificate_input.xsd). The install has the following graphical representation:

• The name node is required.It specifies the name under which the certificate will be known in repository and in Plesk. Data type: string.
• The domain node is required. It specifies the domain repository to which the certificate is installed. Data type: string.
• The admin node is required. If the node is present in a request packet, the certificate is installed to the Administrator's repository. Data type: none.
• The content node is required. It contains all data constituting the certificate. Data type: none.
• The csr node is required. It specifies the certificate CSR (certificate signing request). Data type: string.
• The pvt node is required. It specifies the certificate private key. Data type: string.
• The cert node is optional. It contains the certificate body. Data type: string.

Remarks

1. Certificate name must be unique in Plesk, meaning that two certificates with the same name cannot be installed, even if you want to install them to different repositories.

2. You can install only one certificate to only one repository within one install operation. Therefore, you must include either one domain node or admin node.

3. With one packet, you can install as many different certificates to any of the repositories as you want. To install multiple certificates, use the required number of install nodes in the packet:

<packet version="1.4.2.0">

<certificate>

   <install>

   ¡­

   </install>

   <install>

   ¡­

   </install>

   ¡­

</certificate>

</packet>