An ACME centralized management system, wherein the system is connected with an ACME client and a plurality of certificate authorities (CAs) respectively and comprises an ACME unloading module, and a statistics module, a strategy module, a verification module, and a notification module which are connected with the ACME unloading module respectively, the ACME unloading module being in communication with the ACME client and the plurality of certificate authorities (CAs);
- wherein a working process of the system comprises the following steps:
- 1) launching a certification application to the ACME unloading module by the ACME client, and then performing data analysis unloading by the ACME unloading module;
- 2) selecting by the ACME unloading module the certificate authority (CA) through a strategy set by the strategy module and submitting an order to the corresponding certificate authority (CA) to start an application of a certificate;
- 3) setting by the ACME unloading module a verification value through the verification module and performing a verification on the order through the certificate authority (CA);
- and
- 4) after the verification is passed, issuing by the ACME unloading module an application status notification through the notification module and making statistics of data through the statistics module;
- wherein a load balancing method of the ACME centralized management system comprises that following steps:
- 1) creating an ACME catalogue URL through the ACME centralized management system by a user to acquire a URL address which carries a token bound to the order;
- 2) acquiring by the ACME client an API list through the ACME catalogue URL;
- 3) accomplishing account registration by calling a newNonce function and a newAccount API by the ACME client;
- 4) bringing a domain name message into the ACME centralized management system by calling the newNonce function and a newOrder API by the ACME client;
- 5) acquiring by the ACME centralized management system a corresponding strategy through the token in the ACME catalogue URL requested by the ACME client;
- 6) acquiring by the ACME centralized management system a corresponding order message through the token in the ACME catalogue URL requested by the ACME client;
- 7) creating a CA order with a domain name to be submitted to the certificate authority (CA) and without a CSR by the ACME centralized management system;
- 8) returning ACME Authorization data carrying an order ID and used for a domain name ownership verification by the ACME centralized management system, cheating the ACME client during this step to indicate that a domain name of the ACME client has passed the verification, and sending a message that the domain name has passed the verification, so as to skip a verification process that traditional ACME clients are automatically configured to accomplish an ACME domain name verification;
- 9) generating by the ACME client a private key and a CSR and submitting the order ID and the CSR to the ACME centralized management system by calling the newNonce function and a finalizeOrder function;
- 10) submitting by the ACME centralized management system the CA order to be submitted with the CSR to the certificate authority (CA) to acquire a domain name verification message, and calling the verification module for a domain name verification;
- 11) receiving by the verification module the domain name to be verified and the verification value and setting a verification value through a file proxy and a DNS CNAME authorization;
- 12) calling by the ACME centralized management system a CA certificate to acquire an API and issuing and returning certificate contents after completion of the domain name verification by the certificate authority (CA);
- and
- 13) returning by the ACME centralized management system the certificate contents to the ACME client according to an ACME protocol manner to accomplish a certificate issuing process.