- URL:
- https://<root>/machines/<machine>/sslCertificates/importExistingServerCertificate
- Methods:
POST- Version Introduced:
- 10.8
Access requirements
Required privileges
The Portal Administrator API requires privilege-based access. An administrator must be assigned a specific user privilege, or role, to access any given endpoint. Listed below are the user privileges or roles an administrator can be assigned that provides access to this endpoint. If multiple privileges are listed, only one needs to be assigned to gain access.
Tokens
This API requires token-based authentication. A token is automatically generated for administrators who sign in to the Portal Administrator API directory's HTML interface. Tokens generated in this way are stored for the entirety of the session.
Those accessing the API directory outside of the HTML interface will need to acquire a session token from the generate operation in the Portal Directory API. For security reasons, all POST requests made to the Portal Administrator API must include a token in the request body.
Description
The import operation imports an existing server certificate, stored in the PKCS #12 format, into the key store. If the certificate is a CA-signed certificate, you must first import the CA Root or Intermediate certificate using the Import Root or Intermediate Certificate operation.
Request parameters
| Parameter | Details |
|---|---|
| The name of the certificate. Example |
| The password to unlock the file containing the certificate. Example |
| The multipart POST parameter containing the certificate file. Example |
| Introduced in 11.3. Specifies if the root or intermediate certificates included inside the existing certificate file should also be imported. By default, the parameter is set to Values: |
| The response format. The default response format is Values: |
JSON Response example
{"status": "success"}