CN114499883A - Cross-organization identity authentication method and system based on blockchain and SM9 algorithm - Google Patents

Abstract

The invention discloses a trans-organization identity authentication method and a trans-organization identity authentication system based on a block chain and an SM9 algorithm, belongs to the technical field of digital signatures, and aims to solve the technical problem of how to realize mutual authentication between enterprise key centers for users who sign KGC. Each enterprise organization generates a master key pair through KGC, wherein the master key pair is a signature master key pair used for signature and signature verification and comprises a master public key and a master private key; each enterprise organization privately stores the main private key, uploads and registers the main public key to the alliance chain, and discloses the main public key to other enterprise organizations in the alliance chain; after each enterprise organization receives the signature messages sent by the users of other enterprise organizations in the alliance chain, for other enterprise organizations trusted by the enterprise organizations, the main public keys of the other enterprise organizations are obtained from the alliance chain, and the received signature messages are verified.

Description

Cross-organization identity authentication method and system based on blockchain and SM9 algorithm

technical field

The invention relates to the technical field of digital signatures, in particular to a cross-organization identity authentication method and system based on block chain and SM9 algorithm.

Background technique

Identity-based cryptography is a new branch of public-key cryptography. The identification password algorithm uses the effective identification of the entity (such as email address, mobile phone number, ID code, etc.) as the public key, and users do not need to apply for and exchange certificates, thus greatly reducing the complexity of the system. Identity-based passwords assume the existence of a trusted KGC (Key Generation Center) as the center of the system. When a user joins the system for the first time, the center will generate a private key for the user. The center, also known as a key generation center, acts like a real-life ID card issuer.

The key of the SM9 algorithm is generated by KGC (Key Generation Center), which mainly includes the master key pair of the enterprise KGC and the user's private key. The user private key is generated by the enterprise KGC using the master private key and the user ID. In the SM9 signature/verification process, the enterprise owner public key and user private key are used for signature, and the enterprise owner public key and user ID are used for signature verification.

Because there is no reliance on the certificate, there is no authoritative CA agency to issue the master public key and user ID. The private key of each signer is generated by the KGC of the enterprise to which it belongs, and the signature and verification processes need to rely on the master public key generated by the enterprise KGC. , users between enterprises cannot perform signature verification and identity authentication.

How to realize mutual recognition of users issued by the other party's KGC between enterprise key centers is a technical problem that needs to be solved.

SUMMARY OF THE INVENTION

The technical task of the present invention is to provide a cross-organization identity authentication method and system based on the blockchain and SM9 algorithm to solve the problem of how to realize the mutual recognition of users issued by each other's KGC between enterprise key centers.

In the first aspect, the cross-organization identity authentication method based on the blockchain and the SM9 algorithm of the present invention is characterized by comprising the following steps:

Each enterprise organization generates a master key pair through KGC, and the master key pair is a signature master key pair used for signature and verification, including a master public key and a master private key;

Each enterprise organization keeps its master private key privately, uploads and registers its master public key to the alliance chain, and discloses its master public key to other enterprise organizations in the alliance chain;

After each enterprise organization receives the signed message sent by the user of other enterprise organization in the alliance chain, for other enterprise organization trusted by the enterprise organization, obtain the master public key of the other enterprise organization from the alliance chain, and receive The signed message is verified.

Preferably, after each enterprise organization uploads and registers its master public key to the consortium chain, a trust list is established, and the trust list records the master public keys of other enterprise organizations trusted by the enterprise organization in the consortium chain;

After each enterprise organization receives the signed message sent by the user of other enterprise organization in the alliance chain, if the other enterprise organization is in the trust list, obtains the master public key of the other enterprise organization from the trust list, and signs the received The message is checked.

Preferably, the user's private key is generated by KGC based on the master private key and the user identity, and the signed message is obtained by digitally signing the message to be signed by the user's private key.

More preferably, when the user of other enterprise organization sends the signed message to the enterprise organization, it also sends the master public key corresponding to the enterprise organization, the user ID corresponding to the user, and the to-be-signed message corresponding to the signed message. ;

The enterprise organization takes the master public key, the user ID, the message to be signed, and the signed message as input, obtains the master public key of the other enterprise organization from the alliance chain, and verifies the received signed message to verify user ID.

