KR102079354B1 - User authentication system based on blockchain technology and control method thereof - Google Patents

Abstract

The present invention relates to a system for performing user authentication based on blockchain technology which can increase reliability for user authentication or document re-verification. More specifically, the system for performing user authentication comprises: a main blockchain consisting of a plurality of main nodes; a sub blockchain consisting of a plurality of sub nodes; an authentication request server to request user authentication; and an authentication server to generate user identification information in correspondence with an authentication request from the authentication request server. The authentication server transmits a first transaction associated with the authentication request and a second transaction associated with the user identification information to a first main node. The authentication request server transfers a verification query of the generated user identification information to a first sub node. A second sub node transfers the verification query to the main blockchain via a second main node.

Description

USER AUTHENTICATION SYSTEM BASED ON BLOCKCHAIN TECHNOLOGY AND CONTROL METHOD THEREOF}

The present invention relates to an authentication system, and more particularly, to an authentication system capable of improving reliability by recording and reading operations related to user authentication or document authentication in a blockchain transaction.

Blockchain technology refers to a data distribution processing technology in which all users participating in a network distribute and store all data managed. It is also called 'distributed ledger technology' or 'public ledger' in that the ledger containing transaction information is not owned by the trading entity or a specific institution, but is shared by all network participants. . Blockchain is a name given as a chain of blocks containing transactions.

Such blockchains can be divided into public blockchains and private blockchains. The public blockchain corresponds to the public transaction book described above, and generally referred to as a blockchain refers to a public blockchain. The private blockchain is a relative concept, and is often referred to as an enterprise blockchain because it is mainly used by an enterprise. A consortium blockchain, in which several companies (or institutions) jointly participate, also falls into the category of private blockchain in a broad sense.

Unlike public blockchains, which are open to anyone and anyone can create transactions, private blockchains can only participate if they are authorized by the service provider (enterprise or institution), and only legally responsible institutions can create transactions. In addition, unlike the public blockchain, where transaction details are open to everyone and all nodes participating in the network verify and approve transactions, in the private blockchain, only authorized institutions verify transactions and approve transactions.

Public blockchain can be participated by anyone and is highly trusted through mutual verification of all participants, but it has a disadvantage of slow processing due to keeping and sharing transaction records of all participants. In contrast, the private blockchain is much faster because only authorized nodes participate and do not need to verify other nodes. However, users of private blockchains have a limit on reliability compared to public blockchains because they have to rely entirely on service providers.

Such a blockchain can be utilized in various industrial fields, and will be most suitable for a field in which reliability for counterfeiting is to be secured. Attestation tasks such as authentication of users or verification of documents are inevitably exposed to the risk of forgery or tampering, and reliability will be more urgent than in other industries. Nevertheless, research on such a verification system using blockchain technology has not been conducted properly.

The present invention aims to solve the above-mentioned problem and other problems. Another object is to provide a certification system that can improve the reliability of the user's authentication or document proof.

Another object is to provide a certification system that can be used to verify the entire process from issuing, distributing and destroying the document to be proved, and to verify the process.

Technical problems to be achieved in the present invention are not limited to the above-mentioned technical problems, and other technical problems not mentioned above will be clearly understood by those skilled in the art from the following description. Could be.

According to an aspect of the present invention to achieve the above or another object, a system for performing user authentication (User Authentication), the main block chain consisting of a plurality of main nodes; A sub blockchain composed of a plurality of sub nodes; An authentication request server for requesting user authentication; And an authentication server for generating user identification information in response to an authentication request from the authentication request server, wherein the authentication server comprises: a first transaction relating to the authentication request and a second transaction relating to generation of the user identification information; transaction) to the first main node, the authentication request server forwards a verification query of the generated user identification information to a first sub node, and the second sub node transmits the second sub node through the second main node. An electronic document authentication system is provided, wherein a verification query is transmitted to the main blockchain.

Referring to the effect of the authentication system according to the present invention.

According to at least one of the embodiments of the present invention, there is an advantage in that the reliability of user authentication can be improved based on the blockchain technology.

In addition, according to at least one of the embodiments of the present invention, in recording the authentication procedure from the authentication requesting authority in a blockchain transaction, even if the number of authentication requesting organizations increases, it is possible to record effectively and without problems without a bottleneck. have.

