Digital certificate automatic distribution method and system
By reviewing the automated process of node groups and certificate issuance node groups, and generating and distributing digital certificates, the problem of inefficient distribution of digital certificates is solved, and efficient automated distribution and traceability are achieved.
Patent Information
- Application Number
- CN202510688511.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-27
- Publication Date
- 2025-07-18
AI Technical Summary
In the prior art, digital certificate distribution is inefficient and cumbersome, and there is a lack of convenient automation solutions.
Authentication is performed by auditing the node group, and after passing the verification, the certificate issuing node group will automatically generate a digital certificate and write it to the blockchain. The target client downloads the certificate from the blockchain to realize the automatic distribution of digital certificates.
Improves the distribution efficiency of digital certificates, reduces manual intervention, shortens processing cycles, and compresses from traditional daily processing to seconds, ensuring operation traceability.
Smart Images

Figure CN120342635A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer technology, and in particular, to a method and system for automatic distribution of digital certificates. Background Art
[0002] Currently, there are a large number of tenants, devices, and application programs in the Internet environment. Digital certificates can uniquely and reliably identify the identity of each entity, ensuring that only legally authorized entities can access the corresponding services, thereby realizing identity authentication and access control in the public cloud environment. However, related technologies usually distribute digital certificates through manual review and manual issuance of certificates, resulting in cumbersome operations and low efficiency. Based on this, there is currently no good solution for how to conveniently perform automatic distribution of digital certificates to improve the distribution efficiency of digital certificates. Summary of the Invention
[0003] In view of this, embodiments of the present invention provide a method and system for automatic distribution of digital certificates to solve problems such as cumbersome operations and low distribution efficiency of digital certificates in related technologies; that is to say, embodiments of the present invention can achieve automatic review of identities through an audit node group and automatic generation of digital certificates through a certificate issuance node group, thereby conveniently performing automatic distribution of digital certificates and effectively improving the distribution efficiency of digital certificates.
[0004] According to one aspect of the embodiments of the present invention, there is provided a method for automatic distribution of digital certificates. The method is applied to a digital certificate automatic distribution system, and the digital certificate automatic distribution system includes an audit node group, a certificate issuance node group, and at least one client. The method includes:
[0005] When the audit node group receives a certificate application request sent by a target client, it performs identity verification based on a certificate signature request file indicated by the certificate application request to obtain an identity verification result; wherein, the target client is any one of the at least one client;
[0006] When the identity verification result is used to indicate successful identity verification, the certificate issuance node group reads the certificate signature request file; generates a target digital certificate based on the certificate signature request file, and writes the target digital certificate into the certificate blockchain;
[0007] The target client downloads the target digital certificate from the certificate blockchain.
[0008] According to another aspect of the embodiments of the present invention, there is provided a digital certificate automatic distribution system, and the digital certificate automatic distribution system includes an audit node group, a certificate issuance node group, and at least one client;
[0009] The audit node group is used to: when receiving a certificate application request sent by a target client, perform authentication based on the certificate signature request file indicated by the certificate application request to obtain an authentication result; wherein, the target client is any one of the at least one client;
[0010] The certificate issuance node group is used to: when the authentication result is used to indicate successful authentication, read the certificate signature request file; generate a target digital certificate based on the certificate signature request file, and write the target digital certificate into the certificate blockchain;
[0011] The target client is used to: download the target digital certificate from the certificate blockchain.
[0012] In the embodiment of the present invention, when the audit node group receives a certificate application request sent by a target client, it can perform authentication based on the certificate signature request file indicated by the certificate application request to obtain an authentication result; wherein, the target client is any one of the at least one client. Based on this, when the authentication result is used to indicate successful authentication, the certificate issuance node group can read the certificate signature request file; thereby generate a target digital certificate based on the certificate signature request file, and write the target digital certificate into the certificate blockchain. Correspondingly, the target client can download the target digital certificate from the certificate blockchain. It can be seen that the embodiment of the present invention can realize automatic audit of identities through the audit node group, and realize automatic generation of digital certificates through the certificate issuance node group, so as to conveniently perform automatic distribution of digital certificates and effectively improve the distribution efficiency of digital certificates. Description of the Drawings
[0013] In the following description of exemplary embodiments with reference to the drawings, more details, features and advantages of the present invention are disclosed. In the drawings:
[0014] Figure 1 Shows a schematic flow diagram of a method for automatic distribution of digital certificates according to an exemplary embodiment of the present invention;
[0015] Figure 2 Shows a schematic diagram of a system for automatic distribution of digital certificates according to an exemplary embodiment of the present invention;
[0016] Figure 3 Shows a schematic structural diagram of a blockchain according to an exemplary embodiment of the present invention;
[0017] Figure 4 Shows a schematic flow diagram of another method for automatic distribution of digital certificates according to an exemplary embodiment of the present invention;
[0018] Figure 5Shows a schematic flowchart of yet another method for automatically distributing digital certificates according to an exemplary embodiment of the present invention;
[0019] Figure 6 Shows a block diagram of an exemplary electronic device capable of implementing the embodiments of the present invention. Detailed implementation manners
[0020] The embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present invention are shown in the drawings, it should be understood that the present invention can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. On the contrary, these embodiments are provided to more thoroughly and completely understand the present invention. It should be understood that the drawings and embodiments of the present invention are only for exemplary purposes and are not used to limit the protection scope of the present invention.
[0021] It should be understood that the various steps recited in the method embodiments of the present invention can be executed in a different order and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present invention is not limited in this regard.
[0022] As used herein, the term "including" and its variations are open-ended, that is, "including but not limited to". The term "based on" is "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description. It should be noted that the concepts such as "first" and "second" mentioned in the present invention are only used to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependent relationships.
[0023] It should be noted that the modifications of "one" and "plural" mentioned in the present invention are illustrative rather than restrictive. Those skilled in the art should understand that unless otherwise clearly specified in the context, it should be understood as "one or more".
[0024] The names of the messages or information exchanged between multiple devices in the embodiments of the present invention are only for illustrative purposes and are not used to limit the scope of these messages or information.
[0025] It should be noted that the embodiments of the present invention relate to a digital certificate automatic distribution system; optionally, the digital certificate automatic distribution system may include, but is not limited to, at least one of the following: an audit node group, a certificate issuing node group, at least one client, a supervision node group, a supervision console, etc., and the embodiments of the present invention do not limit this. Based on this, the execution subject of the digital certificate automatic distribution method provided by the embodiments of the present invention may be the digital certificate automatic distribution system, that is, a module (such as each node, etc.) in the digital certificate automatic distribution system, and a node or a client, etc. may be an electronic device; optionally, different modules (such as different nodes, etc.) in the digital certificate automatic distribution system may be located on the same electronic device or on different electronic devices, and the embodiments of the present invention do not limit this. In other words, the execution subject of the digital certificate automatic distribution method provided by the embodiments of the present invention may be one or more electronic devices in the digital certificate automatic distribution system.
[0026] Among them, the electronic device may be a terminal or a server. Optionally, the terminal mentioned here may include, but is not limited to: smart phones, tablet computers, laptop computers, desktop computers, intelligent voice interaction devices, etc. The server mentioned here may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms, etc.
[0027] Based on the above description, the embodiments of the present invention propose a digital certificate automatic distribution method, which can be executed by the digital certificate automatic distribution system mentioned above. The digital certificate automatic distribution system may include, but is not limited to, an audit node group, a certificate issuing node group, and at least one client, etc. As Figure 1 shown, the digital certificate automatic distribution method may include the following steps S101 - S103:
[0028] S101, when the audit node group receives a certificate application request sent by a target client, it performs identity verification based on the certificate signature request file indicated by the certificate application request to obtain an identity verification result.
[0029] Among them, the target client is any one of at least one client; in the embodiments of the present invention, the client can also be referred to as a user client, and one client can be used to support a user to perform at least one certificate processing operation. Optionally, the at least one certificate processing operation may include, but is not limited to, at least one of the following: certificate application operation, certificate invalidation operation, certificate query operation, certificate download operation, and so on; the embodiments of the present invention do not limit this.
[0030] Optionally, the digital certificate automatic distribution system may include an application layer, and the application layer may include sub-modules such as a user client (for implementing operations such as certificate application) and a supervision console (for implementing real-time verification, supervision and auditing operations, etc.); then correspondingly, the digital certificate automatic distribution system may also include a supervision console. Optionally, the supervision console can be used to support an administrator to perform at least one certificate supervision operation; optionally, the at least one certificate supervision operation may include, but is not limited to, at least one of the following: supervision and auditing operation (such as supervising whether the application of any certificate is compliant, etc.), certificate verification operation (such as verifying whether any certificate is valid, etc.), certificate invalidation operation, and contract deployment operation, etc., and the embodiments of the present invention do not limit this.
[0031] It should be noted that the embodiments of the present invention do not limit the specific execution manner of any operation.
[0032] Optionally, the digital certificate automatic distribution system may also include a contract layer, and the contract layer can be mainly used to deploy various smart contracts, that is, the contract layer may include at least one contract; optionally, the at least one contract may include, but is not limited to, at least one of the following: identity authentication contract, certificate issuance contract, and status supervision contract, etc. (such as Figure 2As shown in [figure], embodiments of the present invention do not limit this. Based on this, the digital certificate automatic distribution system can complete the authentication process, certificate issuance process, certificate invalidation process, and status supervision process, etc. through the cooperation between contracts. Optionally, the administrator can perform contract deployment operations (such as contract addition operations, contract modification operations, and contract deletion operations, etc.) on the supervision console. Then, the supervision console can respond to the detected contract deployment operation and deploy the contract according to the contract indicated by the contract deployment operation. Optionally, different contracts can be deployed on different nodes. For example, the authentication contract can be deployed on the audit node (the audit node can be responsible for executing the authentication contract to achieve authentication), the certificate issuance contract can be deployed on the certificate issuing node (the certificate issuing node can be responsible for executing the certificate issuance contract to achieve certificate issuance), the status supervision contract can be deployed on the supervision node (the supervision node can be responsible for executing the status supervision contract to achieve status supervision), etc. Among them, the smart contract can be an automated program code based on the blockchain, which automatically executes specific operations when preset conditions are met. Optionally, at least one contract can be deployed according to experience or according to actual needs. Embodiments of the present invention do not limit this.
[0033] Optionally, the digital certificate automatic distribution system may further include a consensus layer (which can also be called a node layer). The consensus layer may include, but is not limited to, an audit node group, a certificate issuing node group, and a supervision node group. The nodes in the consensus layer are the actual executors responsible for executing smart contracts and storing the blockchain. Among them, a node group (such as the audit node group, etc.) may include multiple node instances. The consensus layer corresponds to the contract layer (that is, the nodes in the consensus layer can be responsible for executing the contracts in the contract layer). Among them, the blockchain is a distributed database technology that can link data blocks into a chain structure in chronological order through cryptographic methods, and has characteristics such as decentralization, immutability, and traceability. Optionally, the supervision node can be a node with penetration audit authority and can monitor the full-chain data in real time. Optionally, the supervision node group can run the Tendermint BFT consensus algorithm (a Byzantine fault tolerance algorithm with an emergency braking function, allowing the supervision node to initiate a hard fork when detecting a malicious block) and hold a homomorphic decryption key (that is, the same type of decryption key, which can authenticate and supervise each other. For example, different supervision nodes can use the homomorphic decryption key for authentication, etc.).
[0034] Optionally, the digital certificate automatic distribution system may further include a storage layer, which can be the actual storage location of the digital certificates. Optionally, the storage layer may include, but is not limited to, at least one of the following: the state database on the blockchain (also referred to as the on-chain state database, which can be used to store the certificate blockchain) and the regulatory private storage, etc., which are not limited in the embodiments of the present invention; that is to say, the on-chain state database can be used to store the ledger structure of the blockchain (i.e., the certificate blockchain). Optionally, the storage layer may include a storage node group. In this case, the digital certificate automatic distribution system may further include a storage node group, and the storage node group can be used to store the certificate blockchain, etc.; or, the on-chain state database can be responsible for each node in the consensus layer (i.e., the certificate blockchain can be located in each node in the consensus layer, that is to say, each node in the consensus layer can also be used as a storage node respectively), and the regulatory private storage can be deployed only on the regulatory node (for the regulatory node to perform status supervision), etc.; which are not limited in the embodiments of the present invention. Optionally, the regulatory private storage can be used to store any specified parameters for status supervision; optionally, the specified parameters can be set according to experience or actual requirements, which are not limited in the embodiments of the present invention. Based on this, the embodiments of the present invention can implement the digital certificate automatic distribution method through the consortium chain. The consortium chain can refer to a blockchain network jointly managed by multiple organizations (such as the audit node group, the certificate issuing node group, etc.), and nodes need to be authorized to join, with both decentralization and controllability; that is to say, the embodiments of the present invention can achieve decentralized trust through the consortium chain node network.
[0035] Optionally, the certificate blockchain may adopt a single-chain multi-module structure, which can be composed of multiple blocks as a whole, and one block can be a certificate record (i.e., a certificate operation record). Optionally, one block may include three sub-modules (which can be used to store different data respectively), and the three sub-modules can be an audit area, a certificate area, and a supervision area respectively, such as Figure 3As shown. Optionally, the review area module may include, but is not limited to, at least one of the following: encrypted application records (such as including, but not limited to, at least one of the following: the entity to which the certificate belongs (such as an enterprise, etc.), the machine where it is located, the scope of permissions, etc.), review logs (such as including, but not limited to, at least one of the following: the results of identity verification of the corresponding application by each review node (such as passed or not passed, etc.)), and review log identifiers (which can be used to indicate review logs, also known as review log indexes, review log numbers, etc.), etc., and the embodiments of the present invention do not limit this; optionally, the review area data can only be accessed by the review nodes (that is, read or query data, etc.). Optionally, the certificate area module may include, but is not limited to, at least one of the following: certificate metadata and an IP (Internet Protocol) list (which can be used to indicate the machines on which the corresponding certificate supports becoming effective, that is, the certificate indicated by a piece of certificate metadata can be used on the IP addresses indicated by the corresponding IP list), etc., and the embodiments of the present invention do not limit this; optionally, the certificate metadata may include, but is not limited to, at least one of the following: certificate content (that is, the digital certificate), certificate serial number, issuer (such as the CA institution (Certificate Authority) that issues the certificate), validity period, the entity to which it belongs (such as the owner or the enterprise to which it belongs, etc.), etc., and the embodiments of the present invention do not limit this; optionally, the certificate area data can only be accessed by the certificate issuing node. Optionally, the supervision area module may include, but is not limited to, at least one of the following: audit trail data (such as including, but not limited to, application time, applicant, etc.) and supervision records (such as including, but not limited to, operation records executed by a certain supervision node, intervention time limit information, etc., also known as intervention records), etc., and the embodiments of the present invention do not limit this; optionally, the supervision area data can only be accessed by the supervision nodes. Optionally, the above IP list may also be located within the certificate metadata, and the embodiments of the present invention do not limit this.
[0036] Optionally, when the user performs a certificate application operation on the target client, the target client can respond to the detected certificate application operation and send a certificate application request to the audit node group. Optionally, a client can send any request (such as a certificate application request) to any audit node in the audit node group, and after receiving any request, any audit node can send the any request to other audit nodes in the audit node group (that is, audit nodes other than any audit node) to enable each audit node in the audit node group to receive the any request; alternatively, a client can send any request to the audit master node in the audit node group (at this time, the audit node group can include the audit master node), and the audit master node can send the received any request to the audit nodes in the audit node group other than the audit master node to enable each audit node in the audit node group to receive the any request; alternatively, a client can send any request to each audit node in the audit node group to enable each audit node in the audit node group to receive any request sent by the corresponding client, etc.; the embodiments of the present invention do not limit this. Optionally, a client can raise any request to the blockchain network through an encrypted channel, that is, submit it to the audit node group; for example, a client can be encrypted and distributed to the audit node group through an API (Application Program Interface) gateway (the entry component of the digital certificate automatic distribution system). The API gateway can be responsible for request routing, traffic control, and security authentication, etc., and implement two-way TLS (Transport Layer Security) encryption communication. Two-way TLS can also be expressed as mTLS (Mutual TLS, two-way security transport layer protocol, a security communication protocol), that is, a connection with the blockchain gateway can be established through two-way TLS, and the client certificate can be issued by the preset blockchain root CA.
[0037] Optionally, a client may have a user interaction interface (a visual operation interface), and then the user may perform certificate application operations, status query operations, emergency revocation of certificates (i.e., certificate invalidation operations), etc. on the user interaction interface of the target client. Optionally, a client may integrate at least one tool. For example, the at least one tool may include, but is not limited to, at least one of the following: a key generation tool and a verification proxy, etc. The embodiments of the present invention are not limited thereto. Among them, the status query operation can be used to query the status of any certificate (a status can be any one of the following: valid, revoked (i.e., invalid), and disputed, etc. The disputed status means that some nodes consider the certificate valid while some nodes consider the certificate invalid); based on this, the embodiments of the present invention can ensure the accurate management of certificates through three-dimensional status (i.e., valid, invalid, and disputed). Optionally, when the verification proxy detects the certificate content input by the user, it can verify whether the certificate is a certificate issued by the current CA, that is, verify whether the certificate is issued by the current CA institution, and so on.
[0038] Optionally, when performing a certificate application operation, the user may generate a key pair through the target client (such as calling the key generation tool in the target client to generate a key pair), and may create an enhanced certificate signature request (CSR, also known as a certificate signature request) file through the client to implement the certificate application operation. Based on this, the target client may generate a certificate application request based on the generated key pair and certificate signature request file. Optionally, the certificate signature request file may include, but is not limited to, at least one of the following: entity identification (such as entity name or entity number, etc. When an entity is an enterprise, it may be the enterprise name or), geographical location, and IP list, etc.; the embodiments of the present invention are not limited thereto. Optionally, the target client may also automatically append the device fingerprint and blockchain address to generate a certificate application request, such as embedding the device fingerprint and blockchain address and other extended information in the certificate signature request file, so as to implement the enhancement of the CSR format.
[0039] Optionally, the key pair can be an asymmetric key pair, that is, it can include a public key and a private key. Optionally, the private key can stay within the local security environment throughout the process, that is, the private key can be located on the client side and not be sent to the audit node group, etc. Correspondingly, the certificate application request can carry the public key and the certificate signature request file. Optionally, the public key generated by the target client can also be embedded in the certificate signature request file. At this time, the certificate application request can carry the certificate signature request file (that is, the certificate signature request file indicated by the certificate application request can be the certificate signature request file carried by the certificate application request), and the certificate signature request file can include the public key. Based on this, when submitting the certificate application request to the audit node group through an encrypted channel, the CSR data packet (i.e., the CSR file) can be encrypted (such as hybrid encryption, etc., and the present invention embodiment does not limit this encryption method) and submitted to the audit node group. Optionally, when submitting the certificate application request, a timestamp signature can also be added to the CSR file and submitted to the audit node group. Optionally, the digital certificate automatic distribution system can include multiple audit node groups (such as there can be audit node groups in different regions). At this time, any request (such as the certificate application request) can be submitted to the nearest (such as the nearest to the target client) audit node group. Correspondingly, when the CSR file is an encrypted CSR file, after receiving the encrypted CSR file, the audit node group can decrypt the CSR file and trigger the execution of the above-mentioned authentication based on the certificate signature request file indicated by the certificate application request to obtain the authentication result.
[0040] Optionally, the audit node group can automatically verify the identity information based on a smart contract (here, the identity verification contract), and can reach an audit conclusion through an improved PBFT (Practical Byzantine Fault Tolerance) consensus mechanism to obtain the authentication result. In the embodiments of the present invention, the audit node can be a blockchain node responsible for verifying the authenticity of the certificate application materials, running the improved PBFT consensus algorithm, and having the KYC (Know Your Customer) data verification ability. Among them, the improved PBFT consensus algorithm is a Byzantine fault tolerance consensus algorithm, which requires more than 2 / 3 of the nodes in the network to reach an agreement to confirm the validity of the transaction. That is to say, the audit node group can conduct a distributed vote on the certificate application through PBFT to ensure the legality and accuracy of the audit result.
[0041] Optionally, the authentication result (which may also be referred to as the audit result) can be used to indicate successful authentication or failed authentication. Optionally, the authentication result can be an authentication success indication message (which can be used to indicate successful authentication) or an authentication failure indication message (which can be used to indicate failed authentication); optionally, the authentication success indication message can include, but is not limited to, at least one of the following: a success identifier and a success reason code, etc., and the authentication failure indication message can include, but is not limited to, at least one of the following: a failure identifier and a failure reason code (which may also be referred to as a rejection reason code), etc., and the embodiments of the present invention do not limit this. Optionally, the success identifier and the failure identifier can be set according to experience or according to actual requirements, and the embodiments of the present invention do not limit this.
[0042] Optionally, the audit node group (such as the main audit passing node, etc.) can send the authentication result to the certificate issuing node group, such as sending it to each certificate issuing node or the main certificate issuing node, etc.
[0043] S102. When the authentication result is used to indicate successful authentication, the certificate issuing node group reads the certificate signature request file; generates a target digital certificate based on the certificate signature request file, and writes the target digital certificate into the certificate blockchain.
[0044] Optionally, when the public key is outside the certificate signature request file, the certificate issuing node group can also obtain the public key indicated by the certificate application request. In the embodiments of the present invention, the certificate issuing node can be a dedicated node for performing digital certificate signing operations; optionally, the certificate issuing node group can use threshold signature technology to generate digital certificates; among them, threshold signature is a cryptographic scheme that requires at least t nodes to provide signature shards to generate a valid certificate signature, such as t can be 3 or 4, etc., and the embodiments of the present invention do not limit this. Optionally, a digital certificate can be an electronic document used to verify the identity of an entity (such as a user, a device), and can include, but is not limited to, a public key, holder information, and a CA signature.
[0045] Optionally, the certificate issuing node can automatically fill a preset certificate template with the certificate signature request file to obtain a certificate template filling result, and generate a target digital certificate based on the certificate template filling result, or can also directly generate a target digital certificate using the certificate signature request file (that is, in this case, the certificate template filling result may not be generated), etc.; the embodiments of the present invention do not limit this. Optionally, the preset certificate template can be set according to experience or according to actual requirements, and the embodiments of the present invention do not limit this.
[0046] Optionally, the certificate issuing node group (such as the certificate issuing master node in the certificate issuing node group) can also generate the certificate serial number of the target digital certificate based on the blockchain transaction hash (such as a globally unique ID (Identity document, identity card identification number, unique code, etc.), which can also be called a certificate transaction hash, etc.). Optionally, the certificate issuing node group can also bind the start time of the target digital certificate to the generation timestamp of the block where the target digital certificate is located to determine the validity period of the target digital certificate; optionally, the validity period of a certificate can be a preset validity period (such as 365 days, etc.), or it can be a validity period set by the user through a certificate application operation, etc., which is not limited in this embodiment of the present invention. Optionally, the certificate issuing node group can also add a blockchain verification identifier (which can be expressed as BVID, such as the ID of the requesting user, etc., which can also be called an on-chain verification identifier) to the block where the target digital certificate is located. For example, the verification identifier can be added to the certificate area in the block where the target digital certificate is located to mark the user to whom a certificate belongs.
[0047] Optionally, the target digital certificate can be encrypted, that is, the target digital certificate can be encrypted into an encrypted certificate package to be written into the certificate blockchain; illustratively, the certificate issuing master node in the certificate issuing node group can encrypt the target digital certificate based on the public key indicated by the certificate application request (which can be located in the certificate signing request file or outside the certificate signing request file), such as determining the certificate public key based on the public key indicated by the certificate application request to encrypt the target digital certificate using the certificate public key. The embodiment of the present invention does not limit the specific determination method of the certificate public key; illustratively, the certificate public key can be obtained by signing the public key indicated by the certificate application request through the root certificate of the CA, etc. Optionally, the above-mentioned chain verification identifier can also be located in the above-mentioned encrypted certificate package.
[0048] Optionally, when the target digital certificate meets the certificate sharding requirements, the target digital certificate can be sharded and encrypted and uploaded to the chain. Exemplarily, the target digital certificate can be divided into multiple certificate shards, and each certificate shard in the multiple certificate shards can be encrypted separately, so that each encrypted certificate shard (which can also be called an encrypted certificate shard package) can be stored in a block in the certificate blockchain respectively, that is, different encrypted certificate shards can be stored in different blocks, so as to realize writing the target digital certificate into the certificate blockchain. In this case, the smart contract can automatically split the data, and then distribute and store the data after threshold encryption. Optionally, when the user performs a certificate application operation on the target client, the user can also set the certificate importance level. Then, the certificate issuing node group can judge whether the target digital certificate meets the certificate sharding requirements according to the certificate importance level. For example, when the certificate importance level is higher than the preset importance level, it can be determined that the target digital certificate meets the certificate sharding requirements. At this time, it can be considered that the target digital certificate is of a higher importance level, that is, the target digital certificate can be considered as sensitive information. It should be noted that the specific judgment method of the certificate sharding requirements in the embodiments of the present invention is not limited. Optionally, the preset importance level can be set according to experience or according to actual requirements, and the embodiments of the present invention do not limit this. Based on this, the embodiments of the present invention can achieve a balance of privacy protection for important certificates. That is to say, the user applying for an important certificate can obtain multiple certificate shards according to the set certificate importance level to obtain the complete digital certificate, while other users except the user applying for the important certificate cannot obtain the complete certificate shard when only reading one certificate shard, which can further improve the privacy protection of the digital certificate.
[0049] S103. The target client downloads the target digital certificate from the certificate blockchain.
[0050] Optionally, the user may perform a certificate download operation on the target digital certificate at the target client. Then, the target client may respond to the detected certificate download operation and download the target digital certificate from the certificate blockchain. Optionally, the user may input the certificate serial number of the target digital certificate (such as the certificate transaction hash) through the target client to execute the certificate download operation. In this case, the node that receives the certificate download request (such as the audit node or the certificate issuing node, etc.) may obtain the target digital certificate from the blockchain through the certificate serial number and return it to the target client. Or, the user may perform a click operation on the certificate download button displayed on the target client, etc., to execute the certificate download operation. At this time, the target client may obtain the user ID, etc., and send a certificate download request to the audit node group or the certificate issuing node group based on the user ID to download the target digital certificate from the certificate blockchain. In this case, the target digital certificate applied by the user indicated by the user ID may be found from the blockchain through the user ID, and so on. The embodiments of the present invention do not limit this. Based on this, the embodiments of the present invention do not limit the specific implementation process of the certificate download process.
[0051] Optionally, after obtaining authorization, the user may perform a certificate download operation on the target digital certificate at the target client to download the target digital certificate. Optionally, the digital certificate automatic distribution system may automatically authorize the user who applies for the target digital certificate after the target digital certificate is successfully issued. Or, the user may also apply for certificate download permission through the target client, and the administrator may approve the certificate download permission application through the management console. Then, the user may obtain authorization after the approval, and so on. The embodiments of the present invention do not limit this.
[0052] Optionally, when the downloaded target digital certificate is an encrypted target digital certificate (i.e., an encrypted certificate package), the target client may use the local private key (i.e., the private key in the key pair generated by the above target client) to decrypt the target digital certificate to obtain the official certificate file, that is, the decrypted target digital certificate can be obtained.
[0053] Optionally, the user may also input any transaction hash through the target client to query the corresponding certificate status under the operation corresponding to any transaction hash in real time, that is, the above status query operation can be implemented. For example, after the user submits any transaction hash, the gateway may return the visual certificate details, etc., under the operation corresponding to any transaction hash through the on-chain status database (i.e., the certificate blockchain). Or, the certificate serial number may be input through the target client to query the certificate status of the certificate indicated by the input certificate serial number, and so on. The embodiments of the present invention do not limit this. Based on this, the embodiments of the present invention support second-level status verification. Optionally, the target client may also display a certificate issuance progress bar for the target digital certificate in real time so that the user can track the progress in real time through the target client.
[0054] Optionally, the administrator can also detect the blockchain by sending the certificate serial number through the monitoring management console to obtain the status of the corresponding certificate, and offline verification of its authenticity can be realized, etc. Optionally, the digital certificate automatic distribution system may further include a regulatory audit interface, and the regulatory audit interface can provide functions such as data perspective, log traceability, and compliance inspection for regulatory agencies (such as administrators, etc.), and support real-time monitoring dashboards (such as for viewing the application volume and expiration volume of digital certificates over a period of time), that is to say, the regulatory agency can call the regulatory audit interface through the management console to implement various query functions, etc. Optionally, the administrator can also perform audit operations through the regulatory console. Then, the regulatory console can respond to the detected audit operation and send an audit request to the regulatory node group, so that the regulatory node group can obtain all data in real time, automatically generate an audit report that meets regulatory requirements, and return the audit report to the regulatory console, etc.; it should be noted that the specific implementation manner of the audit operation in the embodiments of the present invention is not limited. For example, the regulatory scope and / or regulatory requirements can be specified through the audit operation, or the regulatory requirements may not be specified, so that the regulatory node group generates an audit report according to the preset regulatory requirements, etc.; optionally, the preset regulatory requirements can be set according to experience or according to actual needs, and the embodiments of the present invention do not limit this.
[0055] Optionally, when the audit node group receives a certificate invalidation request, it can perform identity verification based on the certificate signature request file indicated by the certificate invalidation request to obtain an invalidation identity verification result; when the invalidation identity verification result is used to indicate successful identity verification, the certificate issuing node group can generate an invalid digital certificate block and chain the invalid digital certificate block. Optionally, the digital certificate in the invalid digital certificate block can be the digital certificate requested to be invalidated by the certificate invalidation request; optionally, the invalid digital certificate block can record invalidation indication information (such as indicating who invalidated the certificate, etc.) and / or an invalid status identifier, etc.; the embodiments of the present invention do not limit this. Optionally, the certificate invalidation request can be sent by any client in response to a certificate invalidation (also referred to as certificate revocation) operation performed by the user to the audit node group, or can be sent by the regulatory console in response to a certificate invalidation operation performed by the administrator to the audit node group (so that the administrator's authority can be verified during identity verification at this time), etc.; the embodiments of the present invention do not limit this. Optionally, in other embodiments, the regulatory console can also send the certificate invalidation request to the regulatory node group to enable the regulatory node group to execute the corresponding certificate invalidation process, etc.; the present invention does not limit this.
[0056] In summary, the embodiments of the present invention from digital certificate application to distribution can include a user stage (i.e., the user application stage), an audit verification stage (i.e., the identity verification stage), a certificate generation and storage stage, and a certificate distribution stage, such as Figure 4As shown in the figure; based on this, the embodiments of the present invention can be driven by smart contracts throughout the process, eliminating manual intervention, compressing the processing cycle of traditional CAs that takes several days to the second level, and ensuring the traceability of operations through the immutable characteristics of the blockchain.
[0057] When the audit node group in the embodiments of the present invention receives a certificate application request sent by a target client, it can perform identity verification based on the certificate signature request file indicated by the certificate application request to obtain an identity verification result; where the target client is any one of at least one client. Based on this, when the identity verification result is used to indicate that the identity verification is passed, the certificate issuance node group can read the certificate signature request file; and then generate a target digital certificate based on the certificate signature request file, and write the target digital certificate into the certificate blockchain. Correspondingly, the target client can download the target digital certificate from the certificate blockchain. It can be seen that the embodiments of the present invention can realize automatic identity verification through the audit node group and automatic generation of digital certificates through the certificate issuance node group, so as to facilitate the automatic distribution of digital certificates and effectively improve the distribution efficiency of digital certificates.
[0058] Based on the above description, the embodiments of the present invention also propose another method for automatic distribution of digital certificates. Correspondingly, this method for automatic distribution of digital certificates can be executed by the above-mentioned system for automatic distribution of digital certificates, and the system for automatic distribution of digital certificates can include but are not limited to an audit node group, a certificate issuance node group, and at least one client, etc. Please refer to Figure 5 , and this method for automatic distribution of digital certificates can include the following steps S501 - S507:
[0059] S501, when the audit node group receives a certificate application request sent by a target client, it performs identity verification based on the certificate signature request file indicated by the certificate application request to obtain an identity verification result.
[0060] Each review node in the review node group can perform authentication based on the certificate signature request file indicated by the certificate application request respectively, and obtain the verification results under each review node. Optionally, for any review node in the review node group, any review node extracts at least one application information from the certificate signature request file indicated by the certificate application request; and determines the data to be verified based on the at least one application information; where the data to be verified includes at least one of the following: credit score and private key leakage risk score. Optionally, the at least one application information may include, but is not limited to, at least one of the following: applicant user, application address, affiliated entity, domain name, organizational information (such as enterprise name), etc., and the embodiments of the present invention do not limit this. Optionally, the data to be verified may also include, but is not limited to, historical certificate issuance records, credit accumulation values (which can be obtained based on past compliance performance), and enterprise operation data, etc., and the embodiments of the present invention do not limit this. Then, any review node can perform authentication based on the data to be verified, and obtain the verification result under any review node; optionally, when each data in the data to be verified meets the corresponding verification passing conditions, it can be determined that the verification result under any review node is the authentication passing indication information, and when there is data in the data to be verified that does not meet the corresponding verification passing conditions, it can be determined that the verification result under any review node is the authentication failure indication information, and one data corresponds to one verification passing condition. Exemplarily, the verification passing condition corresponding to the credit score may refer to that the credit score is greater than the preset credit score threshold, the verification passing condition corresponding to the private key leakage risk score may refer to that the private key leakage risk score is less than the preset private key leakage risk score threshold, the verification passing condition corresponding to the enterprise operation data may refer to that the number of abnormal data in the enterprise operation data is less than the preset number threshold (i.e., it can be judged whether the operation data is compliant), the verification passing condition corresponding to the credit accumulation value may refer to that the credit accumulation value is higher than the preset credit accumulation threshold, the verification passing condition corresponding to the historical certificate issuance record may refer to that there are no abnormal expiration or issuance failure records in the historical certificate issuance record, etc.; the embodiments of the present invention do not limit this. Optionally, the preset credit score threshold, the preset private key leakage risk score threshold, the preset number threshold, and the preset credit accumulation threshold, etc. can all be set according to experience, or can be set according to actual needs, and the embodiments of the present invention do not limit this. Based on this, the embodiments of the present invention can call a smart contract (herein refers to the authentication contract) to check historical behaviors, such as automatically extracting the domain name, organizational information, etc. in the CSR, and cross-verifying through the blockchain query of the WHOIS database (an Internet database about users, host systems, networks, and domains maintained by the Defense Data Network Information Center), enterprise industrial and commercial information, etc., so as to achieve multi-dimensional risk assessment to obtain the verification result.
[0061] Based on this, the audit node group can count the verification results under each audit node, obtain at least one statistical verification result and the statistical quantity of each statistical verification result in the at least one statistical verification result, where the statistical quantity of a statistical verification result is used to indicate the quantity of verification results under each audit node that are the corresponding statistical verification result; and based on the statistical quantity of each statistical verification result, determine the identity verification result from the at least one statistical verification result, so as to enable the audit node group to perform identity verification based on the certificate signature request file indicated by the certificate application request and obtain the identity verification result. Optionally, the identity verification result may be the statistical verification result with the largest statistical quantity among the at least one statistical verification result, or may be the statistical verification result whose statistical quantity reaches a preset statistical quantity threshold, etc., and the embodiments of the present invention do not limit this; optionally, the preset statistical quantity threshold may be set according to experience or may be set according to actual requirements, and the embodiments of the present invention do not limit this. Exemplarily, when the number of audit nodes in the audit node group is 5, the preset statistical quantity threshold may be 3. Then, at this time, the statistical verification result with a statistical quantity reaching 3 may be used as the identity verification result. That is to say, after at least 3 out of 5 audit nodes reach an agreement, the verification result (i.e., the statistical verification result) reached by at least 3 audit nodes in agreement can be used as the identity verification result, thereby generating an audit result. At this time, identity verification can be achieved through an improved PBFT consensus process.
[0062] Optionally, the audit node group may include an audit master node. In this case, the verification results under each audit node can be aggregated into the audit master node (that is, each audit node other than the audit master node in the audit node group can send the corresponding verification result to the audit master node). Then, the audit master node in the audit node group can count the verification results under each audit node to achieve the counting of the verification results under each audit node by the audit node group; or, the verification results under each audit node can be aggregated into any one audit node, and any one audit node can count the verification results under each audit node to achieve the counting of the verification results under each audit node by the audit node group, and so on; the embodiments of the present invention do not limit this.
[0063] In summary, the identity verification contract in the embodiments of the present invention can automatically execute the KYC process, call the oracle to verify the applicant's qualifications, and record the voting results of the audit nodes; based on this, the embodiments of the present invention can enable the audit node group to complete the interaction in stages such as data preparation and submission, and can ensure the authenticity of the request. It should be noted that the audit node group adopts an improved PBFT algorithm to achieve fast Byzantine fault tolerance in the audit node group. A single consensus cycle only requires 1.2 seconds, with high efficiency.
[0064] Optionally, the review node group can also perform a legality screening on any request; for example, after decrypting the CSR file, the review node group can first verify the validity and / or format compliance of the integer signature request file (that is, determine whether the format is reasonable), so as to discard unreasonable requests.
[0065] Optionally, when the authentication result is used to indicate that the authentication fails, the review node group can also trigger a manual review process. After the review conclusion is used to indicate that the authentication is passed, the certificate issuing node group can read the certificate signature request file to generate a target digital certificate and chain it up, etc.
[0066] Optionally, the review node group can broadcast the authentication result, etc., to the entire network through the Gossip protocol (a decentralized, fault-tolerant and eventually consistent protocol), such as broadcasting to each certificate issuing node, etc.
[0067] S502. When the authentication result is used to indicate that the authentication is passed, the certificate issuing node group reads the certificate signature request file.
[0068] Optionally, the certificate issuing node group can read the certificate signature request files indicated by all requests that have passed the authentication. Optionally, the certificate issuing node group can read the certificate signature request files through each target issuing node respectively.
[0069] S503. Each target issuing node among the multiple target issuing nodes included in the certificate issuing node group respectively generates a certificate signature shard under the corresponding target issuing node based on the certificate signature request file; the multiple target issuing nodes include a certificate issuing master node.
[0070] Optionally, the above-mentioned multiple target issuing nodes can be certificate issuing nodes determined from the certificate issuing node group with the number of specified issuing nodes; optionally, the number of specified issuing nodes can be set according to experience or according to actual needs, and the embodiments of the present invention do not limit this. For example, assuming that the number of certificate issuing nodes in the certificate issuing node group is 5 and the number of specified issuing nodes is 3, then the embodiments of the present invention can adopt a (t = 3, n = 5) threshold signature scheme, select 3 certificate issuing nodes to generate signature shards, so as to achieve collaborative signature.
[0071] Optionally, the certificate-issuing master node can be elected from the certificate-issuing node group based on the Raft protocol (a strongly consistent, decentralized, highly available distributed protocol and a consensus algorithm). Optionally, multiple target issuing nodes can be idle certificate-issuing nodes determined by the certificate-issuing master node, or each certificate-issuing node in the certificate-issuing node group can also be a target issuing node, or they can be randomly selected, etc. The embodiments of the present invention do not limit this. Based on this, the embodiments of the present invention can optimize the log replication process through the certificate-issuing master node and support more than 2000 transactions per second for packaging.
[0072] Optionally, when a target issuing node generates a certificate signature shard under the corresponding target issuing node based on the certificate signature request file, it can generate a certificate template filling result based on the certificate signature request file and generate a certificate signature shard under the corresponding target issuing node based on the certificate template filling result (for example, it can use the certificate template filling result and / or the CA certificate (i.e., the root certificate) to generate a certificate signature shard under the corresponding target issuing node), etc. Optionally, a certificate-issuing node (such as the certificate-issuing master node) can also implement validity period calculation and signing permission control, etc., to determine the validity period and certificate permissions (such as read permission or write permission, etc.) of the target digital certificate, etc.; the embodiments of the present invention do not limit this.
[0073] S504. Each target issuing node among the multiple target issuing nodes except the certificate-issuing master node respectively sends the certificate signature shard under the corresponding target issuing node to the certificate-issuing master node.
[0074] S505. The certificate-issuing master node aggregates the certificate signature shards under each target issuing node to obtain the target digital certificate, so as to enable the certificate-issuing node group to generate the target digital certificate based on the certificate signature request file.
[0075] Optionally, the certificate-issuing master node can use the BLS aggregate signature technology (an algorithm that can achieve signature aggregation and key aggregation, also known as the BLS signature algorithm) to aggregate the certificate signature shards under each target issuing node to obtain the target digital certificate. Based on this, the BLS aggregate signature technology in the embodiments of the present invention reduces the PBFT communication overhead by 70%; and can implement pipelined Raft log replication, increasing the throughput by 3 times.
[0076] Optionally, the above target digital certificate can be a blockchain certificate with a timestamp.
[0077] In the embodiments of the present invention, the target digital certificate can be generated through a certificate issuance contract. That is to say, the certificate issuance contract can manage certificate template generation, validity period calculation, and signing permission control, and trigger multi-node collaborative signature.
[0078] S506, the certificate issuing node group writes the target digital certificate into the certificate blockchain.
[0079] Optionally, the certificate issuing master node may generate a candidate block and generate certificate metadata corresponding to the candidate block (which may also be referred to as certificate metadata corresponding to the target digital certificate) based on the target digital certificate. The certificate metadata includes the target digital certificate; store the certificate metadata in the candidate block, such as storing it in the certificate area included in the candidate block; further, the candidate block may be chained to the blockchain to enable the certificate issuing node group to write the target digital certificate into the certificate blockchain. Optionally, when the importance level of the target digital certificate is relatively high (that is, the corresponding certificate importance level is higher than the preset importance level), multiple candidate blocks may be determined, and certificate metadata corresponding to the candidate blocks (which may also be referred to as certificate metadata corresponding to the certificate shards) may be generated based on each of the certificate shards in the multiple certificate shards corresponding to the target digital certificate. One candidate block corresponds to one certificate shard. At this time, one certificate metadata may include one certificate shard, and then each certificate metadata may be stored in the corresponding candidate block, and so on. It should be understood that the method of storing one certificate shard in one block is the same as the method of storing the complete certificate in one block; for the convenience of description, the subsequent description will be based on the example of storing the target digital certificate in one block.
[0080] Optionally, the certificate metadata corresponding to the target digital certificate may include, but is not limited to, at least one of the following: certificate serial number, issuer, validity period, certificate content (i.e., the target digital certificate), applicant user ID, affiliated entity, certificate status flag, and IP list, etc. The embodiments of the present invention do not limit this. Based on this, the embodiments of the present invention may store the certificate metadata in the blockchain to implement the chaining of core data. Among them, the certificate status flag may be used to indicate the status of the certificate (such as valid or invalid, etc.); optionally, a certificate status flag may be a valid status flag or an invalid status flag. The valid status flag may be used to indicate the valid status, and the invalid status flag may be used to indicate the invalid status; optionally, both the valid status flag and the invalid status flag may be set according to experience or actual requirements. The embodiments of the present invention do not limit this.
[0081] Optionally, when the certificate blockchain is stored in a storage node other than the nodes included in the consensus layer, the certificate issuing master node may send a chaining request for the candidate block to any storage node, so that any storage node chains the candidate block based on the chaining request, thereby implementing the certificate issuing master node to chain the candidate block.
[0082] Optionally, after storing the certificate metadata in the candidate block, the certificate issuing master node can also synchronize the log to multiple certificate issuing nodes to be confirmed through the Raft protocol (such as all nodes other than the certificate issuing master node among multiple target issuing nodes, or all nodes other than the certificate issuing master node in the certificate issuing node group, etc.). After multiple certificate issuing nodes to be confirmed have confirmed, the certificate issuing master node can complete block solidification (i.e., perform block chain - on for the candidate block). Optionally, when the certificate blockchain is stored in each node in the consensus layer, after the block is chained, through a hierarchical broadcast strategy (such as sequentially broadcasting to the audit node group, the certificate issuing node group, the regulatory node group, etc.), the entire network of nodes can be quickly covered (such as covering the entire network of nodes within 8 seconds) to update the certificate blockchain in each node. Optionally, after each new block is generated (i.e., after the new block is chained), the node that generates the new block (such as the certificate issuing master node or any storage node, etc.) can synchronize the new block to the entire network within 8 seconds through the Gossip protocol, so as to synchronize the certificate status in the new block to the entire network.
[0083] In summary, the certificate issuing node group can use threshold signature technology to generate digital certificates and store the core data on the chain for evidence, so as to realize the encrypted storage of digital certificates in a distributed network.
[0084] Optionally, in other embodiments, the target digital certificate can also be encrypted and stored in the IPFS (a distributed file storage protocol that realizes decentralized storage and sharing of files through content - based addressing (CID hash, a string of codes for storing files by IPFS nodes)) network, and the content identifier (i.e., CID) of the target digital certificate in the IPFS network is stored in the certificate metadata corresponding to the target digital certificate to be bound to the on - chain record, etc.; the present invention does not limit this. Based on this, the embodiments of the present invention can store the digital certificate file body through IPFS and combine blockchain hash indexing to solve the problem of storage space expansion.
[0085] S507, the target client downloads the target digital certificate from the certificate blockchain.
[0086] Optionally, the audit node group can also determine the audit log for the certificate application request and the audit log identifier of the audit log, and add the audit log identifier to the candidate block (such as adding it to the audit area included in the candidate block) to implement the on-chain of the audit log identifier. Exemplarily, the audit node group can determine the audit log of the certificate application request through the audit master node. The audit log can include the verification results under each audit node (that is, the verification results under each audit node obtained by authenticating the certificate signature request file indicated by the certificate application request), that is, the verification results under each audit node can be added to the audit log to implement the determination of the audit log, and so on. Optionally, the audit log identifier of the audit log can be determined according to the audit log identifier generation policy. Optionally, the audit log identifier generation policy can be set according to experience or according to actual requirements. The embodiments of the present invention do not limit this. Optionally, when the audit node group adds the audit log identifier to the candidate block, the audit node group can send the audit log identifier to the certificate issuance master node (such as sending the audit log identifier to the certificate issuance master node through the audit master node) so that the certificate issuance master node adds the audit log identifier to the candidate block, thereby implementing the audit node group adding the audit log identifier to the candidate block; or, when the candidate area is located at any storage node (that is, any storage node other than the certificate issuance master node), then the audit node group can send the audit log identifier to any storage node so that any storage node adds the audit log identifier to the candidate block, and so on; the embodiments of the present invention do not limit this. Optionally, when the certificate issuance master node generates a candidate block at any storage node, the certificate issuance master node can also send the certificate metadata to any storage node to store the certificate metadata in the candidate block, thereby implementing the certificate issuance master node storing the certificate metadata in the candidate block; when the certificate issuance master node generates a candidate block locally and stores the certificate metadata in the candidate block and then sends the candidate block to any storage node, the certificate issuance master node can store the certificate metadata in the candidate block locally, and so on; the embodiments of the present invention do not limit this.
[0087] Furthermore, the audit node group can also store the audit log in the Ceph cluster (a distributed storage cluster), such as sending the audit log to the Ceph cluster through the audit master node for storage. Optionally, the audit log supports being encrypted for storage in the Ceph cluster.
[0088] Optionally, in other embodiments, the audit node group can also add the audit log to the candidate block, thereby putting the audit log on the chain, and so on; the present invention does not limit this.
[0089] Optionally, the digital certificate automatic distribution system may further include a supervision node group, which supports the supervision of the blocks on the certificate blockchain. Optionally, the supervision node group may run the BFT algorithm to ensure the final certainty of the supervision operation (i.e., ensure that all supervision nodes perform the same supervision operation). Optionally, the supervision node group may further provide the ability to intervene in hard forks, that is, when the supervision node group detects a malicious block (such as a block with a disputed certificate status, that is, when the certificate status marks of the same block are different on different nodes, the block can be regarded as a malicious block), the certificate status marks in the malicious block can be unified into the same certificate status mark with the largest number among multiple nodes; optionally, the multiple nodes may be all nodes in the consensus layer or a supervision node group, etc., and the embodiments of the present invention do not limit this.
[0090] Optionally, the supervision node group may further determine the audit trail data corresponding to the target digital certificate and add the audit trail data to the candidate block (such as adding it to the supervision area included in the candidate block); optionally, the audit trail data may include but is not limited to: request time (such as application time), request user ID (such as application user ID), etc., and the embodiments of the present invention do not limit this. Among them, the audit trail data can be used by the supervision node for block supervision.
[0091] Optionally, after the supervision node group supervises any block on the certificate blockchain (such as supervision operations such as intervention failure), it may generate a supervision record and upload the supervision record to the chain to add a new block to the certificate blockchain, such as adding the supervision record to the supervision area included in the new block; optionally, the new block may also include the data in any block. Optionally, the supervision node may receive a new blockchain (i.e., the updated blockchain) in real time, so as to support auditing new content and generating a compliance report.
[0092] Optionally, when the audit node group receives a private key leakage handling request, it may determine that the private key leakage is detected, and thus authenticate the private key leakage handling request. After consensus confirmation by the audit node group (such as after passing the authentication), it may modify the certificate status mark of the certificate indicated by the private key leakage handling request, that is, modify it to an invalid status mark; or, after consensus confirmation by the audit node group, it may send the private key leakage handling request to the supervision node group to enable the supervision node group to modify the certificate status mark of the certificate indicated by the private key leakage handling request. Optionally, the data carried by the private key leakage handling request may include but is not limited to at least one of the following: private key leakage indication information, certificate serial number, application user ID, affiliated entity, etc., and the embodiments of the present invention do not limit this.
[0093] Optionally, when the regulatory node group detects a certificate expiration event, it can also call the status management contract to automatically initiate a transaction. After being consensus-confirmed by multiple regulatory nodes in the regulatory node group, the certificate status flag of the expired certificate is modified. Based on this, the embodiments of the present invention can automatically perform status changes when a status change requirement is detected.
[0094] Optionally, after the status change is made, any node in the consensus layer can push the status change to the user in real time, so that the user can grasp the certificate status in real time. Based on this, the embodiments of the present invention can introduce a dynamic permission model, different node types can have different contract call permissions, and an event-driven architecture can be adopted to realize pushing the status change to the corresponding user in real time.
[0095] Optionally, when the regulatory node detects data anomalies (such as certificate issuance failure, etc.), it can also reverse-trigger the consensus layer to start a recovery process, and the contract layer can automatically generate a compensation transaction; for example, when a certificate application failure is detected, the certificate issuance node group can be triggered to execute a certificate issuance retry process, so as to generate a corresponding digital certificate for uploading and storing. Based on this, the embodiments of the present invention can automatically trigger a retry process when a signing failure is detected to implement a self-healing contract.
[0096] Optionally, when a new node joins the digital certificate automatic distribution system, it needs to obtain the endorsement of existing nodes in the digital certificate automatic distribution system that is greater than or equal to 2 / 3 (that is, there need to be more than or equal to 2 / 3 nodes recognizing the addition of the new node); and / or, hardware fingerprint verification can be combined to prevent Sybil attacks, so as to realize the dynamic access mechanism of the system.
[0097] In summary, after being encapsulated by the application layer, the user request can trigger the business logic of the contract layer. The consensus layer ensures the legality of operations, and finally the storage layer persists the records, thus achieving vertical collaboration. Moreover, the consensus result of the auditing node can be synchronously transmitted to the certificate issuing node in real time, triggering the execution of the certificate issuance contract. The supervision node can penetrate the data of each layer to conduct cross-layer auditing, thus achieving horizontal linkage. Based on this, the embodiments of the present invention can implement a four-layer architecture collaboration mechanism, which can effectively support the certificate management requirements of millions of tenants and billions of devices, and can meet new security requirements such as real-time dynamic permission adjustment. Specifically, the embodiments of the present invention can divide the blockchain nodes into functional entities such as auditing nodes, certificate issuing nodes, and supervision nodes to form a check and balance mechanism. Exemplarily, the auditing nodes can focus on identity verification and compliance review, the issuing nodes can perform cryptographic operations and certificate generation, and the supervision nodes can conduct penetration auditing and emergency intervention. In addition, the auditing nodes in the embodiments of the present invention can adopt an improved PBFT algorithm (introducing a reputation evaluation mechanism), the certificate issuing nodes can adopt a pipelined Raft algorithm (parallel log replication), the supervision nodes can run Tendermint BFT (with an emergency braking function), and cross-layer consensus coordination can be achieved (i.e., the finality synchronization of different consensus groups can be achieved through a gradient confirmation protocol), so as to reduce the consensus delay and improve the certificate throughput.
[0098] When the auditing node group in the embodiments of the present invention receives a certificate application request sent by a target client, it can perform identity verification based on the certificate signature request file indicated by the certificate application request to obtain an identity verification result. When the identity verification result is used to indicate that the identity verification is passed, the certificate issuing node group can read the certificate signature request file. Each of the multiple target issuing nodes included in the certificate issuing node group can respectively generate a corresponding certificate signature shard under the target issuing node based on the certificate signature request file. The multiple target issuing nodes include a certificate issuing master node. Moreover, each of the target issuing nodes other than the certificate issuing master node among the multiple target issuing nodes respectively sends the certificate signature shard under the corresponding target issuing node to the certificate issuing master node. Based on this, the certificate issuing master node aggregates the certificate signature shards under each target issuing node to obtain a target digital certificate, so as to implement the generation of the target digital certificate by the certificate issuing node group based on the certificate signature request file. Further, the certificate issuing node group can write the target digital certificate into the certificate blockchain. Then correspondingly, the target client can download the target digital certificate from the certificate blockchain. It can be seen that the embodiments of the present invention can eliminate the risk of single point of failure through the auditing node group, the certificate issuing node group, and the supervision node group, etc., improve the system availability to 99.999%, and achieve permission separation to prevent the abuse of power by a single role. Moreover, the embodiments of the present invention can implement the automatic issuance of digital certificates by the certificate issuing node group, effectively reduce manual intervention, and thus conveniently conduct automatic distribution of digital certificates, which can effectively improve the certificate issuance efficiency.
[0099] Based on the description of the related embodiments of the above digital certificate automatic distribution method, an embodiment of the present invention further provides a digital certificate automatic distribution system; the digital certificate automatic distribution system includes an audit node group, a certificate issuance node group, and at least one client. The digital certificate automatic distribution system can execute Figure 1 or Figure 5 the digital certificate automatic distribution method shown, that is, the digital certificate automatic distribution system can run the above units:
[0100] The audit node group is used for: when receiving a certificate application request sent by a target client, performing identity authentication based on the certificate signature request file indicated by the certificate application request to obtain an identity authentication result; wherein, the target client is any one of the at least one client;
[0101] The certificate issuance node group is used for: when the identity authentication result is used to indicate passing the identity authentication, reading the certificate signature request file; generating a target digital certificate based on the certificate signature request file, and writing the target digital certificate into the certificate blockchain;
[0102] The target client is used for: downloading the target digital certificate from the certificate blockchain.
[0103] In one implementation manner, when the audit node group performs identity authentication based on the certificate signature request file indicated by the certificate application request to obtain an identity authentication result, it may specifically include:
[0104] Each audit node in the audit node group is used for: respectively performing identity authentication based on the certificate signature request file indicated by the certificate application request to obtain the verification results under the respective audit nodes;
[0105] The audit node group is used for: counting the verification results under the respective audit nodes to obtain at least one statistical verification result and the statistical quantity of each statistical verification result in the at least one statistical verification result, and the statistical quantity of a statistical verification result is used to indicate the number of verification results under the respective audit nodes that are the corresponding statistical verification result;
[0106] Based on the statistical quantities of the respective statistical verification results, determining the identity authentication result from the at least one statistical verification result, so as to implement the audit node group performing identity authentication based on the certificate signature request file indicated by the certificate application request to obtain the identity authentication result.
[0107] In another implementation, when each audit node in the audit node group performs authentication based on the certificate signature request file indicated by the certificate application request to obtain the verification results under each audit node, it may specifically include:
[0108] For any audit node in the audit node group, the any audit node is used to: extract at least one application information from the certificate signature request file indicated by the certificate application request;
[0109] Based on the at least one application information, determine the data to be verified; wherein, the data to be verified includes at least one of the following: credit score and private key leakage risk score;
[0110] Perform authentication based on the data to be verified to obtain the verification result under the any audit node.
[0111] In another implementation, when the certificate issuance node group generates a target digital certificate based on the certificate signature request file, it may specifically include:
[0112] Each target issuance node in the multiple target issuance nodes included in the certificate issuance node group is used to: respectively generate a certificate signature shard under the corresponding target issuance node based on the certificate signature request file; the multiple target issuance nodes include a certificate issuance master node;
[0113] Each target issuance node other than the certificate issuance master node in the multiple target issuance nodes is used to: respectively send the certificate signature shard under the corresponding target issuance node to the certificate issuance master node;
[0114] The certificate issuance master node is used to: aggregate the certificate signature shards under the respective target issuance nodes to obtain a target digital certificate, so as to implement the certificate issuance node group to generate a target digital certificate based on the certificate signature request file.
[0115] In another implementation, when the certificate issuance node group writes the target digital certificate into the certificate blockchain, it may specifically include:
[0116] The certificate issuance master node is used to: generate a candidate block and generate certificate metadata corresponding to the candidate block based on the target digital certificate, where the certificate metadata includes the target digital certificate;
[0117] Store the certificate metadata in the candidate block;
[0118] Perform block chain-on of the candidate block to implement the certificate issuance node group to write the target digital certificate into the certificate blockchain.
[0119] In another implementation, the audit node group is further configured to: determine an audit log for the certificate application request and an audit log identifier of the audit log, and add the audit log identifier to the candidate block to implement the on-chain of the audit log identifier;
[0120] Store the audit log in the Ceph cluster.
[0121] In another implementation, the digital certificate automatic distribution system further includes a supervision node group, and the supervision node group supports the supervision of blocks on the certificate blockchain;
[0122] The supervision node group is configured to: determine the audit trail data corresponding to the target digital certificate and add the audit trail data to the candidate block; and / or,
[0123] The supervision node group is configured to: after supervising any block on the certificate blockchain, generate a supervision record and chain the supervision record to add a new block on the certificate blockchain.
[0124] In another implementation, the audit node group is further configured to: when receiving a certificate invalidation request, perform identity authentication based on the certificate signature request file indicated by the certificate invalidation request to obtain an invalidation identity authentication result;
[0125] When the invalidation identity authentication result is used to indicate successful authentication, the certificate issuance node group generates an invalid digital certificate block and chains the invalid digital certificate block.
[0126] According to an embodiment of the present invention, each unit in the digital certificate automatic distribution system can be separately or all combined into one or several other units to form, or a certain (some) unit can be further split into multiple smaller units in terms of function to form, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present invention. The above units are divided based on logical functions. In practical applications, the function of one unit can also be implemented by multiple units, or the functions of multiple units can be implemented by one unit. In other embodiments of the present invention, any digital certificate automatic distribution system can also include other units. In practical applications, these functions can also be assisted by other units and can be achieved by the cooperation of multiple units.
[0127] When the audit node group in the embodiment of the present invention receives a certificate application request sent by a target client, it can perform identity authentication based on the certificate signature request file indicated by the certificate application request to obtain an identity authentication result; wherein, the target client is any one of at least one client. Based on this, when the identity authentication result is used to indicate successful authentication, the certificate issuing node group can read the certificate signature request file; and then generate a target digital certificate based on the certificate signature request file and write the target digital certificate into the certificate blockchain. Correspondingly, the target client can download the target digital certificate from the certificate blockchain. It can be seen that the embodiment of the present invention can realize automatic identity audit through the audit node group and automatic generation of digital certificates through the certificate issuing node group, so as to facilitate automatic distribution of digital certificates and effectively improve the distribution efficiency of digital certificates.
[0128] Based on the description of the above method embodiments and system embodiments, an exemplary embodiment of the present invention further provides an electronic device, including: at least one processor; and a memory communicatively connected to the at least one processor. The memory stores a computer program that can be executed by the at least one processor, and when the computer program is executed by the at least one processor, it is used to cause the electronic device to execute the method according to the embodiment of the present invention.
[0129] An exemplary embodiment of the present invention further provides a non-transitory computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor of a computer, it is used to cause the computer to execute the method according to the embodiment of the present invention.
[0130] An exemplary embodiment of the present invention further provides a computer program product, including a computer program, wherein when the computer program is executed by a processor of a computer, it is used to cause the computer to execute the method according to the embodiment of the present invention.
[0131] Reference Figure 6 , the structural block diagram of an electronic device 600 that can be used as a server or a client of the present invention will now be described. It is an example of a hardware device that can be applied to various aspects of the present invention. The electronic device is intended to represent various forms of digital electronic computer devices, such as, laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as, personal digital processors, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are only examples and are not intended to limit the implementation of the present invention described herein and / or claimed.
[0132] As Figure 6As shown, the electronic device 600 includes a computing unit 601 that can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 602 or a computer program loaded from a storage unit 608 into a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the electronic device 600 can also be stored. The computing unit 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.
[0133] Multiple components in the electronic device 600 are connected to the I / O interface 605, including: an input unit 606, an output unit 607, a storage unit 608, and a communication unit 609. The input unit 606 can be any type of device capable of inputting information into the electronic device 600. The input unit 606 can receive input numerical or character information and generate key signal inputs related to the user settings and / or function controls of the electronic device. The output unit 607 can be any type of device capable of presenting information and can include, but is not limited to, a display, a speaker, a video / audio output terminal, a vibrator, and / or a printer. The storage unit 608 can include, but is not limited to, magnetic disks and optical discs. The communication unit 609 allows the electronic device 600 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks and can include, but is not limited to, a modem, a network card, an infrared communication device, a wireless communication transceiver, and / or a chipset, such as a BluetoothTM device, a WiFi device, a WiMax device, a cellular communication device, and / or the like.
[0134] The computing unit 601 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 601 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The computing unit 601 executes the various methods and processes described above. For example, in some embodiments, the volume mesh generation method can be implemented as a computer software program tangibly embodied in a machine-readable medium, such as the storage unit 608. In some embodiments, part or all of the computer program can be loaded and / or installed onto the electronic device 600 via the ROM 602 and / or the communication unit 609. In some embodiments, the computing unit 601 can be configured to execute the volume mesh generation method in any other appropriate manner (e.g., by means of firmware).
[0135] The program code for implementing the methods of the present invention can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general purpose computer, a special purpose computer, or other programmable data processing device, such that when executed by the processor or controller, the program codes cause the functions / operations specified in the flowchart and / or block diagram to be implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package partially on the machine and partially on a remote machine, or entirely on a remote machine or server.
[0136] In the context of the present invention, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0137] As used in the present invention, the terms “machine-readable medium” and “computer-readable medium” refer to any computer program product, apparatus, and / or device (e.g., a disk, an optical disk, a memory, a programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term “machine-readable signal” refers to any signal for providing machine instructions and / or data to a programmable processor.
[0138] In order to provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the computer. Other kinds of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).
[0139] The systems and techniques described herein can be implemented in a computing system including backend components (e.g., as a data server), or a computing system including middleware components (e.g., an application server), or a computing system including frontend components (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described herein), or a computing system including any combination of such backend components, middleware components, or frontend components. The components of the system can be interconnected to each other by digital data communication in any form or medium (e.g., a communication network). Examples of communication networks include: local area network (LAN), wide area network (WAN), and the Internet.
[0140] A computer system can include clients and servers. The clients and servers are generally remote from each other and typically interact through a communication network. The client - server relationship is created by computer programs running on the respective computers and having a client - server relationship with each other.
[0141] Also, it should be understood that the above - disclosed are only the preferred embodiments of the present invention, and of course cannot be used to limit the scope of the rights of the present invention. Therefore, equivalent changes made according to the claims of the present invention still fall within the scope covered by the present invention.
Claims
1. A method for automatically distributing digital certificates, characterized in that The method is applied to a digital certificate automatic distribution system, which includes an audit node group, a certificate issuing node group, and at least one client. The method includes: When the audit node group receives a certificate application request sent by a target client, it performs identity verification based on the certificate signature request file indicated by the certificate application request to obtain an identity verification result. Herein, the target client is any one of the at least one client; When the identity verification result is used to indicate successful identity verification, the certificate issuing node group reads the certificate signature request file, generates a target digital certificate based on the certificate signature request file, and writes the target digital certificate into the certificate blockchain; The target client downloads the target digital certificate from the certificate blockchain.
2. The method according to claim 1, characterized in that, The audit node group performs identity verification based on the certificate signature request file indicated by the certificate application request to obtain an identity verification result, including: Each audit node in the audit node group performs identity verification based on the certificate signature request file indicated by the certificate application request to obtain a verification result under each audit node; The audit node group statistically analyzes the verification results under each audit node to obtain at least one statistical verification result and the statistical quantity of each statistical verification result in the at least one statistical verification result. The statistical quantity of a statistical verification result is used to indicate the number of verification results under each audit node that are the corresponding statistical verification result; Based on the statistical quantities of the respective statistical verification results, the identity verification result is determined from the at least one statistical verification result, so as to enable the audit node group to perform identity verification based on the certificate signature request file indicated by the certificate application request and obtain the identity verification result.
3. The method according to claim 2, characterized in that Each audit node in the audit node group performs identity verification based on the certificate signature request file indicated by the certificate application request to obtain a verification result under each audit node, including: For any audit node in the audit node group, the any audit node extracts at least one application information from the certificate signature request file indicated by the certificate application request; Based on the at least one application information, the data to be verified is determined. Herein, the data to be verified includes at least one of the following: credit score and private key leakage risk score; Identity verification is performed based on the data to be verified to obtain the verification result under the any audit node.
4. The method according to any one of claims 1-3, characterized in that, The certificate issuing node group generates a target digital certificate based on the certificate signature request file, including: Each target issuing node among the multiple target issuing nodes included in the certificate issuing node group respectively generates a certificate signature shard under the corresponding target issuing node based on the certificate signature request file. The multiple target issuing nodes include a certificate issuing master node; Each target issuing node other than the certificate issuing master node among the multiple target issuing nodes respectively sends the certificate signature shard under the corresponding target issuing node to the certificate issuing master node; The certificate issuing master node aggregates the certificate signature shards under each target issuing node to obtain a target digital certificate, so as to enable the certificate issuing node group to generate a target digital certificate based on the certificate signature request file.
5. The method according to claim 3, wherein The certificate issuing node group writes the target digital certificate into the certificate blockchain, including: The certificate issuing master node generates a candidate block and generates certificate metadata corresponding to the candidate block based on the target digital certificate, where the certificate metadata includes the target digital certificate; Store the certificate metadata in the candidate block; Perform blockchain insertion on the candidate block, so as to enable the certificate issuing node group to write the target digital certificate into the certificate blockchain.
6. The method according to claim 5, characterized in that The method further includes: The audit node group determines the audit log for the certificate application request and the audit log identifier of the audit log, and adds the audit log identifier to the candidate block, so as to enable the audit log identifier to be on the chain; Store the audit log in the Ceph cluster.
7. The method according to claim 6, wherein The digital certificate automatic distribution system further includes a supervision node group, and the supervision node group supports supervision of the blocks on the certificate blockchain. The method further includes: The supervision node group determines the audit trail data corresponding to the target digital certificate and adds the audit trail data to the candidate block; and / or, After the supervision node group supervises any block on the certificate blockchain, it generates a supervision record and uploads the supervision record to the chain to add a new block to the certificate blockchain.
8. The method according to any one of claims 1-3, characterized in that, The method further includes: When receiving a certificate invalidation request, the audit node group performs identity verification based on the certificate signature request file indicated by the certificate invalidation request to obtain an invalidation identity verification result; When the invalidation identity verification result is used to indicate successful identity verification, the certificate issuing node group generates an invalid digital certificate block and performs blockchain insertion on the invalid digital certificate block.
9. A digital certificate automatic distribution system, characterized in that The digital certificate automatic distribution system includes an audit node group, a certificate issuing node group, and at least one client; The audit node group is configured to: when receiving a certificate application request sent by a target client, perform identity verification based on the certificate signature request file indicated by the certificate application request to obtain an identity verification result; where the target client is any one of the at least one client; The certificate issuing node group is configured to: when the identity verification result is used to indicate successful identity verification, read the certificate signature request file; generate a target digital certificate based on the certificate signature request file, and write the target digital certificate into the certificate blockchain; The target client is configured to: download the target digital certificate from the certificate blockchain.
10. The system according to claim 9, wherein, The digital certificate automatic distribution system further includes a supervision node group, and the supervision node group supports supervision of the blocks on the certificate blockchain.