In the second aspect, the cross-organization identity authentication system based on the blockchain and the SM9 algorithm of the present invention is characterized in that it is used to pass the cross-organization identity authentication method based on the blockchain and the SM9 algorithm according to any one of the first aspects. Authenticating user identities across organizations, the system includes:

Consortium chain, the consortium chain includes multiple enterprise organizations, and each enterprise organization registers to the blockchain through its digital identity to form a consortium chain;

Master key generation module, each enterprise organization generates a master key pair based on KGC through the master key management module, and the master key pair is a signature master key pair used for signature and verification, including the master public key and the master private key;

Master key management module, each enterprise organization privately owns its master private key through the master key management module, and uploads and registers its master public key to the consortium chain through the master key management module, and transfers it to other organizations in the consortium chain. The enterprise organization discloses its master public key;

The signature module, the user of the enterprise organization of the signer obtains the signature message by digitally signing the message to be signed through the signature module, and sends the signature message to other enterprise organizations in the alliance chain;

The signature verification module, after the enterprise organization as the signature verification party receives the signed message, judges whether the enterprise organization as the signature party is trusted through the signature verification module, and if so, obtains the enterprise organization as the signature party from the alliance chain. The corresponding master public key, and verify the signature of the received signed message.

Even better, it also includes:

a trust list building module, each enterprise organization establishes a trust list through the trust list building module, and records the master public keys of other enterprise organizations trusted by the enterprise organization in the alliance chain through the trust list;

The enterprise organization as the signer reads its trust list through the signature verification module, and verifies whether the enterprise organization as the signer is trusted. If the enterprise organization as the signer is in the trust list, obtain the signature from the trust list as a signature The main public key corresponding to the party's enterprise organization is verified, and the received signature message is verified by the signature verification module.

Preferably, the signature module is configured to generate the user's private key through KGC based on the master private key and the user's identity, and obtain the signed message by digitally signing the message to be signed by the user's private key.

Preferably, when the signed message is sent through the signature module, the master public key corresponding to the enterprise organization serving as the signature verification party, the user ID corresponding to the user, and the to-be-signed message corresponding to the signed message are also sent;

The signature verification module is used to take the main public key, the user ID, the message to be signed and the signed message as input, obtain the main public key corresponding to the enterprise organization as the signer from the alliance chain, and verify the signature of the received signed message. , to authenticate the user.

The cross-organization identity authentication method and system based on blockchain and SM9 algorithm of the present invention have the following advantages:

(1) The enterprise organization generates the master key pair through KGC, and registers the master public key on the alliance chain. After receiving the signed message sent by the user of other enterprise organization, for the enterprise organization it trusts, call the master from the alliance chain. The key pair is used to verify the signature of the signed message, thereby realizing cross-combination user identity authentication;

(2) Each enterprise organization is responsible for the master public key uploaded to the blockchain. On the one hand, it can prevent other enterprise organizations that have not been audited by the alliance from maliciously registering their own master public key. The user enterprise organization issued by KGC cannot deny it either;

(3) Each enterprise organization maintains the trust list of the enterprise organizations it trusts on the alliance chain, and only maintains the enterprise organizations that it trusts in its own trust list, and can independently choose which enterprise organizations to trust, ensuring information security, And speed up the verification process.

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only for the present invention. In some embodiments, for those of ordinary skill in the art, other drawings can also be obtained according to these drawings without any creative effort.

The present invention will be further described below with reference to the accompanying drawings.

FIG. 1 is a flowchart of the cross-organization identity authentication method based on the blockchain and the SM9 algorithm in Embodiment 1.

Fig. 2 is the working principle block diagram of digital signature in the cross-organization identity authentication method based on blockchain and SM9 algorithm in Embodiment 1;

3 is a block diagram of the working principle of signature verification in the cross-organization identity authentication method based on the blockchain and SM9 algorithm in Embodiment 1.

Detailed ways

The present invention will be further described below in conjunction with the accompanying drawings and specific embodiments, so that those skilled in the art can better understand the present invention and implement it, but the embodiments are not intended to limit the present invention, and in the case of no conflict Hereinafter, the embodiments of the present invention and the technical features in the embodiments may be combined with each other.

Embodiments of the present invention provide a method and system for cross-organization identity authentication based on blockchain and SM9 algorithm, which are used to solve the technical problem of how to realize mutual recognition between enterprise key centers of users issued by each other's KGC