Further scope of the applicability of the present invention will become apparent from the following detailed description. However, various changes and modifications within the spirit and scope of the present invention can be clearly understood by those skilled in the art, and therefore, specific embodiments, such as the detailed description and the preferred embodiments of the present invention, should be understood as given by way of example only.

1 is a diagram showing the structure of a blockchain according to an embodiment of the present invention.
2 is a diagram illustrating an extension relationship between a main block chain and a sub block chain according to an embodiment of the present invention.
3 is a diagram illustrating a first proof procedure of a document according to an embodiment of the present invention.
4 is a diagram illustrating a certificate request process between certification authorities according to an embodiment of the present invention.
5 is a diagram illustrating a user authentication procedure according to an embodiment of the present invention.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings, and the same or similar components will be given the same reference numerals regardless of the reference numerals, and redundant description thereof will be omitted. The suffixes "module" and "unit" for components used in the following description are given or mixed in consideration of ease of specification, and do not have distinct meanings or roles. In addition, in describing the embodiments disclosed herein, when it is determined that the detailed description of the related known technology may obscure the gist of the embodiments disclosed herein, the detailed description thereof will be omitted. In addition, the accompanying drawings are intended to facilitate understanding of the embodiments disclosed herein, but are not limited to the technical spirit disclosed herein by the accompanying drawings, all changes included in the spirit and scope of the present invention. It should be understood to include equivalents and substitutes.

Terms including ordinal numbers such as first and second may be used to describe various components, but the components are not limited by the terms. The terms are used only for the purpose of distinguishing one component from another.

When a component is said to be "connected" or "connected" to another component, it may be directly connected to or connected to that other component, but it may be understood that other components may be present in the middle. Should be. On the other hand, when a component is said to be "directly connected" or "directly connected" to another component, it should be understood that there is no other component in between.

Singular expressions include plural expressions unless the context clearly indicates otherwise.

In this application, the terms "comprises" or "having" are intended to indicate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof.

Blockchain technology is now actively used in financial systems. Hereinafter, the method applied to the financial system will be described.

Blockchain focuses on the decentralization of the P2P (Peer to Peer) transaction, which breaks down the existing financial system that secures and manages all transactions in financial institutions. P2P is a communication network connecting personal computers without a server or client, and each connected computer acts as a server and a client and shares information.

In the existing financial system, financial companies have kept transaction records on a central server, whereas in blockchain based on P2P method, transaction information is put in blocks and shared by all participants.

In the financial system, the processing of blockchain technology for the transaction process (transaction, transaction) is performed as follows. ① A asks B for a transfer request for money transfer. ② A block containing the relevant transaction information is created. ③ Once the block is sent to all participants on the network, the participants mutually validate the transaction information. ④ Transaction details that match the majority of the participants' data are verified by the normal ledger, and the verified block is linked to the previous block, and a copy is made and distributed to each user's computer. ⑤ A transfers money to B and the transaction is completed. In this case, all transactions that occur within a predetermined period (for example, about 10 minutes) may be generated as one block.

By this process, by confirming whether or not the data match the majority of the participants, not only the reliability can be secured when the block is created, but also a copy of the completed blocks can be individually stored in each computer (node) for forgery and alteration. Make it practically impossible.

In the present invention, instead of proof of transactions utilized in the financial system as described above, various operations related to user authentication and / or first proof of electronic documents (hereinafter, all operations recorded in the blockchain are referred to as transactions). ) Is to be applied.

Hereinafter, terms related to blockchain will be described.

Block

A block is a unit that stores data and is divided into a body and a header. The body contains the transaction details, and the header contains an encryption code, such as a Merkle hash (Merlute) or a nonce (an arbitrary number related to encryption). Blocks are created every 10 minutes, and the transaction records are pulled together to form blocks, verifying their reliability, and connecting to previous blocks to form a blockchain. The first block started here is called the Genesis block. That is, the Genesis block refers to the first block in which no block is created before it.

Node

The blockchain maintains and manages the network of individual servers that participate in the transaction without keeping and managing transaction records in a centralized server. This individual server, or participant, is called a node. Because there is no central administrator, the role of the node distributing the block is important, and at least half of the participating nodes must agree to create a new block. Nodes have blockchains stored on their computers, and even if some nodes are hacked and the existing contents are misplaced, data remains in multiple nodes so that data can be preserved continuously.

Hash Function

