Enterprise identity verification method and system and electronic equipment
Through the enterprise identification DID creation and identification resolution system combined with the public key private key management method, the complex problem of dysfunction of anonymity in the blockchain DID method is solved, and the security and efficiency of enterprise identity verification are improved.
Patent Information
- Application Number
- CN202510512248.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-22
- Publication Date
- 2025-08-08
AI Technical Summary
The existing blockchain-based DID method has problems such as difficult to identify anonymity, complex management and high cost in enterprise identity authentication, and poor ID stability, resulting in low efficiency and insufficient security of enterprise identity authentication.
The enterprise identification DID creation step is adopted, and the enterprise identification prefix is used to generate DID document identification, and identity verification is performed through the identification resolution system. Combined with the management of public and private keys, the enterprise independently manages DID documents, avoids centralized identity management, and uses enterprise identification DID and DID documents for two-factor verification.
It improves the security and reliability of enterprise identity verification, simplifies the verification process, reduces management costs, enhances the credibility and stability of enterprise identity, and realizes simple and convenient identity verification.
Smart Images
Figure CN120449138A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of identity authentication technology, and in particular to an enterprise identity authentication method, system and electronic equipment. Background Art
[0002] In application scenarios such as supply chains and product digital passports, there are complex interactive relationships between enterprises. Accessing each other's IT systems requires at least two steps: 1) authorizing the other party to access; 2) verifying the other party's identity and confirming that they are authorized when the other party comes to access.
[0003] When applying a decentralized DID solution to this problem, the accessed party does not need to create an account in advance; instead, the accessing party must verify their identity. Most existing DID methods are based on blockchain, a decentralized system. Blockchain-based DID methods store DID documents on persistent storage, such as the blockchain, and require interaction with the blockchain when used. While blockchain or distributed ledger technology is a mainstream distributed technology, the inherent complexity of blockchain makes DID decentralized methods difficult to popularize and increases the cost of user adoption.
[0004] Furthermore, most blockchain-based DID methods generate IDs by performing various hash operations on public keys and DID documents, such as did:bid:efnVUgqQFfYeu97ABf6sGm3WFtVXHZB2. This form of ID can meet anonymity requirements, but it can be difficult to identify when manually authorizing businesses.
[0005] For example, if company A wants to authorize company B, and the authorization is based on the company name, then when company B uses the DID to apply for verification, proving company B's identity is difficult. Simply using the DID and its documentation is not enough because the DID and its documentation are anonymous. Even if the DID documentation is extended to indicate that it is company B, it is easy to forge and lacks credibility. The solution is to combine a verifiable credential (VC) and a wallet that manages the VC to coordinate the identity verification process. A verifiable credential is a trusted credential issued by an authoritative organization that contains key information such as the company name. If the DID is used for authorization, company A must manage the correspondence between company B and the DID, and company B must notify company A of its DID. This is a manual process and prone to errors due to the anonymity and length of the ID string.
[0006] In addition, many blockchain-based DIDs are obtained by performing various hash operations on public keys and DID documents. Public and private keys are often regenerated due to system migration and other reasons, resulting in ID changes and reduced stability. IDs must also be updated due to reasons such as private key leakage, which leads to many management burdens, just like traditional account and password management methods. Summary of the Invention
[0007] In response to the above problems, the present invention provides an enterprise identity authentication method, system and electronic device to at least solve or alleviate some of the problems existing in the prior art.
[0008] The first aspect of the present invention provides an enterprise identity authentication method, including: an enterprise identification DID creation step, generating a DID document identifier from a DID document containing enterprise identification DID information and registering it to an identification resolution system, generating an identifier for the enterprise identification DID, the enterprise identification DID including an enterprise identification prefix; and an identity authentication step, in response to the enterprise's identity authentication request, the enterprise identity authentication party verifies the enterprise identity based on the enterprise identification DID.
[0009] This approach leverages existing authoritative corporate identifier prefix information to enhance the credibility of corporate identities. Enterprises requesting identity verification can independently manage their DID documents, avoiding the risks associated with centralized identity management. The enterprise authentication provider authenticates the enterprise based on its DID and DID document, enabling simple and convenient authentication.
[0010] Optionally, the enterprise identity DID creation step includes: sending an enterprise identity DID creation request; in response to the enterprise identity creation DID request, the identity DID management system generates a public key and a corresponding private key and saves the private key to a key storage system, and the key management system is only accessible to the enterprise that sends the enterprise identity DID creation request; generating an enterprise identity DID based on the enterprise identity prefix, generating a DID document based on the enterprise identity DID and the public key; and generating a DID document identifier based on the DID document and registering it to the identity enterprise node of the identity resolution system to generate an identifier for the enterprise identity DID.
[0011] Through the above method, the identification DID management system generates public and private keys based on the enterprise identification DID creation request sent by the enterprise. The public key is stored in the DID document that the enterprise can manage independently through the identification enterprise node and can be obtained by the enterprise authentication party. The private key is only visible to the enterprise itself, which enhances the security of the enterprise identification DID.
[0012] Optionally, the identity authentication step includes: a verification request step, carrying the enterprise name and enterprise identification DID and the enterprise name and enterprise identification DID signed by the private key as plain text, requesting the enterprise identity authentication party to verify the enterprise identity; an authorization confirmation step, the enterprise identity authentication party checks whether the enterprise identification DID and / or enterprise name in the plain text are in the authorization list. If not, the authentication fails. If so, the identification resolution step is entered; the identification resolution step, obtaining the DID document based on the enterprise identification DID; a key verification step, verifying whether the enterprise has the private key corresponding to the public key in the DID document. If so, the verification is successful. If not, the verification fails.
[0013] Through this approach, the enterprise authentication provider uses its own authorization list to make a preliminary assessment of the enterprise's authorization status, preventing enterprises not on the authorization list from being successfully authenticated. After authorization verification is successful, the enterprise authentication provider conducts a secondary verification of the enterprise's possession of the private key. This verification uses the public key in the DID document to verify the enterprise's signature. This avoids reliance on the blockchain and utilizes only identity resolution to achieve a simple and fast verification method, thereby improving verification efficiency. This dual verification confirms the enterprise's authorization status and identity, enhancing the security and reliability of enterprise authentication. Furthermore, the enterprise uses its own stored private key to sign the plaintext, further enhancing the security and credibility of the signature and further improving the security of authentication.
[0014] Optionally, the identification resolution step includes: obtaining a DID document identification ID based on the enterprise identification DID; using the DID document identification ID to resolve the DID document identification in an identification resolution system; and converting the DID document identification into a DID document.
[0015] Through the above method, the enterprise's identity verification party can obtain the enterprise's DID document by resolving the DID document ID corresponding to the enterprise's DID through the identity resolution system, fully leveraging the authority and convenience of the identity resolution system. At the same time, when the enterprise updates the DID document, the DID document ID of the DID document remains unchanged, facilitating the enterprise's independent management and updates.
[0016] Optionally, the enterprise identity authentication method further includes: an authorization identification step, in which the enterprise identity authentication party authorizes the enterprise identity based on the enterprise identifier DID or the enterprise name.
[0017] Through the above methods, the enterprise identity verification party uses multiple methods to authorize the enterprise, improves the flexibility of authorization, and improves the credibility and security of authorization through the enterprise's identity DID authorization.
[0018] Optionally, if the enterprise identity authentication party authorizes the enterprise identity based on the enterprise name, it also includes: an enterprise name verification step, resolving the identifier corresponding to the enterprise identifier prefix through the identifier resolution system, and verifying whether the enterprise name is consistent with the enterprise name in the identifier. If not, the authentication fails. If so, the identity authentication step continues.
[0019] A second aspect of the present invention provides an enterprise identity verification system, comprising:
[0020] The DID management system is used to initiate enterprise DID creation requests;
[0021] The DID controller is used to generate the enterprise identification DID, generate a DID document identifier from the DID document containing the enterprise identification DID information and register it with the identification resolution system, generate an identifier for the enterprise identification DID, use the enterprise's private key to generate a signature for the enterprise identification DID and the enterprise name, and return the signature to the enterprise. The enterprise identification DID includes the enterprise identification prefix;
[0022] The DID authentication server is used to receive the enterprise identity DID and signature sent by the enterprise identity verification party, and verify whether the enterprise has the private key corresponding to the public key in the DID document. If so, the verification is successful; otherwise, the verification fails.
[0023] An identifier DID resolver, configured to obtain a DID document identifier address ID based on the enterprise identifier DID, send a resolution request to an identifier resolution system using the DID document identifier ID, and convert the received DID document identifier into a DID document; and
[0024] The identification resolution system is used to respond to the resolution request, resolve the DID document identification according to the received DID document identification ID and return it to the identification DID resolver.
[0025] Through the above methods, the various modules of the enterprise identity authentication system are utilized to improve the security and reliability of enterprise identity authentication for enterprises, and the verification efficiency is improved through the enterprise identity DID.
[0026] A third aspect of the present invention provides an electronic device, wherein the electronic device stores a computer program, and when the computer program is executed by a processor of the electronic device, the above-mentioned enterprise identity authentication method is implemented. BRIEF DESCRIPTION OF THE DRAWINGS
[0027] Figure 1 Flowchart of the enterprise identity authentication method in an embodiment of the present invention.
[0028] Figure 2 This is another flow chart of the enterprise identity verification method in an embodiment of the present invention.
[0029] Figure 3 Flowchart of steps for creating a corporate identity DID in an embodiment of the present invention.
[0030] Figure 4 Flowchart of the identity authentication steps in an embodiment of the present invention.
[0031] Figure 5 Schematic diagram of an enterprise identity authentication system in an embodiment of the present invention. DETAILED DESCRIPTION
[0032] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.
[0033] <First embodiment>
[0034] Figure 1 Flowchart of the enterprise identity verification method in the embodiment of the present invention. Figure 1 The first embodiment of the present invention provides an enterprise identity authentication method, including an enterprise identification DID creation step S1 and an identity authentication step S2.
[0035] In the enterprise identification DID creation step S1, the enterprise identification DID is generated according to the enterprise identification prefix, and the DID document identification is generated and registered in the identification resolution system.
[0036] In the identity authentication step S2, in response to the enterprise's identity authentication request, the enterprise identity authentication party verifies the enterprise identity based on the enterprise identifier DID.
[0037] Through this approach, the company's corporate identifier prefix is a unique identifier issued by a higher-level naming authority. This authoritative prefix enhances the credibility of the company's identity. Companies submitting identity verification requests can independently manage their DID documents, eliminating the risks associated with centralized identity management by the company's identity verification provider. The company's identity verification provider authenticates the company based on its DID and DID document, making authentication simple and convenient.
[0038] <Second embodiment>
[0039] Figure 2 This is another flow chart of the enterprise identity verification method in an embodiment of the present invention. Figure 3 This is a flowchart of the enterprise identity DID creation step S01 in the embodiment of the present invention. Figure 2The second embodiment of the present invention provides an enterprise identity authentication method, including an enterprise identification DID creation step S01, an authorization identification step S02 and an identity authentication step S03.
[0040] In the enterprise identification DID creation step S01, the DID document containing the enterprise identification DID information is generated into a DID document identifier and registered in the identity resolution system. Figure 3 After obtaining its own enterprise identifier prefix, the enterprise sends a creation request to the identifier DID controller through the identifier DID management system. The identifier DID controller generates a public key and a corresponding private key. The private key is stored in the enterprise's own key management system. The public key, together with the enterprise identifier DID, generates a DID document and converts it into an identifier format, namely a DID document identifier. This is then registered as the identifier of the enterprise identifier DID through the identifier enterprise node of the identifier resolution system.
[0041] For example, the corporate identifier prefix of a certain enterprise is A. The enterprise identifier DID creation step S01 is applied to register the DID document identifier converted into the identifier format to the identifier enterprise node. The identifier ID is A / did. At the same time, the enterprise identifier DID can be expressed as: did:handle:A, where handle is a placeholder used to represent a specific DID method. The DID document identifier ID of the enterprise can be queried through the identifier resolution system as: A / did.
[0042] Among them, the identity resolution system defines a layered service model. The top layer consists of a single identity service, namely the Global Handle Registry (GHR). The bottom layer consists of all other identity services, generally referred to as Local Handle Services (LHS). The Global Identity Registry can be used to manage any identity namespace. It provides services for managing naming authorities, and all naming authorities are managed as identities. The information provided by the naming authority identity can be used by clients to access and use the local identity service identified under the naming authority. The local identity service is intended to be hosted by an organization that has management responsibility for the identities under a specific naming authority. A local identity service may be responsible for any number of local identity namespaces, each of which is identified by a unique naming authority. The local identity service and the set of local identity namespaces it is responsible for must be registered with the Global Identity Registry.
[0043] A key feature of the identity resolution system is its distributed architecture. For example, the identity resolution system corresponding to the identifier 88.328.807 provides local identification services (i.e., the identity enterprise node), which is managed by the higher-level authority 88.328 (a secondary node). 88.328.807 is also an identified enterprise, corresponding one-to-one with the enterprise, and is therefore also called the identity enterprise prefix. The identity resolution system can resolve the identity enterprise prefix and access the corresponding identity enterprise node.
[0044] Figure 4 Flowchart of the identity verification step S03 in the embodiment of the present invention. Figure 4 In this embodiment, the identity resolution system including the top-level node, the second-level node and the enterprise node is used as an example for explanation.
[0045] The enterprise identifier prefix is a unique identifier issued by the company's superior naming authority. This prefix corresponds to the company name and serves as the company's unique identity within the identity resolution system. The enterprise identifier node within the identity resolution system can be managed by the enterprise itself.
[0046] When the public key and private key need to be updated, only the DID document content needs to be updated, and the enterprise identifier DID and DID document identifier ID remain unchanged.
[0047] Through the above method, the DID management system generates public and private keys based on the enterprise's DID creation request S01. The public key is stored in the DID document identifier, which the enterprise can manage independently through the identity resolution system's enterprise node and can be obtained by the enterprise's authentication party. The private key is visible only to the enterprise itself, enhancing the security of the enterprise DID. Furthermore, the enterprise's public and private keys can be updated without affecting the DID document identifier ID or the enterprise DID, increasing the flexibility of the enterprise identifier in use.
[0048] In the authorization identification step S02, the enterprise identity verification party uses the enterprise identifier DID or the enterprise name to authorize the corresponding enterprise identity. For example, the enterprise identifier prefix that constitutes the enterprise identifier DID can be obtained through the enterprise's website, employee business cards, product nameplates, emails, phone calls, etc., and can be verified by querying the national top-level node (https: / / dms.idfactory.cn / ).
[0049] Through the above methods, the enterprise identity verification party uses multiple methods to authorize the enterprise, improves the flexibility of authorization, and improves the credibility and security of authorization through enterprise identification DID authorization.
[0050] If the enterprise identity authentication party authorizes the enterprise identity based on the enterprise name, the enterprise identity authentication method also includes: an enterprise name verification step, in which the DID authentication server reads the identifier corresponding to the enterprise identifier prefix, and verifies whether the enterprise name in the plain text is consistent with the enterprise name in the resolved identifier. If not, the authentication fails. If so, the identity authentication step S03 is continued.
[0051] It should be noted that the process of the DID authentication server resolving the enterprise identification prefix in the enterprise name verification step is consistent with the process of the identification resolution step in the following identity verification step S03. For details, please refer to the identification resolution step in the following identity verification step S03.
[0052] Figure 5 Schematic diagram of an enterprise identity verification system according to an embodiment of the present invention. Figure 4 and Figure 5 In the identity verification step S03, in response to the enterprise (such as Figure 5 The authentication request of the consumer business system) of the enterprise authentication party (such as Figure 5 The service provider business system) verifies the enterprise identity based on the enterprise's identity DID.
[0053] Specifically, the identity verification step S03 includes:
[0054] Verification request step, carrying the enterprise name and enterprise identity DID as well as the enterprise name and enterprise identity DID signed by the private key as plain text, requesting the enterprise identity verification party to verify the enterprise identity;
[0055] In the authorization confirmation step, the enterprise identity verification party checks whether the enterprise identifier DID and / or enterprise name in the plain text is in the authorization list. If not, the authentication fails. If so, the process proceeds to the identification resolution step.
[0056] Parsing identification step, obtaining DID document based on enterprise identity DID;
[0057] The key verification step verifies whether the enterprise has the private key corresponding to the public key in the DID document. If so, the verification succeeds; otherwise, the verification fails.
[0058] Through the above method, the enterprise authentication provider uses its own authorization list to make a preliminary assessment of the enterprise's authorization status, preventing enterprises not on the authorization list from being successfully authenticated. After authorization verification is successful, the enterprise authentication provider then conducts a secondary verification of whether the enterprise possesses the private key. This is done by verifying the enterprise's signature using the public key in the DID document. This avoids reliance on the blockchain and uses parsing to achieve a simple and fast verification method, thereby improving verification efficiency.
[0059] This double verification confirms the company's authorization and identity, improving the security and reliability of the company's identity verification. At the same time, the company uses its own stored private key to sign the plaintext, improving the security and credibility of the signature and further enhancing the security of identity verification.
[0060] In the identification resolution step, a DID document identification ID is obtained based on the enterprise identification DID; the DID document identification ID is used to resolve the DID document identification in an identification resolution system; and the DID document identification is converted into a DID document.
[0061] For example, if the enterprise identity DID is represented as did:handle: <prefix>,in, <prefix>It is the enterprise identification prefix of the enterprise. The process for enterprise identity verification using the identity resolution system and the identity DID resolver to resolve it is as follows:
[0062] (1) The DID document ID corresponding to the enterprise ID DID is constructed as follows: <prefix> / did;
[0063] (2) Use the identity resolution system to resolve the DID document identity ID, obtain the DID document identity and return it to the identity DID resolver;
[0064] (3) Convert the DID document identifier into a standard DID document format (such as JSON-LD) through the DID resolver;
[0065] (4) Check the content of the DID document, including checking the enterprise identifier prefix in the enterprise identifier DID (i.e. <prefix>), public key, etc.
[0066] (5) Return the enterprise’s DID document to the DID authentication server.
[0067] Through the above method, the enterprise authentication party can resolve the enterprise identity DID through the identity resolution system to obtain the corresponding DID document identification ID, and then obtain the enterprise's DID document based on the DID document identification ID. At the same time, when the enterprise updates the DID document, the corresponding DID document identification ID does not change, which facilitates the enterprise's independent management and updates.
[0068] <Third embodiment>
[0069] refer to Figure 4 and Figure 5 The third embodiment of the present invention provides an enterprise identity authentication system, including an identification DID management system, an identification DID controller, an identification DID authentication server, an identification DID resolver and an identification resolution system. The enterprise identity authentication party can verify the identity of the enterprise through the enterprise identity authentication system.
[0070] The identification DID management system is connected to the identification DID controller. The enterprise can initiate a request to create an enterprise identification DID to the identification DID controller based on the identification DID management system. The identification DID controller generates a public key-private key pair in response to the request, where the private key is stored in the enterprise's own key management system. The public key is combined with the enterprise identification DID to generate a DID document and converted into an identification format to generate a DID document identifier. The DID document identifier is registered with the identification enterprise node of the identification resolution system to generate the identification of the enterprise identification DID, and the enterprise's DID document identifier can be queried from the identification resolution system based on a fixed ID.
[0071] Continue to refer Figure 5 The enterprise (hereinafter referred to as the service consumer business system) sends a signature request to the identification DID controller. The identification DID controller uses the enterprise's private key to sign the enterprise identification DID and enterprise name in plain text and returns the signature to the enterprise.
[0072] The enterprise carries this plaintext and signature to request authentication from the enterprise identity verification party (hereinafter also referred to as the service provider business system). The enterprise identity verification party checks whether the enterprise name or enterprise identifier DID in the plaintext is in its own authorization list. If not, the authentication fails. If so, it proceeds to the next authentication step.
[0073] Specifically, if the enterprise identity verification party uses the enterprise name to authorize the enterprise, it is necessary to check whether the enterprise name in the plain text is in its own authorization list. If they are consistent, continue; otherwise, the authentication fails; if the enterprise identity verification party uses the enterprise identifier DID to authorize the enterprise, go directly to the next verification step to verify that the enterprise owns the private key corresponding to the public key in the declared DID document.
[0074] If the enterprise identifier DID or enterprise name is in its own authorization list, the enterprise identity authentication party carries the enterprise identifier DID and the signature request identifier DID authentication server for authentication. The identifier DID authentication server sends a request to the identifier DID resolver based on the request to query the DID document corresponding to the enterprise identifier DID. The identifier DID resolver responds to the query request and sends an enterprise identifier DID resolution request to the identifier resolution system. The identifier resolution system responds to the request and can send the corresponding identifier format DID document to the identifier DID resolver based on the enterprise identifier DID. The identifier DID resolver parses the identifier format DID document into a DID document and sends it to the identifier DID authentication server.
[0075] The enterprise's signature is verified based on the public key in the DID document. If the signature verification fails, the authentication fails. If the signature verification succeeds, the enterprise identity authentication is successful and the session key can be sent.
[0076] In addition, under the additional condition that the enterprise name needs to be verified to confirm the success of the authentication, the authentication process mentioned above also includes: the identification DID authentication server intercepts the enterprise identification prefix from the enterprise identification DID and initiates an enterprise identification prefix query request to the identification resolution system. The identification resolution system provides the resolution result of the enterprise identification DID. The identification DID authentication server checks whether the enterprise name in the resolution result matches the enterprise name declared in plain text. If it matches, it returns an authentication success message, otherwise it returns an authentication failure message.
[0077] Continue to refer Figure 5 When the result of identity verification step S03 is a successful authentication, the DID authentication server sends a session key to the enterprise. Specifically, if the result of identity verification step S03 for the enterprise is a successful authentication, the DID authentication server sends the session key to the enterprise, enabling a conversation between the enterprise's identity verification party and the enterprise. If the authentication is unsuccessful, the conversation between the enterprise's identity verification party and the enterprise is blocked. This configuration improves the security and reliability of subsequent conversations between the enterprise's identity verification party and the enterprise.
[0078] Through the above method, the enterprise identifier prefix is authoritatively created by a secondary node in the identity resolution system and is therefore authoritative. The DID document within the enterprise identifier DID is created and managed independently by the enterprise itself, demonstrating its distributed nature. The enterprise identifier DID and DID document combine authoritative identification with distributed identity. This solves the difficulty of memorizing and recognizing anonymized DID identities, while also enabling autonomous management while ensuring identity authority (other enterprises can verify the authenticity of the identity through authoritative channels). This means that enterprises can replace DID documents at any time, avoiding the risks of centralized identity management.
[0079] Enterprise identity verification methods based on DIDs rely solely on identity resolution systems, independent of blockchain, verifiable credentials, or wallets. This makes implementation simple, fast, and low-cost. Furthermore, DID-based enterprise identity verification methods can fully leverage existing identity resolution systems, applying them to new authentication scenarios and further enhancing the value of identity resolution systems.
[0080] <Fourth embodiment>
[0081] A fourth embodiment of the present invention provides an electronic device having a computer program stored therein. When the computer program is executed by a processor of the electronic device, the enterprise identity authentication method described above is implemented to improve the security and reliability of identity authentication.
[0082] The above are only preferred embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.< / prefix> < / prefix> < / prefix> < / prefix>
Claims
1. An enterprise identity verification method, characterized in that: Including steps: A DID creation step is to generate a DID document identifier from a DID document containing DID information and register it with an identifier resolution system to generate an identifier for the DID, wherein the DID includes an enterprise identifier prefix. as well as In the identity authentication step, in response to the enterprise's identity authentication request, the enterprise identity authentication party verifies the enterprise identity based on the enterprise identifier DID.
2. The enterprise identity verification method according to claim 1, characterized in that: The steps of creating the enterprise identity DID include: Send a request to create a corporate identity DID; In response to the enterprise identity DID creation request, the identity DID management system generates a public key and a corresponding private key and saves the private key to a key management system, where the key management system is accessible only to the enterprise that sent the enterprise identity DID creation request; Generate the enterprise identifier DID based on the enterprise identifier prefix, and generate a DID document based on the enterprise identifier DID and the public key; and A DID document identifier is generated based on the DID document and registered with the identifier enterprise node of the identifier resolution system to generate an identifier of the enterprise identifier DID.
3. The enterprise identity verification method according to claim 2, characterized in that: The identity verification steps include: Verification request step, carrying the enterprise name and the enterprise identifier DID as well as the enterprise name and enterprise identifier DID signed by the private key as plain text, requesting the enterprise identity verification party to verify the enterprise identity; In the authorization confirmation step, the enterprise identity verification party checks whether the enterprise identifier DID and / or the enterprise name in the plain text are in the authorization list. If not, the authentication fails. If so, the authentication proceeds to the identification resolution step; An identification parsing step, obtaining the DID document based on the enterprise identifier DID; The key verification step verifies whether the enterprise possesses the private key corresponding to the public key in the DID document. If so, the verification succeeds; otherwise, the verification fails.
4. The enterprise identity verification method according to claim 3, characterized in that: The identification parsing step includes: Obtaining a DID document identification ID based on the enterprise identification DID; Resolving the DID document identifier in the identifier resolution system using the DID document identifier ID; and The DID document identifier is converted into a DID document.
5. The enterprise identity verification method according to any one of claims 1 to 4, characterized in that: Also includes: In the authorization identification step, the enterprise identity verification party authorizes the enterprise identity based on the enterprise identifier DID or enterprise name.
6. The enterprise identity verification method according to claim 5, characterized in that: If the enterprise identity verification party authorizes the enterprise identity based on the enterprise name, it also includes: The enterprise name verification step is to parse the identifier corresponding to the enterprise identifier prefix through the identifier resolution system to verify whether the enterprise name is consistent with the enterprise name in the identifier. If not, the authentication fails. If so, the identity verification step continues.
7. An enterprise identity verification system, characterized in that: include: The DID management system is used to initiate enterprise DID creation requests; An identification DID controller is used to generate an enterprise identification DID, generate a DID document identifier from a DID document containing the enterprise identification DID information and register it with the identification resolution system, generate an identifier for the enterprise identification DID, generate a signature for the enterprise identification DID and the enterprise name using the enterprise's private key, and return the signature to the enterprise, where the enterprise identification DID includes the enterprise identification prefix; The DID authentication server is configured to receive the enterprise identifier DID and the signature sent by the enterprise identity verification party, and verify whether the enterprise possesses the private key corresponding to the public key in the DID document. If so, the verification succeeds; otherwise, the verification fails. An identifier DID resolver, configured to obtain the DID document identifier ID based on the enterprise identifier DID, send a resolution request to the identifier resolution system using the DID document identifier ID, and convert the received DID document identifier into a DID document; as well as The identification resolution system is used to respond to the resolution request, resolve the DID document identification according to the received DID document identification ID and return it to the identification DID resolver.
8. An electronic device, characterized in that: The electronic device stores a computer program, and when the computer program is executed by the processor of the electronic device, it implements the enterprise identity authentication method according to any one of claims 1 to 6.