A cross-domain identity authentication method and related device based on distributed ledger
Through distributed ledger technology, the single point of failure and trust problems in the existing technology are solved, the reliability and security of identity authentication are improved, and the credibility and security of cross-domain identity authentication are realized. .
Patent Information
- Application Number
- CN202411216360.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-02
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2044-09-02
AI Technical Summary
There are single point of failure and trust problems in existing cross-domain identity authentication. The invalidity of the authentication agency leads to the inability to verify the identity, lack of consideration of user behavior information, and it is prone to information tampering and token leakage, which affects security, and lacks identity credibility. Evaluate.
Using a cross-domain identity authentication method based on distributed ledgers, a cross-domain distributed identity identifier is generated by authenticating blockchain nodes, a joint signature identity certificate is generated using the certificate model, an identity token is generated and information tampering is performed, and a distributed verification consensus is combined with The algorithm performs cross-domain verification and performs identity credibility assessment, and finally generates identity credibility proof to judge user identity authentication and allocate permissions.
Avoid single point of failure, improve the reliability and security of identity authentication, reduce the risk of information leakage, and ensure the credibility and security of cross-domain identity authentication through distributed ledgers, achieving more ideal authentication results.
Smart Images

Figure CN118764215B_ABST
Abstract
Description
Technical Field
[0001] The present invention mainly relates to the field of identity authentication technology, and in particular to a cross-domain identity authentication method and related devices based on a distributed ledger. Background Art
[0002] At present, the cross-business departments of each enterprise have established identity authentication systems according to their own businesses. Since the identity authentication systems are independent of each other, cross-domain identity authentication is required to realize the access of different systems. However, in the existing cross-domain identity authentication, the identity certificate is usually determined by a single authentication agency. If the authentication agency fails, the user identity cannot be verified. At the same time, there is a lack of consideration of user behavior information, which makes the reliability of the final determined identity certificate low. At the same time, for the determination of cross-domain identity credentials, after simply verifying the identity token, the cross-domain identity credential is issued, resulting in a greater risk of identity authentication, which is prone to information tampering and token leakage, seriously affecting the security of cross-domain identity authentication. In addition, in the current cross-domain identity authentication, the evaluation of identity credibility is rarely considered. Usually, after the identity credential verification is passed, the user's identity authentication and authority allocation are directly passed, which cannot guarantee the security of cross-domain identity authentication, which is prone to information leakage and makes cross-domain identity authentication unable to achieve the expected effect. Summary of the invention
[0003] The purpose of the present invention is to overcome the shortcomings of the prior art. The present invention provides a cross-domain identity authentication method and related devices based on a distributed ledger. The distributed ledger can avoid single point failures and trust issues, so that cross-domain identity authentication can achieve a more ideal effect.
[0004] In order to solve the above technical problems, the present invention provides a cross-domain identity authentication method based on a distributed ledger, the method comprising:
[0005] Receiving a cross-domain registration request sent by a user based on an authentication blockchain node, generating a cross-domain distributed identity based on the cross-domain registration request, and generating a joint signature identity certificate based on the cross-domain distributed identity using a certificate model;
[0006] Sending the jointly signed identity certificate to a first distributed notary node, wherein the first distributed notary node generates an identity token based on the jointly signed identity certificate;
[0007] Sending the identity token to a second distributed notary node, which generates a cross-domain identity credential based on the identity token and the information tampering check result, and writes the cross-domain identity credential into a distributed cross-domain identity ledger;
[0008] The distributed cross-domain identity ledger performs cross-domain verification based on the cross-domain identity credential to obtain a cross-domain verification result;
[0009] Performing an identity credibility assessment based on the cross-domain identity credential to obtain an identity credibility assessment result, and generating an identity credibility certificate based on the identity credibility assessment result and the cross-domain verification result;
[0010] Based on the identity trustworthy proof, it is determined whether the user has passed the cross-domain identity authentication. If it is determined that the user has passed the cross-domain identity authentication, permissions are assigned to the user, and the judgment result of the cross-domain identity authentication, the identity trustworthy proof, and the permissions assigned to the user are written into the distributed cross-domain identity ledger.
[0011] Optionally, the generating a cross-domain distributed identity based on the cross-domain registration request, and generating a joint signature identity certificate based on the cross-domain distributed identity using a certificate model, includes:
[0012] Parsing the cross-domain registration request to obtain a cross-domain distributed identity;
[0013] Generate a certificate signing request based on the cross-domain distributed identity combined with the certificate identifier, and perform public key authentication with several certification authorities based on the certificate signing request to obtain several public key authentication results;
[0014] Generate a corresponding sub-signature certificate using a sub-signature generation algorithm based on the multiple public key authentication results;
[0015] Generate a user behavior feature vector based on the cross-domain registration request using a certificate model, and generate a user behavior certificate based on the user behavior feature vector;
[0016] All sub-signature certificates, cross-domain distributed identities and user behavior certificates are generated into a hash value with a fixed bit length using a hash algorithm, and asymmetric encryption is performed based on the hash value with a fixed bit length to obtain a joint signature identity certificate.
[0017] Optionally, the first distributed notary node generates an identity token based on the joint signature identity certificate, including:
[0018] The first distributed notary node generates a certificate verification request based on the joint signature identity certificate, and sends the certificate verification request to the certificate verification node;
[0019] The certificate verification node performs valid signature certificate authentication on the joint signature identity certificate based on the certificate verification request to obtain a valid signature certificate authentication result;
[0020] Based on the valid signature certificate authentication result, an identity token is generated by utilizing a preset security authentication mechanism in combination with cookie information verification.
[0021] Optionally, the generating a cross-domain identity credential based on the identity token in combination with the information tampering check result includes:
[0022] generating a result signature based on the identity token, and generating an initial identity credential based on the result signature and the identity token;
[0023] Performing byte stream conversion on the initial identity credential based on the ObjectOutputStream sequence to obtain the initial identity credential after byte stream conversion;
[0024] Based on ObjectInputStream deserialization, the initial identity credential after the byte stream conversion is converted into the original object, and the original object is checked for information tampering to obtain the information tampering check result;
[0025] A cross-domain identity credential is generated based on the information tampering check result, the initial identity credential and the result signature.
[0026] Optionally, the distributed cross-domain identity ledger performs cross-domain verification based on the cross-domain identity credential to obtain a cross-domain verification result, including:
[0027] The distributed cross-domain identity ledger verifies the cross-domain identity credential based on the cross-domain identity credential definition to obtain a verification result;
[0028] Based on the distributed verification consensus algorithm, the cross-domain identity credential is used to perform a cross-domain request review to obtain a cross-domain request review result;
[0029] Based on the signature verification result and the cross-domain request review result, cross-domain verification is performed to obtain a cross-domain verification result.
[0030] Optionally, performing identity credibility assessment based on the cross-domain identity credential to obtain an identity credibility assessment result, and generating an identity credibility certificate based on the identity credibility assessment result and the cross-domain verification result includes:
[0031] Sending a trusted authentication request to a trusted evaluation node, and obtaining a trusted measurement request parameter list, a timestamp, and an identity credibility evaluation standard based on the trusted authentication request;
[0032] Generate a homomorphically encrypted public-private key pair based on the cross-domain identity credential, perform identity credibility evaluation using the homomorphically encrypted public-private key pair based on the trusted metric request parameter list, timestamp, and identity credibility evaluation criteria, and obtain an identity credibility evaluation result;
[0033] Obtaining historical user identity credibility assessment records based on the distributed cross-domain identity ledger;
[0034] An identity credibility certificate is generated based on the historical user identity credibility evaluation record, the identity credibility evaluation result and the cross-domain verification result.
[0035] Optionally, judging whether the user has passed the cross-domain identity authentication based on the identity trustworthy proof, and if it is judged that the user has passed the cross-domain identity authentication, assigning permissions to the user, and writing the judgment result of the cross-domain identity authentication, the identity trustworthy proof, and the permissions assigned to the user into the distributed cross-domain identity ledger, includes:
[0036] Obtaining a definition of a trusted identity certificate, verifying the trusted identity certificate based on the definition of the trusted identity certificate, and obtaining a verification result;
[0037] Performing validity judgment on the identity credibility certificate to obtain a validity judgment result;
[0038] Determine whether the user has passed the cross-domain identity authentication based on the signature verification result and the validity period judgment result;
[0039] If it is determined that the user has passed the cross-domain identity authentication, permissions are assigned to the user, and the judgment result of the cross-domain identity authentication, the identity trustworthiness certificate and the permissions assigned to the user are composed of a compact storage structure based on the Merkle tree, and the compact storage structure based on the Merkle tree is written into the distributed cross-domain identity ledger.
[0040] In addition, the present invention also provides a cross-domain identity authentication device based on a distributed ledger, the device comprising:
[0041] A joint signature identity certificate generation module: used to receive a cross-domain registration request sent by a user based on an authentication blockchain node, generate a cross-domain distributed identity based on the cross-domain registration request, and generate a joint signature identity certificate based on the cross-domain distributed identity using a certificate model;
[0042] An identity token generation module is used to send the joint signature identity certificate to a first distributed notary node, and the first distributed notary node generates an identity token based on the joint signature identity certificate;
[0043] A cross-domain identity credential generation module: used to send the identity token to a second distributed notary node, which generates a cross-domain identity credential based on the identity token and the information tampering check result, and writes the cross-domain identity credential into a distributed cross-domain identity ledger;
[0044] Cross-domain verification module: used for the distributed cross-domain identity ledger to perform cross-domain verification based on the cross-domain identity credential to obtain a cross-domain verification result;
[0045] Identity credibility proof module: used to perform identity credibility assessment based on the cross-domain identity credential, obtain identity credibility assessment result, and generate identity credibility proof based on the identity credibility assessment result and the cross-domain verification result;
[0046] Cross-domain identity authentication module: used to determine whether the user has passed the cross-domain identity authentication based on the identity trust certificate. If it is determined that the user has passed the cross-domain identity authentication, permissions are assigned to the user, and the judgment result of the cross-domain identity authentication, the identity trust certificate and the permissions assigned to the user are written into the distributed cross-domain identity ledger.
[0047] In addition, the present invention also provides an electronic device, which includes a processor and a memory, the memory is used to store instructions, and the processor is used to call the instructions in the memory, so that the electronic device executes the above-mentioned cross-domain identity authentication method based on a distributed ledger.
[0048] In addition, the present invention also provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the above-mentioned cross-domain identity authentication method based on a distributed ledger.
[0049] In an embodiment of the present invention, a joint signature identity certificate is generated based on all sub-signature certificates, cross-domain distributed identity identifiers and user behavior certificates generated from several public key authentication results obtained by performing public key authentication on several certification authorities through a certificate signing request. Sub-signature certificates are generated through multiple certification authorities to avoid the failure of a single certification authority to verify the user's identity. At the same time, a user behavior certificate is added to improve the credibility of the obtained joint signature identity certificate. A cross-domain identity credential is generated based on an identity token combined with an information tampering check result to avoid information tampering and leakage of the identity token, improve the security of the cross-domain identity credential, and enable the obtained cross-domain identity credential to carry more resources and resource domains through deserialization processing. An identity credibility assessment is performed based on the cross-domain identity credential to generate an identity credibility certificate, and the user's identity risk assessment is achieved without increasing the network communication load, which can effectively ensure the reliability of user identity authentication and greatly reduce the threat of out-of-domain attacks. The judgment results of cross-domain identity authentication, identity credibility proof and the permissions assigned to users are composed of a compact storage structure based on the Merkle tree and written into a distributed cross-domain identity ledger. The distributed ledger can avoid single point failures and trust issues, making cross-domain identity authentication achieve a more ideal effect. BRIEF DESCRIPTION OF THE DRAWINGS
[0050] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0051] Figure 1 It is a schematic diagram of a cross-domain identity authentication method based on a distributed ledger in an embodiment of the present invention;
[0052] Figure 2 Schematic diagram of the structure of a cross-domain identity authentication device based on a distributed ledger in an embodiment of the present invention;
[0053] Figure 3 It is a schematic diagram of the structure of an electronic device in an embodiment of the present invention. DETAILED DESCRIPTION
[0054] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. 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 creative work are within the scope of protection of the present invention.
[0055] Embodiment 1
[0056] See also Figure 1 , Figure 1 It is a flow chart of a cross-domain identity authentication method based on a distributed ledger in an embodiment of the present invention.
[0057] like Figure 1 As shown, a cross-domain identity authentication method based on a distributed ledger comprises:
[0058] S11: receiving a cross-domain registration request sent by a user based on an authentication blockchain node, generating a cross-domain distributed identity based on the cross-domain registration request, and generating a joint signature identity certificate based on the cross-domain distributed identity using a certificate model;
[0059] In the specific implementation process of the present invention, a cross-domain distributed identity is generated based on the cross-domain registration request, and a joint signature identity certificate is generated based on the cross-domain distributed identity using a certificate model, including: parsing the cross-domain registration request to obtain a cross-domain distributed identity; generating a certificate signing request based on the cross-domain distributed identity combined with a certificate identifier, and performing public key authentication on several certification authorities based on the certificate signing request to obtain several public key authentication results; generating a corresponding sub-signature certificate based on the several public key authentication results using a sub-signature generation algorithm; generating a user behavior feature vector based on the cross-domain registration request using a certificate model, and generating a user behavior certificate based on the user behavior feature vector; generating a hash value with a fixed bit length for all sub-signature certificates, cross-domain distributed identity and user behavior certificates using a hash algorithm, and performing asymmetric encryption based on the hash value with a fixed bit length to obtain a joint signature identity certificate.
[0060] Specifically, based on the cross-domain registration request sent by the user received by the authentication blockchain node, the authentication blockchain node is in the local domain, and the cross-domain registration request is a registration request initiated by the authentication blockchain node to the out-of-domain system. The cross-domain registration request is parsed to obtain a cross-domain distributed identity, which includes a cross-domain distributed identity identifier and a cross-domain public-private key pair. The cross-domain distributed identity identifier is different from the identity identifier registered by the user in the original identity authentication system of the department to which he belongs. A certificate signing request is generated based on the cross-domain distributed identity combined with the certificate identifier, and the certificate signing request is obtained by binding the cross-domain public key domain certificate identifier in the cross-domain distributed identity. Public key authentication is performed to several certification authorities based on the certificate signing request, and the public key validity period is authenticated to several certification authorities according to the certificate signing request to obtain several public key authentication results. If the public key authentication fails, the cross-domain registration request is parsed and the certificate signing request is generated again. If the public key authentication passes, that is, the cross-domain public key is within the validity period, a corresponding sub-signature certificate is generated using a sub-signature generation algorithm based on the several public key authentication results, and each cross-domain public key within the validity period is submitted to the certificate authority for identity verification. After the identity verification passes, a certificate file to be signed is generated, and a sub-signature is generated using an anti-collision hash function in combination with the certificate file to be signed. According to the sub-signature, a corresponding sub-signature certificate is generated using the certificate running parameters generated by the cyclic group order, bilinear mapping and encryption channel. A user behavior feature vector is generated based on the cross-domain registration request using a certificate model. The cross-domain registration request includes user behavior information, which includes the user's terminal device coordinate information, terminal device mobile operation information and terminal screen operation information. The certificate model is obtained by training the user's historical behavior information. The user behavior information is input into the certificate model to generate a user behavior feature vector, and a user behavior certificate is generated based on the user behavior feature vector. The user behavior probability information is calculated according to the user behavior feature vector. The user behavior probability information includes the screen operation time interval distribution probability, the operation number distribution and the mobile operation time distribution. The target behavior feature vector is generated based on the user behavior probability information combined with the preset vector construction logic. The user behavior certificate is generated based on the target behavior feature vector combined with the user behavior probability information. Whether the user behavior is legal can be judged through the user behavior certificate. The target user is guaranteed to be a legal user through the behavior information of the target user, and illegal users are prevented from stealing the user identity information of the target user for authentication, thereby improving the accuracy and security of identity authentication. All sub-signature certificates, cross-domain distributed identities and user behavior certificates are generated using a hash algorithm with a fixed-bit length hash value, which can be set to 160 bits. Asymmetric encryption is performed based on the fixed-bit length hash value to obtain a joint signature identity certificate.
[0061] S12: Sending the joint signature identity certificate to a first distributed notary node, wherein the first distributed notary node generates an identity token based on the joint signature identity certificate;
[0062] In the specific implementation process of the present invention, the first distributed notary node generates an identity token based on the joint signature identity certificate, including: the first distributed notary node generates a certificate verification request based on the joint signature identity certificate, and sends the certificate verification request to the certificate verification node; the certificate verification node performs a valid signature certificate authentication on the joint signature identity certificate based on the certificate verification request to obtain a valid signature certificate authentication result; based on the valid signature certificate authentication result, a preset security authentication mechanism is used in combination with cookie information verification to generate an identity token.
[0063] Specifically, the joint signature identity certificate is sent to the first distributed notary node through an encrypted transmission channel, and the first distributed notary node generates a certificate verification request based on the joint signature identity certificate, and sends the certificate verification request to the certificate verification node. The certificate verification node performs valid signature certificate authentication on the joint signature identity certificate based on the certificate verification request, generates a challenge number according to the certificate verification request, generates a secret random number by using a random number generation function through the challenge number, performs a blind transformation on the joint signature identity certificate and the secret random number, obtains a temporary joint signature identity certificate, verifies the legality of the temporary joint signature identity certificate by querying the identity revocation list and corresponding calculations, verifies the legality of the temporary joint signature identity certificate by verifying the legality of the joint signature identity certificate, obtains a valid signature certificate authentication result, that is, verifies whether the joint signature identity certificate is legal or whether it is within the validity period, and thus can achieve the correctness and unforgeability of the verification of the joint signature identity certificate, reduce the computational overhead and effectively improve the security and reliability, and if the valid signature certificate authentication fails, a prompt message is issued, and the user performs the above process again according to the prompt message. Based on the valid signature certificate authentication result, an identity token is generated using a preset security authentication mechanism combined with cookie information verification. The preset security authentication mechanism can adopt Hypertext Transfer Protocol or Hypertext Transfer Security Protocol authentication. Cookie information verification is a network-based authentication mechanism. A security identifier is generated based on cookie information verification. According to the security identifier and the preset security authentication mechanism, an identity token is generated using a legally passed joint signature identity certificate.
[0064] S13: Send the identity token to a second distributed notary node, which generates a cross-domain identity credential based on the identity token and the information tampering check result, and writes the cross-domain identity credential into a distributed cross-domain identity ledger;
[0065] In the specific implementation process of the present invention, the cross-domain identity credential is generated based on the identity token in combination with the information tampering check result, including: generating a result signature based on the identity token, and generating an initial identity credential based on the result signature and the identity token; converting the initial identity credential into a byte stream based on the ObjectOutputStream sequence to obtain the initial identity credential after the byte stream conversion; converting the initial identity credential after the byte stream conversion into an original object based on the ObjectInputStream desequence, and performing an information tampering check on the original object to obtain the information tampering check result; generating a cross-domain identity credential based on the information tampering check result, the initial identity credential and the result signature.
[0066] Specifically, the identity token is sent to the second distributed notary node, the second distributed notary node is used to generate a cross-domain identity credential, and the first distributed notary node is used to generate an identity token. The two distributed notary nodes are responsible for generating different identity information, thereby improving the reliability of cross-domain identity authentication. A result signature is generated based on the identity token, a cross-domain request signature is parsed from the identity token, and the cross-domain request signature is verified. After the verification is passed, the verification result is signed to generate a result signature, and the credential resource content is generated based on the result signature and the identity token, and the initial identity credential is generated according to the credential resource content. The initial identity credential is converted into a byte stream based on the ObjectOutputStream sequence. The ObjectOutputStream sequence is an object stream function that provides a serialization function, which can convert an object into a byte stream, realize the persistent storage of the object, and obtain the initial identity credential after the byte stream conversion. The initial identity credential after the byte stream conversion is converted into the original object based on the ObjectInputStream deserialization. The ObjectInputStream deserialization is an object stream function that provides a deserialization function. Through the deserialization process, the obtained cross-domain identity credential can carry more resources and resource domains. The original object is checked for information tampering, and the signature information of the original object is checked to see if it has been tampered with and compared with the database data to ensure the authenticity and integrity of the identity information. If it is found that information tampering has occurred, a prompt message is issued to stop the user's cross-domain identity authentication. The user re-verifies according to the prompt message to obtain the information tampering check result. By checking the original object generated by the initial identity credential after the byte stream is converted, a more comprehensive and accurate information tampering check can be achieved without losing identity information data. A cross-domain identity credential is generated based on the information tampering check result, the initial identity credential and the result signature. After checking that the signature information in the initial identity credential has not been tampered with, the credential resource content in the identity credential is extracted, and a cross-domain identity credential is generated according to the credential resource content combined with the information tampering check result and the result signature, and the cross-domain identity credential is written into the distributed cross-domain identity ledger.
[0067] S14: The distributed cross-domain identity ledger performs cross-domain verification based on the cross-domain identity credential to obtain a cross-domain verification result;
[0068] In the specific implementation process of the present invention, the distributed cross-domain identity ledger performs cross-domain verification based on the cross-domain identity credential to obtain a cross-domain verification result, including: the distributed cross-domain identity ledger verifies the cross-domain identity credential based on the cross-domain identity credential definition to obtain a verification result; based on a distributed verification consensus algorithm, the cross-domain request review is performed using the cross-domain identity credential to obtain a cross-domain request review result; based on the verification result and the cross-domain request review result, cross-domain verification is performed to obtain a cross-domain verification result.
[0069] Specifically, the distributed cross-domain identity ledger verifies the cross-domain identity credential based on the cross-domain identity credential definition, that is, verifies the summary generated by the cross-domain identity credential according to the cross-domain identity credential definition, obtains the verification signature, and obtains the verification result. Based on the distributed verification consensus algorithm, the cross-domain request is reviewed using the cross-domain identity credential. After the verification is passed, a cross-domain authentication request is initiated, and the distributed verification consensus algorithm is run to review the cross-domain request using the cross-domain identity credential. An authentication group is set, and the authentication group includes several nodes. The nodes in the authentication group elect a sorting node to be responsible for counting authentication voting information. The authentication group nodes vote on the cross-domain identity credential and the cross-domain authentication request according to the authentication credentials. The voting results are submitted to the sorting node. It is determined whether the cross-domain request review is passed according to the voting results. If the cross-domain request review is passed, a cross-domain authentication credential is generated according to the cross-domain identity credential. If it fails, a prompt message is issued, and the user re-verifies according to the prompt message, that is, the cross-domain request review result is obtained. Cross-domain verification is performed based on the signature verification result and the cross-domain request review result. That is, when the signature verification and cross-domain request review are passed, the user is judged to have passed the cross-domain verification based on the generated signature verification signature and the cross-domain authentication credential, and the cross-domain verification result is obtained.
[0070] S15: Performing an identity credibility assessment based on the cross-domain identity credential to obtain an identity credibility assessment result, and generating an identity credibility certificate based on the identity credibility assessment result and the cross-domain verification result;
[0071] In the specific implementation process of the present invention, the identity credibility is evaluated based on the cross-domain identity credential to obtain the identity credibility evaluation result, and the identity credibility proof is generated based on the identity credibility evaluation result and the cross-domain verification result, including: sending a trusted authentication request to a trusted evaluation node, and obtaining a trusted measurement request parameter list, a timestamp and an identity credibility evaluation standard based on the trusted authentication request; generating a homomorphically encrypted public-private key pair based on the cross-domain identity credential, and performing an identity credibility evaluation using the homomorphically encrypted public-private key pair based on the trusted measurement request parameter list, a timestamp and an identity credibility evaluation standard to obtain an identity credibility evaluation result; obtaining a historical user identity credibility evaluation record based on the distributed cross-domain identity ledger; and generating an identity credibility proof based on the historical user identity credibility evaluation record, the identity credibility evaluation result and the cross-domain verification result.
[0072] Specifically, a trusted authentication request is sent to a trusted evaluation node, and a trusted measurement request parameter list, a timestamp, and an identity credibility evaluation standard are obtained based on the trusted authentication request. The trusted measurement request parameter list may include an identity authentication value and a response random number, etc. The identity credibility evaluation standard includes an identity credibility minimum threshold requirement. A homomorphically encrypted public-private key pair is generated based on the cross-domain identity credential, and a homomorphically encrypted public-private key pair is generated using the cross-domain identity credential according to the Paillier improved algorithm for the partial discrete logarithm problem. Identity credibility is evaluated using the homomorphically encrypted public-private key pair based on the trusted measurement request parameter list, timestamp, and identity credibility evaluation standard. A ciphertext authentication chain code is calculated for the cross-domain identity credential according to the trusted measurement request parameter list and timestamp, and comparison parameters are set. Identity credibility is calculated using the ciphertext authentication chain code combined with linear transformation parameters according to the comparison parameters. The identity credibility is compared with the identity credibility minimum threshold requirement in the identity credibility evaluation standard, and the comparison result is verified according to the homomorphically encrypted public-private key pair to obtain an identity credibility evaluation result, that is, identity credibility is obtained. Based on the corresponding storage node of the distributed cross-domain identity ledger, the historical user identity credibility evaluation record is obtained, and the identity credibility proof is generated based on the historical user identity credibility evaluation record, the identity credibility evaluation result and the cross-domain verification result, that is, the identity credibility proof is generated according to the identity credibility, the verification signature and the cross-domain authentication credential and the average of the historical identity credibility in the historical identity credibility evaluation record.
[0073] S16: Determine whether the user has passed the cross-domain identity authentication based on the identity trustworthy proof. If it is determined that the user has passed the cross-domain identity authentication, assign permissions to the user, and write the judgment result of the cross-domain identity authentication, the identity trustworthy proof, and the permissions assigned to the user into the distributed cross-domain identity ledger.
[0074] In the specific implementation process of the present invention, the method of judging whether the user has passed the cross-domain identity authentication based on the identity trustworthy proof, and if it is judged that the user has passed the cross-domain identity authentication, assigning permissions to the user, and writing the judgment result of the cross-domain identity authentication, the identity trustworthy proof and the permissions assigned to the user into the distributed cross-domain identity ledger, includes: obtaining the identity trustworthy proof definition, verifying the identity trustworthy proof based on the identity trustworthy proof definition, and obtaining the signature verification result; judging the validity period of the identity trustworthy proof, and obtaining the validity period judgment result; judging whether the user has passed the cross-domain identity authentication based on the signature verification result and the validity period judgment result; if it is judged that the user has passed the cross-domain identity authentication, assigning permissions to the user, and forming a compact storage structure based on the Merkle tree with the judgment result of the cross-domain identity authentication, the identity trustworthy proof and the permissions assigned to the user, and writing the compact storage structure based on the Merkle tree into the distributed cross-domain identity ledger.
[0075] Specifically, obtain the definition of a trusted identity certificate, verify the trusted identity certificate based on the trusted identity certificate definition, determine whether the trusted identity certificate is complete, and obtain the verification result. Determine the validity period of the trusted identity certificate and obtain the validity period judgment result. Determine whether the user has passed the cross-domain identity authentication based on the verification result and the validity period judgment result. If the verification is passed and the trusted identity certificate is within the validity period, the user is judged to have passed the cross-domain identity authentication. If the verification fails and / or the trusted identity certificate is not within the validity period, a prompt message is issued to notify the user to re-authenticate. If it is determined that the user has passed the cross-domain identity authentication, permissions are assigned to the user, and the user accesses different systems to perform related operations according to the assigned permissions. The judgment results of cross-domain identity authentication, identity credibility proof and the permissions assigned to users are composed of a compact storage structure based on the Merkle tree, and the compact storage structure based on the Merkle tree is written into the distributed cross-domain identity ledger. The Merkle tree is a Merkle hash tree. The compact storage structure that constitutes the Merkle tree enables data integrity verification to be completed in logarithmic time without checking the entire data set. It can effectively store large amounts of data, and only the root hash value needs to be retained. The Merkle tree improves storage performance and security.
[0076] In an embodiment of the present invention, a joint signature identity certificate is generated based on all sub-signature certificates, cross-domain distributed identity identifiers and user behavior certificates generated from several public key authentication results obtained by performing public key authentication on several certification authorities through a certificate signing request. Sub-signature certificates are generated through multiple certification authorities to avoid the failure of a single certification authority to verify the user's identity. At the same time, a user behavior certificate is added to improve the credibility of the obtained joint signature identity certificate. A cross-domain identity credential is generated based on an identity token combined with an information tampering check result to avoid information tampering and leakage of the identity token, improve the security of the cross-domain identity credential, and enable the obtained cross-domain identity credential to carry more resources and resource domains through deserialization processing. An identity credibility assessment is performed based on the cross-domain identity credential to generate an identity credibility certificate, and the user's identity risk assessment is achieved without increasing the network communication load, which can effectively ensure the reliability of user identity authentication and greatly reduce the threat of out-of-domain attacks. The judgment results of cross-domain identity authentication, identity credibility proof and the permissions assigned to users are composed of a compact storage structure based on the Merkle tree and written into a distributed cross-domain identity ledger. The distributed ledger can avoid single point failures and trust issues, making cross-domain identity authentication achieve a more ideal effect.
[0077] Embodiment 2
[0078] See also Figure 2 , Figure 2 It is a schematic diagram of the structural composition of a cross-domain identity authentication device based on a distributed ledger in an embodiment of the present invention.
[0079] like Figure 2 As shown, a cross-domain identity authentication device based on a distributed ledger, the device comprising:
[0080] Joint signature identity certificate generation module 21: used to receive a cross-domain registration request sent by a user based on an authentication blockchain node, generate a cross-domain distributed identity based on the cross-domain registration request, and generate a joint signature identity certificate based on the cross-domain distributed identity using a certificate model;
[0081] The identity token generation module 22 is used to send the joint signature identity certificate to the first distributed notary node, and the first distributed notary node generates an identity token based on the joint signature identity certificate;
[0082] A cross-domain identity credential generation module 23 is used to send the identity token to a second distributed notary node, which generates a cross-domain identity credential based on the identity token and the information tampering check result, and writes the cross-domain identity credential into a distributed cross-domain identity ledger;
[0083] Cross-domain verification module 24: used for the distributed cross-domain identity ledger to perform cross-domain verification based on the cross-domain identity credential to obtain a cross-domain verification result;
[0084] The identity trust proof module 25 is used to perform an identity trustworthiness assessment based on the cross-domain identity credential, obtain an identity trustworthiness assessment result, and generate an identity trustworthiness proof based on the identity trustworthiness assessment result and the cross-domain verification result;
[0085] The cross-domain identity authentication module 26 is used to determine whether the user has passed the cross-domain identity authentication based on the identity trust certificate. If it is determined that the user has passed the cross-domain identity authentication, permissions are assigned to the user, and the judgment result of the cross-domain identity authentication, the identity trust certificate and the permissions assigned to the user are written into the distributed cross-domain identity ledger.
[0086] In the specific implementation process of the present invention, the specific implementation method of the device item can refer to the implementation method of the above-mentioned method item, which will not be repeated here.
[0087] In an embodiment of the present invention, a joint signature identity certificate is generated based on all sub-signature certificates, cross-domain distributed identity identifiers and user behavior certificates generated from several public key authentication results obtained by performing public key authentication on several certification authorities through a certificate signing request. Sub-signature certificates are generated through multiple certification authorities to avoid the failure of a single certification authority to verify the user's identity. At the same time, a user behavior certificate is added to improve the credibility of the obtained joint signature identity certificate. A cross-domain identity credential is generated based on an identity token combined with an information tampering check result to avoid information tampering and leakage of the identity token, improve the security of the cross-domain identity credential, and enable the obtained cross-domain identity credential to carry more resources and resource domains through deserialization processing. An identity credibility assessment is performed based on the cross-domain identity credential to generate an identity credibility certificate, and the user's identity risk assessment is achieved without increasing the network communication load, which can effectively ensure the reliability of user identity authentication and greatly reduce the threat of out-of-domain attacks. The judgment results of cross-domain identity authentication, identity credibility proof and the permissions assigned to users are composed of a compact storage structure based on the Merkle tree and written into a distributed cross-domain identity ledger. The distributed ledger can avoid single point failures and trust issues, making cross-domain identity authentication achieve a more ideal effect.
[0088] An embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, a cross-domain identity authentication method based on a distributed ledger is implemented in any of the above embodiments. The computer-readable storage medium includes, but is not limited to, any type of disk (including floppy disk, hard disk, optical disk, CD-ROM, and magneto-optical disk), ROM (Read-Only Memory), RAM (Random Access Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory, magnetic card or optical card. That is, the storage device includes any medium that can store or transmit information in a readable form by a device (for example, a computer, a mobile phone), which can be a read-only memory, a disk or an optical disk, etc.
[0089] Embodiment 3
[0090] See also Figure 3 , Figure 3 It is a schematic diagram of the structure of an electronic device in an embodiment of the present invention.
[0091] The embodiment of the present invention further provides an electronic device, such as Figure 3 As shown, the electronic device includes a memory 31, a processor 33, and a computer program 32 stored in the memory 31 and executable on the processor 33. Those skilled in the art will appreciate that Figure 3The electronic device shown does not constitute a limitation on all devices, and may include more or fewer components than shown, or combine certain components. The memory 31 can be used to store the computer program 32 and various functional modules, and the processor 33 runs the computer program 32 stored in the memory 31, thereby executing various functional applications and data processing of the device. The memory can be an internal memory or an external memory, or include both internal and external memories. The internal memory can include a read-only memory (ROM), a programmable ROM (PROM), an electrically programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a flash memory, or a random access memory. The external memory can include a hard disk, a floppy disk, a ZIP disk, a U disk, a magnetic tape, etc. The processor 33 can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general processor may be a microprocessor, a single chip microcomputer or the processor 33 may also be any conventional processor, etc. The processor and memory disclosed in the present invention include but are not limited to these types of processors and memories. The processor and memory disclosed in the present invention are only examples and not limitations.
[0092] As an embodiment, the electronic device includes: one or more processors 33, a memory 31, and one or more computer programs 32, wherein the one or more computer programs 32 are stored in the memory 31 and are configured to be executed by the one or more processors 33, and the one or more computer programs 32 are configured to execute the cross-domain identity authentication method based on a distributed ledger in any of the above-mentioned embodiments. For the specific implementation process, please refer to the above-mentioned embodiments and will not be repeated here.
[0093] In an embodiment of the present invention, a joint signature identity certificate is generated based on all sub-signature certificates, cross-domain distributed identity identifiers and user behavior certificates generated from several public key authentication results obtained by performing public key authentication on several certification authorities through a certificate signing request. Sub-signature certificates are generated through multiple certification authorities to avoid the failure of a single certification authority to verify the user's identity. At the same time, a user behavior certificate is added to improve the credibility of the obtained joint signature identity certificate. A cross-domain identity credential is generated based on an identity token combined with an information tampering check result to avoid information tampering and leakage of the identity token, improve the security of the cross-domain identity credential, and enable the obtained cross-domain identity credential to carry more resources and resource domains through deserialization processing. An identity credibility assessment is performed based on the cross-domain identity credential to generate an identity credibility certificate, and the user's identity risk assessment is achieved without increasing the network communication load, which can effectively ensure the reliability of user identity authentication and greatly reduce the threat of out-of-domain attacks. The judgment results of cross-domain identity authentication, identity credibility proof and the permissions assigned to users are composed of a compact storage structure based on the Merkle tree and written into a distributed cross-domain identity ledger. The distributed ledger can avoid single point failures and trust issues, making cross-domain identity authentication achieve a more ideal effect.
[0094] In addition, the above is a detailed introduction to a cross-domain identity authentication method based on a distributed ledger and related devices provided in an embodiment of the present invention. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for general technical personnel in this field, according to the idea of the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.
Claims
1. A cross-domain identity authentication method based on a distributed ledger, characterized in that: The method comprises: Receiving a cross-domain registration request sent by a user based on an authentication blockchain node, generating a cross-domain distributed identity based on the cross-domain registration request, and generating a joint signature identity certificate based on the cross-domain distributed identity using a certificate model; Sending the jointly signed identity certificate to a first distributed notary node, wherein the first distributed notary node generates an identity token based on the jointly signed identity certificate; Sending the identity token to a second distributed notary node, which generates a cross-domain identity credential based on the identity token and the information tampering check result, and writes the cross-domain identity credential into a distributed cross-domain identity ledger; The distributed cross-domain identity ledger performs cross-domain verification based on the cross-domain identity credential to obtain a cross-domain verification result; Performing an identity credibility assessment based on the cross-domain identity credential to obtain an identity credibility assessment result, and generating an identity credibility certificate based on the identity credibility assessment result and the cross-domain verification result; Based on the identity trustworthy proof, it is judged whether the user has passed the cross-domain identity authentication. If it is judged that the user has passed the cross-domain identity authentication, permissions are assigned to the user, and the judgment result of the cross-domain identity authentication, the identity trustworthy proof and the permissions assigned to the user are written into the distributed cross-domain identity ledger, including: obtaining the identity trustworthy proof definition, verifying the identity trustworthy proof based on the identity trustworthy proof definition, and obtaining the signature verification result; judging the validity period of the identity trustworthy proof, and obtaining the validity period judgment result; judging whether the user has passed the cross-domain identity authentication based on the signature verification result and the validity period judgment result; if it is judged that the user has passed the cross-domain identity authentication, permissions are assigned to the user, and the judgment result of the cross-domain identity authentication, the identity trustworthy proof and the permissions assigned to the user are composed of a compact storage structure based on a Merkle tree, and the compact storage structure based on the Merkle tree is written into the distributed cross-domain identity ledger.
2. The cross-domain identity authentication method based on distributed ledger according to claim 1 is characterized in that: The generating a cross-domain distributed identity based on the cross-domain registration request, and generating a joint signature identity certificate based on the cross-domain distributed identity using a certificate model, includes: Parsing the cross-domain registration request to obtain a cross-domain distributed identity; Generate a certificate signing request based on the cross-domain distributed identity combined with the certificate identifier, and perform public key authentication with several certification authorities based on the certificate signing request to obtain several public key authentication results; Generate a corresponding sub-signature certificate using a sub-signature generation algorithm based on the multiple public key authentication results; Generate a user behavior feature vector based on the cross-domain registration request using a certificate model, and generate a user behavior certificate based on the user behavior feature vector; All sub-signature certificates, cross-domain distributed identities and user behavior certificates are generated into a hash value with a fixed bit length using a hash algorithm, and asymmetric encryption is performed based on the hash value with a fixed bit length to obtain a joint signature identity certificate.
3. The cross-domain identity authentication method based on distributed ledger according to claim 1 is characterized in that: The first distributed notary node generates an identity token based on the joint signature identity certificate, including: The first distributed notary node generates a certificate verification request based on the joint signature identity certificate, and sends the certificate verification request to the certificate verification node; The certificate verification node performs valid signature certificate authentication on the joint signature identity certificate based on the certificate verification request to obtain a valid signature certificate authentication result; Based on the valid signature certificate authentication result, an identity token is generated by utilizing a preset security authentication mechanism in combination with cookie information verification.
4. The cross-domain identity authentication method based on distributed ledger according to claim 1 is characterized in that: The generating a cross-domain identity credential based on the identity token and the information tampering check result includes: generating a result signature based on the identity token, and generating an initial identity credential based on the result signature and the identity token; Performing byte stream conversion on the initial identity credential based on the ObjectOutputStream sequence to obtain the initial identity credential after byte stream conversion; Based on ObjectInputStream deserialization, the initial identity credential after the byte stream conversion is converted into the original object, and the original object is checked for information tampering to obtain the information tampering check result; A cross-domain identity credential is generated based on the information tampering check result, the initial identity credential and the result signature.
5. The cross-domain identity authentication method based on distributed ledger according to claim 1 is characterized in that: The distributed cross-domain identity ledger performs cross-domain verification based on the cross-domain identity credential to obtain a cross-domain verification result, including: The distributed cross-domain identity ledger verifies the cross-domain identity credential based on the cross-domain identity credential definition to obtain a verification result; Based on the distributed verification consensus algorithm, the cross-domain identity credential is used to perform a cross-domain request review to obtain a cross-domain request review result; Based on the signature verification result and the cross-domain request review result, cross-domain verification is performed to obtain a cross-domain verification result.
6. The cross-domain identity authentication method based on distributed ledger according to claim 1, characterized in that: The performing of identity credibility assessment based on the cross-domain identity credential to obtain an identity credibility assessment result, and generating an identity credibility certificate based on the identity credibility assessment result and the cross-domain verification result, includes: Sending a trusted authentication request to a trusted evaluation node, and obtaining a trusted measurement request parameter list, a timestamp, and an identity credibility evaluation standard based on the trusted authentication request; Generate a homomorphically encrypted public-private key pair based on the cross-domain identity credential, perform identity credibility evaluation using the homomorphically encrypted public-private key pair based on the trusted metric request parameter list, timestamp, and identity credibility evaluation criteria, and obtain an identity credibility evaluation result; Obtaining historical user identity credibility assessment records based on the distributed cross-domain identity ledger; An identity credibility certificate is generated based on the historical user identity credibility evaluation record, the identity credibility evaluation result and the cross-domain verification result.
7. A cross-domain identity authentication device based on a distributed ledger, characterized in that: The device comprises: A joint signature identity certificate generation module: used to receive a cross-domain registration request sent by a user based on an authentication blockchain node, generate a cross-domain distributed identity based on the cross-domain registration request, and generate a joint signature identity certificate based on the cross-domain distributed identity using a certificate model; An identity token generation module is used to send the joint signature identity certificate to a first distributed notary node, and the first distributed notary node generates an identity token based on the joint signature identity certificate; A cross-domain identity credential generation module: used to send the identity token to a second distributed notary node, which generates a cross-domain identity credential based on the identity token and the information tampering check result, and writes the cross-domain identity credential into a distributed cross-domain identity ledger; Cross-domain verification module: used for the distributed cross-domain identity ledger to perform cross-domain verification based on the cross-domain identity credential to obtain a cross-domain verification result; Identity credibility proof module: used to perform identity credibility assessment based on the cross-domain identity credential, obtain identity credibility assessment result, and generate identity credibility proof based on the identity credibility assessment result and the cross-domain verification result; Cross-domain identity authentication module: used to determine whether the user has passed the cross-domain identity authentication based on the identity trustworthy proof. If it is determined that the user has passed the cross-domain identity authentication, permissions are assigned to the user, and the judgment result of the cross-domain identity authentication, the identity trustworthy proof and the permissions assigned to the user are written into the distributed cross-domain identity ledger, including: obtaining the identity trustworthy proof definition, verifying the identity trustworthy proof based on the identity trustworthy proof definition, and obtaining the signature verification result; judging the validity period of the identity trustworthy proof to obtain the validity period judgment result; judging whether the user has passed the cross-domain identity authentication based on the signature verification result and the validity period judgment result; if it is determined that the user has passed the cross-domain identity authentication, permissions are assigned to the user, and the judgment result of the cross-domain identity authentication, the identity trustworthy proof and the permissions assigned to the user are composed of a compact storage structure based on a Merkle tree, and the compact storage structure based on a Merkle tree is written into the distributed cross-domain identity ledger.
8. An electronic device, comprising a processor and a memory, characterized in that: The memory is used to store instructions, and the processor is used to call the instructions in the memory, so that the electronic device executes the cross-domain identity authentication method based on a distributed ledger as described in any one of claims 1 to claim 6.
9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and when the computer instructions are executed on an electronic device, the electronic device executes the cross-domain identity authentication method based on a distributed ledger as described in any one of claims 1 to 6.