This function produces a result of the same length no matter what data is entered. The result is unlikely to overlap, and it is difficult to inversely estimate the input as the result. Because of this, you can compare hash values to see if data has changed. The hash function is a more advanced form of SHA-2 (SHA 256) since the Secure Hash Algorithm (SHA-1) was first devised, which is used in the blockchain. SHA-2 results in 256 bits no matter what length you enter.

1 is a diagram showing the structure of a blockchain according to an embodiment of the present invention. 2 is a diagram illustrating an extension relationship between a main block chain and a sub block chain according to an embodiment of the present invention.

Proof system according to an embodiment of the present invention, the main blockchain 110 and at least two sub-nodes (121-1 to 121-4) that at least two main nodes (111-1 to 111-3) participate. May include a sub blockchain 120 to participate.

The main block chain 110 may form a main block at a predetermined period based on the main transaction, and the sub block chain 120 may form a sub block at a predetermined period based on the sub transaction. That is, the blocks generated between the main block chain 110 and the sub block chain 120 are not connected to each other or a verification procedure is performed.

However, the main block chain 110 and the sub block chain 120 may be selectively connected, and when selectively connected, a verification procedure may be required.

For example, as will be described in detail below, when a certificate generation transaction occurs in the main blockchain 110, information on the transaction may be shared in the subblockchain. Based on the shared certificate generation transaction, the sub blockchain 120 may perform a verification query for the transaction.

As such, the relationship between the blocks is not blocked, but the main block chain 110 and the sub block chain 120 may transmit and receive data by the connection node. At least one of the main nodes 111-1 to 111-3 participating in the main blockchain 110 is the main connection node 111-3, and the subnodes 121-1 to ~ participating in the sub blockchain 120. At least one of 121-4) is a sub connection node 121-1, and main and sub connection nodes 111-3 and 121-1 are provided to connect the main and sub block chains with each other.

In this case, connecting to each other may mean exchanging data.

In one embodiment of the present invention, it is proposed to exchange data between the connection nodes only under specific conditions. This is because the main blockchain is a private blockchain, and information stored in the main blockchain should not be disclosed to the outside.

For example, only a predetermined query may be received from the sub blockchain 120, or only data transmission / reception in case of replying to the predetermined query may be performed through the connection node. The preset query and its reply will be described later in detail.

According to an embodiment of the present invention, the main blockchain 110 may be a private blockchain. That is, the main nodes 111-1 to 111-3, which are nodes of the main blockchain 110, are not open to anyone, and only authorized or designated institutions can participate.

On the other hand, the sub blockchain 120 may be a private block chain or a public block chain. Although not completely blocked, it may be a private blockchain in a broad sense, in which only confirmed or authenticated subjects (some preset entities) can participate in a limited way. Accordingly, additional subnodes 122-1, 122-2,..., Subnodes 121-1 through 121-4, which are nodes of the sub blockchain 120, may participate.

As such, the main blockchain 110 and the subblockchain 120 are separated from each other because security for the authentication system is required. According to the blockchain technology, all transactions are open to the public, since the user's authentication or the proof of the document itself must not be open to the public. For example, the proof of graduation document should only be disclosed to the receiving institution (eg, the company wishing to receive a certificate for the applicant) requested by the requestor (eg, the applicant of the company), This is because the information should not be disclosed to third parties such as financial institutions or others.

Another reason why the main block chain 110 and the sub block chain 120 are separated is to ensure the expandability of the receiving institution. In the case of the main blockchain 110, since the content is a private blockchain that should not be disclosed, it is limited in terms of its expandability.

If a company that wants to participate as a node of a blockchain additionally occurs, the system according to an embodiment of the present invention is provided to participate in a node of a subblockchain.

A plurality of organizations (hereinafter, referred to as recipients) for requesting user authentication or requesting first verification of a document may correspond to the subnodes 121-1 to 121-4. That is, the receiving authority may be connected to one subnode in a match, and one receiving node may be connected to one receiving node.

In contrast, a certification authority may be connected to at least one of the plurality of main nodes 111-1 to 111-3 in the main blockchain 110. In other words, one integrated certification authority may use multiple nodes.

Furthermore, the sub blockchain 120 can expand the number of blockchains themselves. As shown in FIG. 2, a plurality of sub blockchains 120-1, 120-2, 120-3,... May be connected to one main block chain 110. At this time, the main connection node 111-3 of the main block chain 110 has a '1 to many' relationship with the plurality of sub connection nodes 121-1, 130-1, and 130-2 in FIG. 2. Each can be connected.

In the following, a specific method of performing first proof of a document and user authentication based on this structure of the present invention will be described.

