Authentication information signature system, authentication information signature program, and authentication information signature method
The authentication information signature system addresses the inconvenience and security issues of conventional electronic signatures by integrating secure authentication and key management without device installation, enhancing user convenience and security through linked authentication and split keys.
Patent Information
- Application Number
- JP2023185493
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-10-30
- Publication Date
- 2024-12-09
- Estimated Expiration
- 2042-03-11
AI Technical Summary
Conventional electronic signature systems require installation of authentication devices and input of authentication information, which impairs convenience and security, especially when managing private keys in IC cards.
An authentication information signature system that integrates a signature processing unit, authentication information issuing unit, and key management device to manage authentication information and private keys without requiring installation on terminal devices, allowing seamless integration and secure signature generation.
This system reduces user burden by eliminating the need for constant input of authentication information while ensuring security through linked authentication information and private keys, with additional security measures like expiration dates and split keys.
Smart Images

Figure 0007596485000001 
Figure 0007596485000002 
Figure 0007596485000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to electronic signature systems. [Background technology]
[0002] In electronic signatures using public key cryptography, a private key is used to generate an electronic signature, and a public key is used to verify the authenticity of the electronic signature. An electronic signature has the same meaning as a handwritten signature in that only the owner of the private key used to generate the signature can possess it. In an electronic signature system, in order to equip a terminal device with a highly secure personal authentication function based on possessions or biometrics, etc., installation work was previously required; however, by providing a separate authentication device, it is possible to provide the electronic signature system with a highly secure personal authentication function without performing installation work on the terminal device (Patent Document 1). [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2010-81418 A Summary of the Invention [Problem to be solved by the invention]
[0004] The method of Patent Document 1 requires the input of authentication information when signing, which reduces convenience. Furthermore, in conventional electronic signatures, in order to strictly manage the private key, it is stored together with the electronic certificate on an IC (Integrated Circuit) card, etc. Managing the private key on an IC card can ensure a certain level of security, but it requires the user to always carry the IC card and have the private key read by an IC card reader, which still poses a problem in terms of convenience. The present disclosure has been made to improve convenience when signing in an electronic signature system that can be used without installing the system on a terminal device. By linking authentication information to a private key for signing, it becomes possible to use an IC card at all times and to omit the need to enter authentication information when signing, thereby reducing the burden on users when signing while ensuring security. [Means for solving the problem]
[0005] The authentication information signature system disclosed herein includes a signature processing unit that accepts received data including a signature request from a terminal device operated by a signature requesting user who requests a signature and determines whether the received data includes authentication information, and an authentication information issuing unit that issues authentication information corresponding to the signature requesting user and transmits it to the terminal device when the signature processing unit determines that the received data does not include authentication information, and the signature processing unit again accepts the received data including the signature request and the authentication information issued by the authentication information issuing unit from the terminal device. Effect of the Invention
[0006] According to the present disclosure, in an electronic signature system that can be used without installation on a terminal device, it is possible to reduce the burden on a user when signing while ensuring safety. [Brief description of the drawings]
[0007] [Figure 1] FIG. 1 is a configuration diagram of an authentication information signature system according to a first embodiment. [Diagram 2] FIG. 2 is a functional configuration diagram of the authentication information signature system according to the first embodiment. [Diagram 3] FIG. 2 is a hardware configuration diagram of the authentication information signature system according to the first embodiment. [Figure 4] FIG. 2 is a data structure diagram of the authentication information signature system according to the first embodiment. [Diagram 5] FIG. 4 is a flowchart of a signature process according to the first embodiment. [Figure 6] FIG. 4 is a flow diagram of authentication information issuing processing according to the first embodiment. [Figure 7]FIG. 2 is a hardware configuration diagram of an authentication information signature system according to a first modification of the first embodiment. [Figure 8] FIG. 11 is a functional configuration diagram of an authentication information signature system according to a second embodiment. [Figure 9] FIG. 11 is a data structure diagram of an authentication information signature system according to the second embodiment. [Figure 10] FIG. 11 is a functional configuration diagram of an authentication information signature system according to a third embodiment. [Figure 11] FIG. 11 is a data structure diagram of an authentication information signature system according to the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0008] Embodiment 1 In the first embodiment, a process of performing a signature in an authentication information signature system which is a system configuration including a terminal device, an authentication device, a signature device, and a key management device will be described. In this embodiment, the data to be signed is some kind of electronic file, and may have any configuration as long as it is configured to allow a digital signature to be added. The signature key, which is the private key used for signing, is assumed to be prepared in advance by the system administrator. The signature process involves signing data to be signed with a signature key to generate a signature value, and linking the data to be signed with the generated signature value to generate signature data. The authentication information is information required for user authentication, which is issued for each logged-in user of a terminal device. To enhance security, the authentication information may be encrypted and decrypted when used. A specific example of the authentication information is a token. The token includes an ID (Identification) token that contains information about the user, such as the user name and user attributes, and an access token that contains information about the user's access rights.
[0009] ***Configuration of the First Embodiment*** FIG. 1 is a configuration diagram of an authentication information signature system 1. As shown in FIG. The authentication information signature system 1 comprises a network 2, a terminal device 10, an authentication device 20, a signature device 30, and a key management device 40. The authentication information signature system 1 may have other configurations.
[0010] FIG. 2 is a functional configuration diagram showing the functional configuration of the system. The terminal device 10 includes a storage unit 11, a communication unit 12, and an input / output unit 13. Signature target data 111 and authentication information 112 are stored in the storage unit 11. The input / output unit 13 receives a signature request from a signature requesting user and displays the result of the signature processing to the signature requesting user. In this embodiment, the input / output unit 13 operates on a web browser. The authentication device 20 includes a storage unit 21, a communication unit 22, an authentication information issuing unit 23, and an authentication information verifying unit 24. The storage unit 21 stores user management data 211. The authentication information issuing unit 23 issues authentication information 112. The authentication information verifying unit 24 verifies the authentication information 112. The signature device 30 includes a storage unit 31, a communication unit 32, and a signature processing unit 33. The signature processing unit 33 performs signature processing. The key management device 40 includes a storage unit 41, a communication unit 42, a signature value generation unit 43, and a key management unit 44. A signature key 411 and key management data 412 are stored in the storage unit 41. The signature value generation unit 43 generates a signature value. The key management unit 44 obtains data from the key management data. The communication unit of each device communicates with other devices via network 2 based on the information required for communication. The memory unit of each device stores data received from other devices via the communication unit. Although not shown, it is assumed that the memory unit of each device stores information required for communication, such as the IP (Internet Protocol) address of each device.
[0011] Each function of the authentication information signature system 1 configured as above is realized by hardware as shown in Fig. 3. This hardware is configured such that a processing device 101 such as a CPU (CENTRAL PROCESSING UNIT), a storage device 102 such as a ROM (READ ONLY MEMORY) or a hard disk device, a communication device 103 connected to other hardware via a network 2, and input / output devices 104 such as a keyboard, a mouse, a speaker, a display, etc. are connected by a bus. The CPU may have its own memory. There may be a plurality of processing devices 101, and the plurality of processing devices 101 may cooperate to execute programs for realizing the respective functions. In addition, in embodiment 1, the terminal device 10 is equipped with a processing device 101, a storage device 102, a communication device 103, and an input / output device 104, and the authentication device 20, the signature device 30, and the key management device 40 are each equipped with a processing device 101, a storage device 102, and a communication device 103.
[0012] FIG. 4 is a data structure diagram. The authentication information 112 includes an authentication information ID for identifying the authentication information, a user ID for identifying the signature requesting user who has requested the issuance of the authentication information, and the expiration date of the issued authentication information. The user management data 211 includes items such as a user ID for identifying a signature requesting user and a password of the signature requesting user. The key management data 412 consists of items: a user ID for identifying the signature requesting user who uses the signature key, and a user signature key for storing the signature key itself. As will be described later, the user management data 211 and the key management data 412 are information that is set in advance by a system administrator. Here, the authentication information 112 includes an authentication information ID "T001", a user ID "U001", and an expiration date "2022 / 3 / 30 18:00". It is assumed that the user ID "U001" and password "P001" are registered as the user management data 211. It is assumed that data on a user ID "U001" and a user signature key "signature key 411" are registered as key management data 412.
[0013] ***Operation of the First Embodiment*** FIG. 5 is a flow diagram of the signature process. The operation of the signature process of the authentication information signature system 1 will be described with reference to this flow diagram. In this process, signature data is generated upon receiving a signature request from a signature requesting user who requests a signature at the terminal device 10. The user ID of the signature requesting user is assumed to be "U001". The operation procedure of the authentication information signature system 1 according to the embodiment 1 corresponds to the authentication information signature method according to the embodiment 1. Moreover, the program that realizes the operation of the authentication information signature system 1 according to the embodiment 1 corresponds to the authentication information signature program according to the embodiment 1.
[0014] When input / output unit 13 of terminal device 10 receives a signature request from a signature requesting user specifying user ID "U001" and signature target data 111, input / output unit 13 acquires authentication information 112 from storage unit 11. Thereafter, input / output unit 13 uses communication unit 12 to transmit the signature request to signature device 30 together with user ID "U001", the acquired signature target data 111, and authentication information 112 (step S101). In addition, when authentication information has not been issued and authentication information 112 is not stored in memory unit 11, such as during the initial signature process, input / output unit 13 uses communication unit 12 to transmit data to be signed 111 and a signature request to signature device 30. The user ID may also be obtained from the login information of the terminal device 10.
[0015] Upon receiving the signature request via the communication unit 32, the signature processing unit 33 checks whether or not authentication information is included in the received data. If the authentication information is present, the signature processing unit 33 stores the received signature target data 111 in the storage unit 31 . If the authentication information is not present, the process proceeds to step S201 (step S102), which will be described later.
[0016] Next, the signature processing unit 33 uses the communication unit 32 to transmit a signature value generation request to the key management device 40 together with the received user ID "U001", the signature target data 111, and the authentication information 112 (step S103).
[0017] The signature value generation unit 43, which has received the signature value generation request through the communication unit 42, stores the received signature target data 111 in the storage unit 41. Thereafter, the signature value generation unit 43 uses the communication unit 42 to transmit an authentication information verification request together with the received user ID "U001" and authentication information 112 to the authentication device 20 (step S104).
[0018] The authentication information verification unit 24, which receives the authentication information verification request through the communication unit 22, performs authentication information verification processing. The authentication information verification process may be performed as follows. The expiration date "2022 / 3 / 30 18:00" is obtained from the received authentication information 112. After that, the expiration date is compared with the current date and time, and if the expiration date has not expired, i.e., if the current date and time is within the expiration date and time, the result of the authentication information verification process is determined to be "success", and otherwise the result of the authentication information verification process is determined to be "failure". The result of the authentication information verification process is information for authorizing the generation of a signature value, and if "successful", it authorizes the generation of a signature value, and if "failed", it does not authorize the generation of a signature value. As the authentication information verification process, a comparison may be additionally performed to determine whether the user ID included in the authentication information 112 is the same as the received user ID. If the result of the authentication information verification process is "success", the authentication information verification unit 24 acquires the user ID "U001" included in the authentication information. After that, the authentication information verification unit 24 uses the communication unit 22 to transmit the authentication information verification result "success" and the acquired user ID "U001" to the key management device 40 as a response to the authentication information verification request. If the result of the authentication information verification process is "failed", the authentication information verification unit 24 uses the communication unit 22 to transmit the authentication information verification result "failed" as a response to the authentication information verification request to the key management device 40 (step S105).
[0019] The signature value generating unit 43 receives the response to the authentication information verification request through the communication unit 42 and acquires the authentication information verification result from the response to the authentication information verification request. If the authentication information verification result is "success", generation of a signature value is permitted, and so the signature value generation unit 43 obtains the user ID "U001" from the authentication information verification request response. The signature value generation unit 43 then uses the obtained user ID "U001" to obtain the signature key 411 corresponding to the user ID "U001" from the key management data 412. The signature value generation unit 43 then obtains the signature target data 111 from the storage unit 41. The signature value generation unit 43 then signs the signature target data 111 with the signature key 411 to generate a signature value. The signature value generation unit 43 then uses the communication unit 42 to transmit the processing result "success" and the generated signature value to the signature device 30 as a signature value generation request response. If the authentication information verification result is “failed”, generation of a signature value is not permitted, so the signature value generation unit 43 uses the communication unit 42 to send the processing result “failed” to the signature device 30 as a response to the signature value generation request (step S106).
[0020] The signature processing unit 33 receives the signature value generation request response via the communication unit and obtains the processing result from the signature value generation request response. If the processing result is "success", signature processing unit 33 obtains the signature value from the signature value generation request response. Thereafter, signature processing unit 33 obtains signature target data 111 from memory unit 31. Thereafter, signature processing unit 33 links signature target data 111 with the signature value to generate signature data. Thereafter, signature processing unit 33 uses communication unit 32 to transmit the processing result "success" and the generated signature data as a signature request response to terminal device 10. If the processing result is "failed", signature processing unit 33 uses communication unit 32 to transmit the processing result "failed" as a signature request response to terminal device 10 (step S107).
[0021] Input / output unit 13 receives the signature request response via communication unit 12 and obtains the processing result from the signature request response. If the processing result is "success", input / output unit 13 acquires signature data from the signature request response. Then, input / output unit 13 stores the acquired signature data in storage unit 11. Then, input / output unit 13 ends the processing with the processing result being "success". If the processing result is "failure", the input / output unit 13 ends the processing as a "failure" processing result (step S108).
[0022] FIG. 6 is a flow diagram of the authentication information issuing process. The operation of the authentication information issuing process will be described with reference to this flow diagram. This process is performed when there is no authentication information in step S102.
[0023] If the authentication information is not present in step S102, the signature processing unit 33 of the signature device 30 transmits an authentication information sending request to the terminal device 10 together with information on a predetermined authentication information acquisition destination (step S201). The authentication information is acquired from the authentication device 20.
[0024] The input / output unit 13 of the terminal device 10 that has received the authentication information sending request through the communication unit 12 acquires information on the authentication information acquisition destination from the received authentication information sending request. After that, the input / output unit 13 uses the communication unit 12 to transmit an authentication information issue request to the authentication device 20 that is the authentication information acquisition destination (step S202). This process may be performed by opening the redirect URL in a web browser.
[0025] The authentication information issuing unit 23, which has received the authentication information issuance request via the communication unit 22, uses the communication unit 22 to transmit login screen information as a response to the authentication information issuance request to the terminal device 10 (step S203). This process may send the URL of the login screen as the login screen information.
[0026] The input / output unit 13, which has received the authentication information issuance request response via the communication unit 12, acquires login screen information from the authentication information issuance request response. Thereafter, the input / output unit 13 displays a login screen from the login screen information. Thereafter, the input / output unit 13 acquires user identification information entered by the signature requesting user from the login screen. Thereafter, the input / output unit 13 transmits an authentication information issuance request together with the user identification information to the authentication device 20 using the communication unit 12 (step S204). The user identification information includes a user ID and a password. This process may be performed by opening the URL of the login screen in a web browser.
[0027] The authentication information issuing unit 23, which has received an authentication information issuance request through the communication unit 22, acquires user identification information from the received authentication information issuance request. Then, the authentication information issuing unit 23 acquires a user ID and a password from the user identification information. Then, the authentication information issuing unit 23 uses the user ID and the password to determine whether or not a combination of the same user ID and password is registered in the user management data 211. If the same user ID and password combination is registered, user authentication is successful. In other cases, the user authentication is deemed to have "failed." If the user authentication is "successful", the authentication information issuing unit 23 issues a new authentication information ID that identifies the authentication information. After that, the authentication information issuing unit 23 determines the expiration date according to the expiration date setting rule. After that, the authentication information issuing unit 23 issues authentication information 112 including the newly issued authentication information ID, the acquired user ID, and the determined expiration date. After that, the authentication information issuing unit 23 uses the communication unit 22 to transmit an authentication information issuance request response to the terminal device 10 together with the acquired user ID and the issued authentication information 112. If the user authentication is "failed", the process ends (step S205). In addition, the expiration date setting rule may determine the expiration date to be a fixed time such as 8 hours after the current date and time, or may determine the expiration date to be a specified date and time such as until 6:00 p.m. on the current day.
[0028] Input / output unit 13, which has received the authentication information issuance request response via communication unit 12, acquires authentication information 112 from the received authentication information issuance request response. Input / output unit 13 then stores the acquired authentication information 112 in memory unit 11. Input / output unit 13 then acquires signature target data 111 from memory unit 11. Input / output unit 13 then uses communication unit 12 to transmit a signature request to signature device 30 together with the received user ID, the acquired signature target data 111, and the received authentication information 112 (step S206).
[0029] When performing the authentication information issuing process, additional authentication such as FIDO authentication may be performed to enhance security and confirm the validity of the user identification information.
[0030] ***Advantages of the First Embodiment*** By linking authentication information to the private key used for signing, it becomes possible to omit the need to input authentication information each time a signature is made, thereby ensuring security while reducing the burden on the user when signing and ensuring security at the same time. In addition, there is no need to always carry an IC card or the like in which the private key is stored. Furthermore, since the authentication information 112 has an expiration date, a certain level of security can be ensured against leakage of the authentication information 112.
[0031] ***Other configurations*** <Variation 1> In the first embodiment, each functional component is realized by software. However, as a first modification, each functional component may be realized by hardware. The following describes the first modification in terms of differences from the first embodiment.
[0032] The configuration of an authentication information signature system 1 according to the first modification will be described with reference to FIG. When each functional component is realized by hardware, an electronic circuit 105 is provided instead of the processing device 101 and the storage device 102. The electronic circuit 105 is a dedicated circuit for realizing the functions of the processing device 101 and the storage device 102.
[0033] The electronic circuit 105 may be a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, a logic IC (INTEGRATED CIRCUIT), a GA (GATE ARRAY), an ASIC (APPLICATION SPECIFIC Examples of such devices include integrated circuits (ICs) and field-programmable gate arrays (FPGAs). Each functional component may be realized by one electronic circuit 105, or each functional component may be distributed across multiple electronic circuits 105.
[0034] <Variation 2> As a second modification, some of the functional components may be realized by hardware, and other functional components may be realized by software.
[0035] The processing device 101, the storage device 102, and the electronic circuit 105 are collectively referred to as a processing circuit. In other words, the functions of the respective functional components are realized by the processing circuit.
[0036] <Variation 3> As a third modification, some or all of the functions of authentication device 20, signature device 30, and key management device 40 of authentication information signature system 1 may be integrated into a single device.
[0037] <Modification 4> As a fourth modification, some or all of the functions of the authentication information signature system 1 may be realized on a cloud server.
[0038] Embodiment 2 In the first embodiment, the process when the authentication information 112 includes information required for user authentication has been described. In the second embodiment, the authentication information 112 includes only an authentication information ID for identifying the authentication information, and the information required for user authentication is managed in the authentication information management data 212. The second embodiment will describe the differences from the first embodiment with respect to the process.
[0039] FIG. 8 is a functional configuration diagram showing the functional configuration of the system. The storage unit 21 of the authentication device 20 stores authentication information management data 212. The other configurations are the same as those in the first embodiment.
[0040] FIG. 9 is a data structure diagram. The authentication information 112 includes an authentication information ID that identifies the authentication information. The authentication information management data 212 includes items such as an authentication information ID, a user ID for identifying the signature requesting user who has requested the issuance of the authentication information, and the expiration date of the issued authentication information. As will be described later, the authentication information management data 212 is information generated by the authentication information issuing unit 23 when the authentication information is issued. The user management data 211 and the key management data 412 are the same as those in the first embodiment.
[0041] ***Operation of the Second Embodiment*** The operation of the signature process of the authentication information signature system 1 will be described with reference to the flow diagram of FIG. In this process, signature data is generated upon receiving a signature request from a signature requesting user who requests a signature at the terminal device 10. The user ID of the signature requesting user is assumed to be "U001". Steps other than step S105 are the same as those in the first embodiment.
[0042] The authentication information verification unit 24, which receives the authentication information verification request through the communication unit 22, performs authentication information verification processing. The authentication information verification process may be performed as follows. The authentication information ID "T001" included in the authentication information 112 is obtained. Then, using the obtained authentication information ID, the user ID "U001" and the expiration date "2022 / 3 / 30 18:00" are obtained from the authentication information management data 212. Then, the expiration date is compared with the current date and time, and if the expiration date has not expired, the result of the authentication information verification process is determined to be "success", and otherwise the result of the authentication information verification process is determined to be "failure". If the result of the authentication information verification process is "success", the authentication information verification unit 24 uses the communication unit 22 to notify the user of the authentication information verification result "success" and the user ID "U001" acquired in the authentication information verification process. is transmitted to the key management device 40 as a response to the authentication information verification request. If the result of the authentication information verification process is "failed", the authentication information verification unit 24 uses the communication unit 22 to transmit the authentication information verification result "failed" as a response to the authentication information verification request to the key management device 40 (step S105).
[0043] Next, the operation of the authentication information issuing process will be described with reference to the flow diagram of FIG. This process is performed when there is no authentication information in step S102. Steps other than step S205 are the same as those in the first embodiment.
[0044] The authentication information issuing unit 23, which has received an authentication information issuance request through the communication unit 22, acquires user identification information from the received authentication information issuance request. Then, the authentication information issuing unit 23 acquires a user ID and a password from the user identification information. Then, the authentication information issuing unit 23 uses the user ID and the password to determine whether or not a combination of the same user ID and password is registered in the user management data 211. If the same user ID and password combination is registered, the user authentication is deemed "successful"; otherwise, the user authentication is deemed "failed." If the user authentication is "successful", the authentication information issuing unit 23 issues a new authentication information ID that identifies the authentication information. After that, the authentication information issuing unit 23 determines the expiration date according to the expiration date setting rule. After that, the authentication information issuing unit 23 generates authentication information management data 212 from the newly issued authentication information ID, the acquired user ID, and the determined expiration date. After that, the authentication information issuing unit 23 issues authentication information 112 including the newly issued authentication information ID. After that, the authentication information issuing unit 23 uses the communication unit 22 to transmit the acquired user ID and the issued authentication information 112 to the terminal device 10. If the user authentication is "failed", the process ends (step S205).
[0045] ***Effects of the second embodiment*** By including only the authentication information ID in the authentication information 112, the risk of information leakage due to leakage of the authentication information 112 can be reduced, and security can be improved.
[0046] Embodiment 3 In the first embodiment, the process of signing using one signature key has been described. In the third embodiment, differences from the first embodiment will be described with regard to the process of signing using signature keys (split keys) generated by dividing one signature key. Split keys are multiple signing keys generated by dividing a single signing key. By signing with all the split keys, the same signature value can be generated as if the signing key before being divided was used. In this embodiment, two signature keys are used, which are generated by dividing one signature key, the first signature key 213 and the second signature key 413. The first signature key 213 and the second signature key 413 are assumed to be prepared in advance by a system administrator.
[0047] ***Configuration of the Third Embodiment*** The configuration of the third embodiment is similar to that of the first embodiment. Although it is possible to combine the functions of each device into a single device, in order to reduce the risk of the signature key being leaked, it is desirable to store the first signature key 213 and the second signature key 413 in separate devices.
[0048] FIG. 10 is a functional configuration diagram showing the functional configuration of the system. The authentication device 20 includes a first signature value generation unit 25. A first signature key 213 is stored in the storage unit 21. The first signature value generation unit 25 generates a signature value. The other configurations are the same as those in the first embodiment. The key management device 40 includes a storage unit 41, a communication unit 42, a key management unit 44, and a second signature value generation unit 45. The storage unit 41 stores key management data 412 and a second signature key 413. The second signature value generation unit 45 generates a signature value.
[0049] FIG. 11 is a data structure diagram. The key management data 412 consists of items: a user ID for identifying the signature requesting user who uses the signature key, a first key ID for identifying the signature key, and a second signature key for storing the signature key itself. Here, it is assumed that the following data is registered as the key management data 412: a user ID "U001", a first key ID "K001", and a second signature key "second signature key 413". The key ID “K101” is the key ID that indicates the first signature key 213. The user management data 211 is the same as in the first embodiment.
[0050] ***Operation of the Third Embodiment*** The operation of the signature process of the authentication information signature system 1 will be described with reference to the flow diagram of FIG. In this process, signature data is generated upon receiving a signature request from a signature requesting user who requests a signature at the terminal device 10. The user ID of the signature requesting user is assumed to be "U001". Steps S101 to S103 and step S108 are the same as those in the first embodiment.
[0051] The signature value generation unit 43, which has received the signature value generation request through the communication unit 42, stores the received signature target data 111 in the storage unit 41. Thereafter, the signature value generation unit 43 uses the received user ID "U001" to obtain the first key ID "K101" corresponding to the user ID "U001" from the key management data 412. Thereafter, the signature value generation unit 43 uses the communication unit 42 to transmit an authentication information verification request to the authentication device 20 together with the received user ID "U001", the obtained first key ID "K101", the signature target data 111, and the authentication information 112 (step S104).
[0052] The authentication information verification unit 24, which receives the authentication information verification request through the communication unit 22, performs authentication information verification processing. The authentication information verification process may be performed as follows. The expiration date "2022 / 3 / 30 18:00" is obtained from the received authentication information 112. After that, the expiration date is compared with the current date and time, and if the expiration date has not expired, the result of the authentication information verification process is determined to be "success", and otherwise the result of the authentication information verification process is determined to be "failure". If the result of the authentication information verification process is "success", the first signature value generation unit 25 performs a first signature value generation process. The first signature value generation process may be performed as follows. Based on the received first key ID "K101", the first signature key 213 corresponding to the first key ID is obtained from among the signature keys stored in the memory unit 21. After that, the first signature value generation unit 25 signs the received signature target data 111 with the first signature key 213, and generates a first signature value. Next, the authentication information verification unit 24 uses the communication unit 22 to transmit the authentication information verification result "success", the received user ID "U001", and the generated first signature value to the key management device 40 as a response to the authentication information verification request. If the result of the authentication information verification process is "failed", the authentication information verification unit 24 uses the communication unit 22 to transmit the authentication information verification result "failed" as a response to the authentication information verification request to the key management device 40 (step S105).
[0053] The signature value generating unit 43 receives the response to the authentication information verification request through the communication unit 42 and acquires the authentication information verification result from the response to the authentication information verification request. If the authentication information verification result is "success", the signature value generation unit 43 uses the received user ID "U001" to obtain the second signature key 413 corresponding to the user ID "U001" from the key management data 412. The signature value generation unit 43 then obtains the first signature value from the authentication information verification request response. The signature value generation unit 43 then signs the obtained first signature value with the second signature key 413 to generate a second signature value. The signature value generation unit 43 then uses the communication unit 42 to transmit the processing result "success" and the generated second signature value to the signature device 30 as a signature value generation request response. If the authentication information verification result is "failed", signature value generation unit 43 uses communication unit 42 to transmit the processing result "failed" as a response to the signature value generation request to signature device 30 (step S106).
[0054] The signature processing unit 33 receives the signature value generation request response via the communication unit and obtains the processing result from the signature value generation request response. If the processing result is "success", signature processing unit 33 obtains the second signature value from the signature value generation request response. Thereafter, signature processing unit 33 obtains signature target data 111 from memory unit 31. Thereafter, signature processing unit 33 links signature target data 111 with the second signature value to generate signature data. Thereafter, signature processing unit 33 uses communication unit 32 to transmit the processing result "success" and the generated signature data to terminal device 10 as a signature request response. If the processing result is "failed", signature processing unit 33 uses communication unit 32 to transmit the processing result "failed" as a signature request response to terminal device 10 (step S107).
[0055] ***Effects of the Third Embodiment*** By splitting the signing key, the risk of the signing key being leaked can be reduced compared to when there is only one signing key, thereby increasing security.
[0056] In addition, the word "part" in the above description may be read as a "circuit," "step," "procedure," "processing," or "processing circuit."
[0057] The above describes the embodiments and modifications of the present disclosure. Some of these embodiments and modifications may be combined and implemented. Also, one or some of them may be partially implemented. Note that the present disclosure is not limited to the above embodiments and modifications, and various modifications are possible as necessary. [Explanation of symbols]
[0058] 1 authentication information signature system, 2 network, 10 terminal device, 11 memory unit, 12 communication unit, 13 input / output unit, 20 authentication device, 21 memory unit, 22 communication unit, 23 authentication information issuing unit, 24 authentication information verifying unit, 25 first signature value generation unit, 30 signature device, 31 memory unit, 32 communication unit, 33 signature processing unit, 40 key management device, 41 memory unit, 42 communication unit, 43 signature value generation unit, 44 key management unit, 45 second signature value generation unit, 101 processing device, 102 storage device, 103 communication device, 104 input / output device, 105 electronic circuit, 111 data to be signed, 112 authentication information, 211 user management data, 212 authentication information management data, 213 first signature key, 411 signature key, 412 key management data, 413 second signature key.
Claims
1. a signature processing unit that receives received data including at least a signature request and a signature requesting user ID input by a signature requesting user from a terminal device operated by the signature requesting user and determines whether or not the received data includes authentication information including an authentication information user ID for identifying the signature requesting user; an authentication information verification unit that verifies whether or not the signature requesting user ID and an authentication information user ID included in the authentication information are identical when the signature processing unit determines that the authentication information is included in the received data; an authentication information issuing unit that issues authentication information corresponding to the signature requesting user and transmits the authentication information to the terminal device when the signature processing unit determines that the authentication information is not included in the received data; Equipped with when the authentication information verification unit verifies that the signature requesting user ID and the authentication information user ID are identical, the signature processing unit generates signature data using the signature requesting user ID; when receiving data including the signature request and the authentication information issued by the authentication information issuing unit from the terminal device again, generating signature data using the signature requesting user ID; Credential signing system.
2. The authentication information generated by the authentication information issuing unit includes an authentication information ID, the authentication information user ID, and an expiration date, the authentication information ID is uniquely generated for each authentication information, the signature requesting user ID is set as the authentication information user ID when the signature requesting user ID is identical to any user ID registered in user management data which is information for identifying a user, and the expiration date is set to a period after a certain time from the time of issuance or until a specified date and time.
2. The authentication information signing system of claim 1.
3. The authentication information verification unit further The expiration date of the authentication information is obtained, and if the obtained expiration date has not expired, the authentication information is successfully verified; 3. The authentication information signing system of claim 2.
4. moreover, a signature value generation unit that generates a signature value by signing with a user signature key, which is a private key for signing of the signature requesting user, when the verification by the authentication information verification unit is successful; 4. The authentication information signing system of claim 3.
5. the terminal device includes an input / output unit for acquiring the signature-requested user ID of the signature-requested user from login information of the signature-requested user to the terminal device, The authentication information issuing unit, When a request for issuing authentication information is received from the signature processing unit based on a determination that the authentication information is not included in the received data, It is determined whether or not the same ID as the signature requesting user ID is registered in any of the user IDs in the user management data, and if it is determined that the ID is registered, the authentication information is issued.
5. The authentication information signing system of claim 4.
6. The authentication information issuing unit, When the authentication information issuance request is received together with the signature requesting user ID of the signature requesting user, A new authentication information ID is issued and the expiration date is determined. The authentication information including the newly issued authentication information ID, user identification information for identifying the signature requesting user, and the determined expiration date is issued.
6. The authentication information signing system of claim 5.
7. The authentication information issuing unit, When the authentication information issuance request is received together with the signature requesting user ID of the signature requesting user, A new authentication information ID is issued and the expiration date is determined. generating authentication information management data including the authentication information ID, information about the signature requesting user, and the expiration date; The authentication information including the newly issued authentication information ID is issued.
6. The authentication information signing system of claim 5.
8. The authentication information verification unit obtaining the authentication information ID based on the authentication information; The expiration date is obtained from the authentication information management data by using the obtained authentication information ID; If the acquired expiration date has not expired, the verification of the authentication information is successful.
8. The authentication information signing system of claim 7.
9. the user signature key is composed of a first signature key and a second signature key; a first signature value generation unit that generates a signature value by signing with the first signature key; a second signature value generation unit that generates a signature value by signing with the second signature key, When the authentication information verification unit has successfully verified the authentication information, The first signature value generation unit and the second signature value generation unit perform signing to generate a signature value.
9. An authentication information signing system according to any one of claims 4 to 8.
10. The authentication information signing system is built on a cloud server. An authentication information signing system according to any one of claims 1 to 9.
11. A signature process in which a computer receives received data including at least a signature request and a signature requesting user ID input by a signature requesting user from a terminal device operated by the signature requesting user, and determines whether the received data includes authentication information including an authentication information user ID that identifies the signature requesting user; an authentication information verification process for verifying whether or not the signature requesting user ID is identical to an authentication information user ID included in the authentication information when it is determined in the signature process that the authentication information is included in the received data; an authentication information issuing process for issuing authentication information corresponding to the signature requesting user and transmitting the authentication information to the terminal device when it is determined in the signature process that the authentication information is not included in the received data; Run the command, the signature processing generates signature data using the signature requesting user ID when the authentication information verification processing verifies that the signature requesting user ID and the authentication information user ID are identical; when receiving data including the signature request and the authentication information issued in the authentication information issuing process from the terminal device again, generating signature data using the signature requesting user ID; Credential signing program.
12. An authentication information signing method executed by a computer of an authentication information signing system, comprising: a signature processing step of receiving received data including at least a signature request and a signature requesting user ID input by a terminal device operated by a signature requesting user who requests a signature, and determining whether or not the received data includes authentication information including an authentication information user ID including an authentication information user ID that identifies the signature requesting user; an authentication information verification step of verifying whether or not the signature requesting user ID and an authentication information user ID included in the authentication information are identical when the signature processing step determines that the authentication information is included in the received data; an authentication information issuing step of issuing authentication information corresponding to the signature requesting user and transmitting the authentication information to the terminal device when it is determined in the signature processing step that the authentication information is not included in the received data; having When it is verified in the authentication information verification step that the signature requesting user ID and the authentication information user ID are identical, signature data is generated using the signature requesting user ID, when receiving data including the signature request and the authentication information issued in the authentication information issuing step from the terminal device again in the signature processing step, generating signature data using the signature requesting user ID. Credential signing method.
Citation Information
Patent Citations
Electronic signature system, electronic signature method, authentication device and program
JP2010081418A
Signature device
JP2010154098A
Encryption system, encryption device, encryption program, and encryption method
JP2018029268A
Key management system, signing device, method for managing key, and program
JP2021040278A
Electronic signature system
JP2021111925A