Example 1:

The cross-organization identity authentication method based on the block chain and the SM9 algorithm of the present invention includes the following steps:

S100. Each enterprise organization generates a master key pair through KGC, and the master key pair is a signature master key pair used for signature and signature verification, including a master public key and a master private key;

S200. Each enterprise organization keeps its master private key privately, uploads and registers its master public key to the alliance chain, and discloses its master public key to other enterprise organizations in the alliance chain;

S300. After each enterprise organization receives the signed message sent by the user of other enterprise organization in the alliance chain, for other enterprise organization trusted by the enterprise organization, obtain the master public key of other enterprise organization from the alliance chain, and sign the received The message is checked.

In this embodiment, the master private key is only used to calculate the user's private key. The user private key is generated by the interaction between the user ID and the master private key. Specifically, the user uses the entity's valid identifier (such as email address, mobile phone number, ID code, etc.) as the user's public key, and the user's private key is signed by the enterprise's KGC (Key Generation Center) using the enterprise's master private key based on the user's use of the entity. issued with a valid ID.

The inputs to the digital signature process are the master public key, the user's private key, and the message to be signed. As shown in Figure 2, suppose the message to be signed is a bit string M, in order to obtain the digital signature (h, S) of the message M, the user A as the signer performs the following operation steps:

A1: Calculate the element g=e(P ₁ , P _pub-s ) in the group _GT ;

A2: Generate random numbers r∈[1,N-1];

A3: Calculate the element w=g ^r in the group _GT , and then convert the data type of w into a bit string;

A4: Calculate the integer h=H ₂ (M||w,N);

A5: Calculate the integer l=(r-h)mod N, if l=0, return to A2;

A6: Calculate the elements in the group G _T

A7: The signature of message M is (h, S).

Among them, M: the original text of the message to be signed;

G _T : group T;

g: an element g in the group T;

P ₁ : generator P1 of group 1;

P _pub-s : signature master public key;

r: a random number in the range of [1,N-1];

N: random number value range;

w: an element w in the group T calculated by g and r;

h: an integer calculated from the original text M of the message to be signed, the element w and the random number range N;

l: an integer obtained by calculating r, h, and N;

签名私钥(用户私钥)；

Signature private key (user private key);

(h, S): digital signature of message M.

When users of other enterprise organizations send signed messages to the enterprise organization, they also send the master public key corresponding to the enterprise organization, the user ID corresponding to the user, and the message to be signed corresponding to the signed message; , the message to be signed and the signed message as input, obtain the master public key of other enterprise organizations from the alliance chain, and verify the signature of the received signed message to verify the identity of the user.

As shown in Figure 3, the input of the digital signature verification process is the master public key, the user ID, the message M and its digital signature M', and the user B as the verifier performs the following signature verification steps:

B1: Check whether h′∈[1,N-1] holds, if not, the verification fails;

B2: Convert the data type of S' to a point on the elliptic curve, and check S'∈G ₁ , if it does not hold, the verification fails;

B3: Calculate the element g=e(P ₁ , P _pub-s ) in the group _GT ;

B4: Calculate the element _t =g ^h′ in the group GT;

B5: Calculate the integer h ₁ =H ₁ (ID _A ||hid,N);

B6: Calculate the element P=[h ₁ ]P ₂ +P _pub-s in the group G ₂ ;

B7: Calculate the element u=e(S′,P) in the group _GT ;

B8: Calculate the element w'=ut in the group _GT , and convert the w' type into a bit string;

B9: h ₂ =H ₂ (M'||w',N), check whether h ₂ =h' holds, and if it holds, the verification is passed.

Among them, M': the digital signature of the message M, namely (h', S');

G _T : group T;

P ₁ : generator P 1 of group ₁ ;

P _pub-s : signature master public key;

g: an element g in the group T;

t: an element t in the group T calculated by g, h';

ID _A : User identity identifier;

hid: User private key type identifier;

N: random number value range;

h ₁ : an integer calculated from ID _A , hid and N;

G ₂ : group 2;

P ₂ : generator P2 of group 2;

u: an element u in the group T;

w': an element w' in the group T calculated by u, t;

h ₂ : an integer calculated from the digital signature M' of the message M, the element w' and the random number range N.

