The POST /CertificateAuthority/Import method is used to import into Keyfactor Command any certificate authorities from the provided configuration tenant
A grouping of CAs. The Microsoft concept of forests is not used in EJBCA so to accommodate the new EJBCA functionality, and to avoid confusion, the term forest needed to be renamed. The new name is configuration tenant. For EJBCA, there would be one configuration tenant per EJBCA server install. For Microsoft, there would be one per forest. Note that configuration tenants cannot be mixed, so Microsoft and EJBCA cannot exist on the same configuration tenant. DNS The Domain Name System is a service that translates names into IP addresses. suffix (e.g. keyexample.com). This endpoint An endpoint is a URL that enables the API to gain access to resources on a server. returns 204 with no content upon success.
Table 298: POST Certificate Authority Import Input Parameters
| Name | In | Description |
|---|---|---|
| dns | Query |
Required. The DNS suffix of the configuration tenant to query for CAs to import. For example: Copy
|
A set of functions to allow creation of applications. Keyfactor offers the Keyfactor API, which allows third-party software to integrate with the advanced certificate enrollment and management features of Keyfactor Command. endpoints can be called and results returned. It is intended to be used primarily for validation, testing and workflow A workflow is a series of steps necessary to complete a process. In the context of Keyfactor Command, it refers to the workflow builder, which allows you automate event-driven tasks when a certificate is requested or revoked. development. It also serves secondarily as documentation for the API. The link to the Keyfactor API Reference and Utility is in the dropdown from the help icon (
) at the top of the Management Portal page next to the Log Out button.