3 is a diagram illustrating a first proof procedure of a document according to an embodiment of the present invention.

The certificate request server 391 may mean a server managed by a receiving authority (or an individual) who wants to verify the authenticity of a document regarding the requestor 390. For example, the certificate request server 391 may be a server. A server operated by an enterprise, and the requestor 390 may be an applicant applying for employment in the company, and the certificate of graduation to confirm the details of the requestor 390 through the certificate request server 391 in the company. We can assume a situation where we want to verify the authenticity of.

The certification body 393 refers to a subject who performs the corresponding certification, and in the above example, the requesting authority 390 may be a university bachelor's or academic certificate system. The term "certificate authority 393" used in the present invention is merely a term used to easily understand the concept, and it will be apparent that the term may be interpreted as a device, a system, or a server operated by the certification authority 393.

The certificate issuing server 392 is an authority for collectively managing the authentication-related procedures of the plurality of certification authorities 393. The certificate issuing server 392 refers to a subject that issues matters authenticated by the certification authority 393 in a document encrypted. . For example, if each of the numerous universities is a certification authority (393), the certificate issuing server 392 may perform the role of integrating the content confirmed / certified by the number of universities, encrypts it and issues it as a certificate.

However, the present invention is not limited to the certificate issuing server 392 directly generates a certificate, the certificate is issued from a plurality of certification authorities 393, the case where the collection and management of the issued certificate is also included in the present invention. will be.

In addition, although the certificate issuing server 392 may be provided separately from the certification authority 393, the certificate issuing server 392 may be provided as one authority without being distinguished from the certification authority 393.

The term server used in the detailed description for carrying out the present invention is a term that includes both apparatuses capable of transmitting and receiving data on and off-line, and the term server is not limited thereto.

In addition, in the detailed description for carrying out the present invention, the term certificate is a term encompassing all electronic documents that can be issued, distributed, and stored electronically.

According to the existing certification system, the requestor 390 directly requests the graduation certificate document from the certification authority 393 or the certificate issuing server 392, and prints the graduation certificate document to the printer and outputs the graduation certificate document to the receiving institution. It was confirmed by submitting.

According to this existing proof system, there is always a risk of forgery and alteration in the process of the requester's output of the document and submission to the recipient.

However, in one embodiment of the present invention, based on the request of the requester 390, in the institution (for example, the company that wants to check the request details of the requester) using the blockchain technology to verify the certificate It proposes a method of performing and delivering a request for direct certificate issuance.

In operation S301, the requestor 390 requests the certificate request server 391 to generate a document (certificate) to be verified. In operation S302, the certificate request server 391 transmits a request to the certificate issuing server 392. In step S303, the certificate issuing server 392 designates the certificate file name to be generated and returns the specified file name to the certificate request server 391.

In operation S304, the certificate issuing server 392 transmits a request for generating a certificate to the certification authority 393. The certification authority 393 may generate a certificate based on the received request. Subsequently, the certificate issuing server 392 transfers a transaction for generating a certificate to a node of the main blockchain 110 (S305). As described above, the transferred transaction may be stored in the main block as described above, and may be selectively transferred to the sub blockchain 120 and stored in the sub block.

Furthermore, the transaction according to an embodiment of the present invention proposes to be transferred to a subchain and stored in a subblock. This is because the verification is performed in step S307 described later. In this case, the transaction may be transmitted through a connection between the main connection node 111-3 and the sub connection node 121-1. That is, the transaction for generating the certificate may be recorded in the sub block of the sub block chain through the main connection node 111-3 and the sub connection node 121-1 in sequence.

In step S306, the certificate request server 391 continuously checks the generated contract with the certificate issuing server 392. That is, based on the file name returned in step S303, it is continuously checked whether a certificate having the file name is generated. If the certificate generation is confirmed, the verification query is transmitted whether the corresponding certificate has been generated through the sub blockchain 120 (S307). In other words, it verifies that the certificate is correctly generated.

In this case, the checking process (S307) may be performed based on the contents stored in the sub block. That is, a transaction for generating a certificate is stored in a subblock, and verification is performed by checking a transaction recorded in the subblock.

The confirmation result, which is a response to the query, may be returned to the certificate request server 391 again.