The process of digitally signing a message with the user's private key requires the master public key of the enterprise organization, and the process of verifying the user's digital signature also requires the master public key of the enterprise organization. To verify the digital signature of a user in an enterprise organization, it is only necessary to trust the KGC and obtain the master public key of the enterprise organization from the KGC, and then the digital signature can be independently verified offline, thereby authenticating users in the enterprise organization.

However, for cross-organization user identity authentication, because there is no authoritative organization like CA, it is impossible to trust the master public key published by the KGC of other organizations, so it is impossible to verify the cross-organization digital signature, that is, it is impossible to perform cross-organizational digital signature verification. User authentication for the organization.

In this embodiment, a consortium chain is formed between enterprise organizations, and each enterprise organization creates its own enterprise identity in the consortium chain. The enterprise organization uses its own KGC to generate the master key pair (master public key and master private key) of its own enterprise, and the master private key is independently stored by the enterprise organization and will not be released to the public. The main public key of the enterprise organization is registered on the alliance chain using the digital identity on its own alliance chain, and the main public key is disclosed to all members of the alliance chain. The purpose is to allow other enterprise organizations in the alliance chain to verify the users issued by themselves .

As an improvement, in this embodiment, after each enterprise organization uploads and registers its master public key to the alliance chain, it establishes a trust list, and records the masters of other enterprise organizations trusted by the enterprise organization in the alliance chain through the trust list. After each enterprise organization receives the signed message sent by the user of other enterprise organization in the alliance chain, if the other enterprise organization is in the trust list, it obtains the master public key of the other enterprise organization from the trust list, and signs the received The message is checked.

A large number of enterprise organization participants are registered in the alliance chain, and each enterprise organization participant can publish its own master public key in the alliance chain. All the enterprise organizations that join the alliance chain are subject to the consent of other members of the alliance, and all the master public keys on the blockchain are signed on the chain with the private key of the enterprise organization in the alliance chain. On the one hand, it can prevent other enterprise organizations that have not been audited by the alliance from maliciously registering their own master public key, and ensure that the master public key issued by a trusted enterprise organization; Deny, because the main public key of the enterprise organization on the chain is signed by the identity private key of the enterprise organization on the alliance chain, and the users authenticated by other users using the main public key on the chain are all based on the enterprise organization. trust.

In practice, an enterprise organization may not trust some of the enterprise organizations on the consortium chain, but only choose to trust the enterprise organization that it believes to be credible, maintain a trust list of its own in the consortium chain, and only trust its own trust list. business organization. Users authenticate the identities of other users according to the trust list of their own enterprise organization.

Different enterprise organizations retrieve the enterprise trust list maintained on their own blockchain from the blockchain. For example, if company A includes company B in the trust list on the blockchain, company A can retrieve company B from the blockchain. 's primary public key. When the message signed by the user signed by the B company organization requests the authentication from the A company, the A company can use the B company's master public key retrieved from the trust list on the blockchain for authentication. Because the public key of company B's public key transferred by company A is uploaded to the blockchain by company B using its digital identity on the alliance chain, company A can use it with confidence without worrying about the public key of company B being used by company B. Malicious tampering.

Example 2:

The cross-organization identity authentication system based on the blockchain and SM9 algorithm of the present invention includes a consortium chain, a master key generation module, a master key management module, a signature module and a signature verification module. The alliance chain includes a plurality of enterprise organizations, each All enterprise organizations register to the blockchain through their digital identities to form a consortium chain; each enterprise organization generates a master key pair based on KGC through the master key management module, and the master key pair is used for signature and verification. Signature master key pair, including master public key and master private key; each enterprise organization privatizes its master private key through the master key management module, and uploads and registers its master public key through the master key management module Go to the alliance chain, and disclose its master public key to other enterprise organizations in the alliance chain; the user of the enterprise organization as the signer obtains the signed message by digitally signing the message to be signed through the signature module, and sends the signed message to other organizations in the alliance chain. Enterprise organization; after the enterprise organization as the signer receives the signed message, it judges whether the enterprise organization as the signer is trusted through the signature verification module, and if so, obtains the correspondence of the enterprise organization as the signer from the alliance chain , and verify the received signed message.

In this embodiment, the signature module is configured to generate a user's private key through KGC based on the master private key and the user's identity, and obtain a signed message by digitally signing the message to be signed by the user's private key.