The generated certificate is transmitted to the certification authority 393, the certificate issuing server 392, and the certificate request server 391 through steps S308 and S309, and the certificate request server 391 can receive (download) the certificate. When the receipt of the certificate is completed, the certificate request server 391 transmits a receipt completion transaction to the sub node 121-4 in step S310. The transaction thus transmitted will be stored in a sub block of the sub block chain 120.

In step S311, the requestor 390 receives (downloads) a certificate from the certificate request server 391. The certificate request server 391 may transfer a transaction for issuance of the certificate (that is, transfer to the requester) to the sub node 121-4 of the sub block chain 120 (step S312) and store the transaction in the sub block. There will be. In addition, not only the completion of the transfer of the certificate but also all operations such as duplication, destruction or transfer of the certificate may be delivered to the sub node 121-4 in a transaction.

According to the procedure in Fig. 3, the certificate request server 391 receiving the certificate can not only verify with high reliability whether the received certificate has been correctly generated, but also the requestor 390 receives the generated certificate from the receiving authority. It has the advantage that it can be confirmed with high reliability whether it was delivered to the third party, whether or not.

4 is a diagram illustrating a certificate request process between certification authorities according to an embodiment of the present invention.

In some cases, it may be necessary to issue certificates between certification bodies. For example, if a student attending university A applies for college credit, or attends graduate school at university B, he or she may need a certificate of whether he or she is attending university A. Since the certification authorities collectively manage the contents related to certificate issuance through the certificate issuing server 392 described above, the certification authority may proceed slightly differently from the procedure of FIG. 3.

4 illustrates a process in which the first certification authority 393-1 requests a certificate from the second certification authority 393-2 based on the request of the requestor. That is, in the above example, if a student wishing to apply for credit exchange makes a request to university B as a requester, university B may become the first certification authority 393-1, and the requestor is currently attending university A. May be the second certification authority (393-2).

In operation S401, the first certification authority 393-1 transmits a request for generating a certificate to the certificate issuing server 392. The certificate issuing server 392 then designates the certificate file name to be generated, and returns the specified file name to the first certification authority 393-1. In operation S403, the certificate issuing server 392 transmits a certificate generation request to the second certification authority 393-2, and the second certification authority 393-2 generates the requested certificate.

When the certificate is generated, the certificate issuing server 392 may transfer a transaction for generating the certificate to the main node of the main blockchain 110.

In operation S405, the first certification authority 393-1 continuously confirms the generated contract to the certificate issuing server 392. Based on the file name returned in step S402, it is continuously checked whether a certificate having the file name is generated.

In operation S406, the second certification authority 393-2 transmits the generated certificate to the certificate issuing server 392. When the certificate issuing server 392 receives the certificate, the certificate issuing server 392 generates a transaction for receiving the certificate and transfers it to the main node of the main blockchain 110 (step S407).

Subsequently, the certificate issuing server 392 transmits the received certificate to the first certification authority (step S408). When the certificate delivery is completed, a transaction for certificate delivery is generated and delivered to the main node of the main blockchain 110 (step S409).

Hereinafter, a process of performing user authentication using blockchain technology will be described.

5 is a diagram illustrating a user authentication procedure according to an embodiment of the present invention.

The authentication request server 591 may mean a server to perform authentication for the requestor 390, and may mean, for example, a server of a homepage to which the requester 390 wants to subscribe.

The certification authority 393 ′ refers to a subject that performs authentication for the requestor 390. For example, the certification request server 591 may be a student of the requester 390. May request a certification authority 393 '. In this case, the certification body 393 'may be a university bachelor's or academic certificate system for which the requestor 390 graduated. The certification authority 393 ′ may be an organization belonging to the certification authority 393 described above with reference to FIGS. 3 and 4, or may be a separate organization from the certification authority 393.

The integrated authentication server 592 means a subject for collectively managing user authentication related procedures of the plurality of certification authorities 393 '. For example, if each of the numerous universities are called a certification authority 393 ', the integrated authentication server 592 may perform a role of integrating the authentications performed at the numerous universities, encrypting them, and issuing them as user identification information.

In operation S501, the requester 390 may request the authentication request server 591 to generate user identification information. In operation S502, the authentication request server 591 may forward the request to the integrated authentication server 592. have.

The integrated authentication server 592 may transfer the transaction for the above request to the main blockchain 110 (step S503).