When the signed message is sent through the signature module, the master public key corresponding to the enterprise organization serving as the signature verification party, the user ID corresponding to the user, and the to-be-signed message corresponding to the signed message are also sent. The signature verification module is used to take the main public key, user ID, message to be signed and signed message as input, obtain the main public key corresponding to the enterprise organization as the signer from the alliance chain, and verify the signature of the received signed message to obtain Authenticate the user.

For the digital signature process, let the message to be signed be a bit string M, in order to obtain the digital signature (h, S) of the message M, the user A as the signer performs the following operation steps:

A1: Calculate the element g=e(P ₁ , P _pub-s ) in the group _GT ;

A2: Generate random numbers r∈[1,N-1];

A3: Calculate the element w=g ^r in the group _GT , and then convert the data type of w into a bit string;

A4: Calculate the integer h=H ₂ (M||w,N);

A5: Calculate the integer l=(r-h)mod N, if l=0, return to A2;

A6: Calculate the elements in the group G _T

A7: The signature of message M is (h, S).

For the digital signature verification process, the steps are as follows:

B1: Check whether h′∈[1,N-1] holds, if not, the verification fails;

B2: Convert the data type of S' to a point on the elliptic curve, and check S'∈G ₁ , if it does not hold, the verification fails;

B3: Calculate the element g=e(P ₁ , P _pub-s ) in the group _GT ;

B4: Calculate the element _t =g ^h′ in the group GT;

B5: Calculate the integer h ₁ =H ₁ (ID _A ||hid,N);

B6: Calculate the element P=[h ₁ ]P ₂ +P _pub-s in the group G ₂ ;

B7: Calculate the element u=e(S′,P) in the group _GT ;

B8: Calculate the element w'=ut in the group _GT , and convert the w' type into a bit string;

B9: h ₂ =H ₂ (M'||w',N), check whether h ₂ =h' holds, and if it holds, the verification is passed.

The method disclosed in the embodiments can be executed through the system, and a consortium chain is formed between enterprise organizations, and each enterprise organization creates its own enterprise identity in the consortium chain. The enterprise organization uses its own KGC to generate the master key pair (master public key and master private key) of its own enterprise, and the master private key is independently stored by the enterprise organization and will not be released to the public. The main public key of the enterprise organization is registered on the alliance chain using the digital identity on its own alliance chain, and the main public key is disclosed to all members of the alliance chain. The purpose is to allow other enterprise organizations in the alliance chain to verify the users issued by themselves .

As an improvement of the system in this embodiment, the system further includes a trust list building module, each enterprise organization establishes a trust list through the trust list building module, and records the masters of other enterprise organizations trusted by the enterprise organization in the alliance chain through the trust list. Public key; the enterprise organization as the signer reads its trust list through the signature verification module, and verifies whether the enterprise organization as the signer is trusted, if the enterprise organization as the signer is in the trust list, from the trust list The master public key corresponding to the enterprise organization serving as the signer is obtained, and the received signature message is verified by the signature verification module.

In practice, an enterprise organization may not trust some enterprise organizations on the consortium chain, but only choose to trust the enterprise organization that it believes to be credible, maintain a trust list of its own in the consortium chain, and only trust its own trust list. medium enterprise organization. Users authenticate the identities of other users according to the trust list of their own enterprise organization.

Different enterprise organizations retrieve the enterprise trust list maintained on their own blockchain from the blockchain. For example, if company A includes company B in the trust list on the blockchain, company A can retrieve company B from the blockchain. 's primary public key. When the message signed by the user signed by the B company organization requests the authentication from the A company, the A company can use the B company's master public key retrieved from the trust list on the blockchain for authentication. Because the public key of company B transferred by company A is uploaded to the blockchain by company B using its digital identity on the alliance chain, company A can use it with confidence, without worrying about the public key of company B being used by company B. Malicious tampering.

The present invention is shown and described in detail above through the accompanying drawings and preferred embodiments. However, the present invention is not limited to these disclosed embodiments. Those skilled in the art can know that the above-mentioned different embodiments can be combined based on the above-mentioned multiple embodiments. More embodiments of the present invention can be obtained by the means in the present invention, and these embodiments are also within the protection scope of the present invention.

Claims (8)

1. The cross-organization identity authentication method based on blockchain and SM9 algorithm is characterized by comprising the following steps: Each enterprise organization generates a master key pair through KGC, and the master key pair is a signature master key pair used for signature and verification, including a master public key and a master private key; Each enterprise organization keeps its master private key privately, uploads and registers its master public key to the alliance chain, and discloses its master public key to other enterprise organizations in the alliance chain; After each enterprise organization receives the signed message sent by the user of other enterprise organization in the alliance chain, for other enterprise organization trusted by the enterprise organization, obtain the master public key of the other enterprise organization from the alliance chain, and receive The signed message is verified. 2. The cross-organization identity authentication method based on blockchain and SM9 algorithm according to claim 1, characterized in that after each enterprise organization uploads and registers its master public key to the consortium chain, establishes a trust list, The trust list records the master public keys of other enterprise organizations trusted by the enterprise organization in the alliance chain; After each enterprise organization receives the signed message sent by the user of other enterprise organization in the alliance chain, if the other enterprise organization is in the trust list, obtains the master public key of the other enterprise organization from the trust list, and signs the received The message is checked. 3. the cross-organization identity authentication method based on block chain and SM9 algorithm according to claim 1 and 2, it is characterized in that based on master private key and user identity, generate user private key by KGC, by described user private key If the message to be signed is digitally signed, a signed message is obtained. 4. The cross-organization identity authentication method based on block chain and SM9 algorithm according to claim 3, it is characterized in that when the user of other enterprise organization sends a signed message to the enterprise organization, it also sends the corresponding information of the enterprise organization. the master public key, the user ID corresponding to the user, and the message to be signed corresponding to the signed message; The enterprise organization takes the master public key, the user ID, the message to be signed, and the signed message as input, obtains the master public key of the other enterprise organization from the alliance chain, and verifies the received signed message to verify user ID. 5. The cross-organizational identity authentication system based on blockchain and SM9 algorithm is characterized in that it is used for cross-organizational identity authentication method based on blockchain and SM9 algorithm as described in any one of claims 1-4. The user identity is authenticated, and the system includes: Consortium chain, the consortium chain includes multiple enterprise organizations, and each enterprise organization registers to the blockchain through its digital identity to form a consortium chain; Master key generation module, each enterprise organization generates a master key pair based on KGC through the master key management module, and the master key pair is a signature master key pair used for signature and verification, including the master public key and the master private key; Master key management module, each enterprise organization privately owns its master private key through the master key management module, and uploads and registers its master public key to the consortium chain through the master key management module, and transfers it to other organizations in the consortium chain. The enterprise organization discloses its master public key; The signature module, the user of the enterprise organization as the signer obtains the signature message by digitally signing the message to be signed through the signature module, and sends the signature message to other enterprise organizations in the alliance chain; The signature verification module, after the enterprise organization as the signature verification party receives the signed message, judges whether the enterprise organization as the signature party is trusted through the signature verification module, and if so, obtains the enterprise organization as the signature party from the alliance chain. The corresponding master public key, and verify the received signed message. 6. according to claim 5 based on block chain and the cross-organizational identity authentication system of SM9 algorithm, it is characterized in that also comprising: a trust list building module, each enterprise organization establishes a trust list through the trust list building module, and records the master public keys of other enterprise organizations trusted by the enterprise organization in the alliance chain through the trust list; The enterprise organization as the signer reads its trust list through the signature verification module, and verifies whether the enterprise organization as the signer is trusted. If the enterprise organization as the signer is in the trust list, obtain the signature from the trust list as the signature The main public key corresponding to the party's enterprise organization is verified, and the received signature message is verified by the signature verification module. 7. the cross-organization identity authentication system based on block chain and SM9 algorithm according to claim 5 or 6, it is characterized in that described signature module is used to generate user private key by KGC based on master private key and user identity, A signed message is obtained by digitally signing the message to be signed by the user's private key. 8. The cross-organization identity authentication system based on block chain and SM9 algorithm according to claim 7, is characterized in that while sending the signed message through the signature module, also send the master public key corresponding to the enterprise organization as the signature verification party , the user ID corresponding to the user, and the message to be signed corresponding to the signed message; The signature verification module is used to take the main public key, the user ID, the message to be signed and the signed message as input, obtain the main public key corresponding to the enterprise organization as the signer from the alliance chain, and verify the signature of the received signed message. , to authenticate the user.

Images