Upon receiving the request for generating the user identification information, the integrated authentication server 592 forwards the request to the certification authority 393 'again, and the certification authority 393' performs user authentication (step S504) based on the received request. can do. In the user authentication step of S504, the certification authority 393 'may search the database for the requester 390 and perform an authentication operation. For example, the requestor 390 is a university student, and the certification authority 393 'is a university academic system that performs the academic certification on the requestor 390 through the academic database query and displays the result of the integrated authentication server. 592 can be delivered.

The integrated authentication server 592 may generate user identification information on the user whose authentication has been completed, and may transmit a transaction for generation of the user identification information to the main node of the main blockchain (step S505). Here, the user identification information may mean a unique code assigned to the requester 390, and may mean a user ID (Identication information) or a token value. In this case, the subject generating the user identification information may be the integrated authentication server 592, but the authentication authority 393 'may generate the user identification information and transfer it to the integrated authentication server 592.

On the other hand, the system according to an embodiment of the present invention, as in step S503, the transaction for the request to the first main node (111-1), and the transaction for generating identification information is the second main node (111-). Propose to block by passing to 2). The transaction for generating the identification information may eventually be an authentication response to the S503 request.

In a blockchain system, at least three nodes are basically required. This is because the verification of the newly created block is performed at all nodes together because a majority of the verification results must be exceeded to generate a new block, and two nodes cannot form the majority result. Accordingly, at least three nodes are also necessary in the main blockchain 110 illustrated in FIG. 5.

Since the integrated authentication server 592 plays a role of integrating authentication procedures for numerous certification authorities 393 ', bottlenecks may occur. Therefore, in the present invention, by classifying the types of transactions that may occur in the integrated authentication server 592, one type of transaction is the first main node (111-1), the other type of transaction is the second main node ( 111-2). That is, due to the nature of the blockchain in which at least three nodes are to be formed, the role is to be shared among the nodes in order to alleviate the bottleneck.

The integrated authentication server 592 may transfer the user identification information generated in step S506 to the authentication request server 591. The authentication request server 591 may transmit a transaction for receiving user identification information to a sub node of the sub blockchain (step S507).

In operation S508, the requester 390 may be provided with a user identification number or may be notified (notified) of the fact that the user identification number has been issued.

As described above, an embodiment of a proof system and a control method thereof according to the present invention have been described, which will be described as at least one embodiment, and thus the technical idea and construction and operation of the present invention are not limited. The scope of the technical idea of the present invention is not limited or restricted by the drawings or the description with reference to the drawings. In addition, the concept and embodiment of the present invention presented in the present invention can be used by those skilled in the art as a basis for modifying or designing to other structures for carrying out the same purpose of the present invention. The equivalent structure modified or changed by those skilled in the art to which the present invention pertains is to be bound by the technical scope of the present invention described in the claims, and the spirit or scope of the invention described in the claims. Various changes, substitutions and alterations are possible without departing from the scope of the invention.

Claims (6)

In a system for performing user authentication,
A main block chain composed of a plurality of main nodes;
A sub blockchain composed of a plurality of sub nodes;
An authentication request server for requesting user authentication; And
Including an authentication server for generating user identification information in response to the authentication request from the authentication request server,
The authentication server sends a first transaction related to the authentication request and a second transaction related to generation of the user identification information to a first main node,
The authentication request server transmits a verification query of the generated user identification information to a first sub node.
The second sub node transmits the verification query to the main blockchain through a second main node.
User Authentication System. The method of claim 1,
The main block chain, characterized in that to form a main block based on the received first and second transactions,
User Authentication System. The method of claim 2,
The second main node performs a verification on the received verification query based on the second transaction stored in the main block.
And replying the performed verification result to the second sub node.
User Authentication System. A main block chain composed of a plurality of main nodes;
A sub blockchain composed of a plurality of sub nodes;
An authentication request server for requesting user authentication; And
A control method of a system for performing user authentication including an authentication server generating user identification information in response to an authentication request from the authentication request server,
Sending, by the authentication server, a first transaction relating to the authentication request and a second transaction relating to generation of the user identification information to a first main node;
Transmitting, by the authentication request server, a verification query of the generated user identification information to a first sub node; And
And transmitting, by a second sub node, the verification query to the main blockchain through a second main node.
How to control the user authentication system. The method of claim 4, wherein
The main block chain further comprises the step of forming a main block based on the received first and second transactions,
How to control the user authentication system. The method of claim 5, wherein
Performing, by the second main node, verifying the received verification query based on the second transaction stored in the main block; And
And responding, by the second main node, the performed verification result to the second sub node.
How to control the user authentication system.

Images