Information processing system, information processing device, and information processing method

Abstract

To prevent an incorrect signature in electronic signature.SOLUTION: A signature application server 40 displays a signature instruction screen including a document ID corresponding to signature target data on a signer operation terminal 13, receives a signature instruction from the signer operation terminal 13, and transmits a signature approval request including information on the document ID to an authentication and approval server 20. The authentication and approval server 20 displays a signature intention confirmation screen including the document ID on a signer approval terminal 11 upon receiving the signature approval request from the signature application server 40, and generates a token to permit use of a signature key and transmits the token to the signature application server 40 when a signature intention confirmation result is received from the signer approval terminal 11.SELECTED DRAWING: Figure 12

Description

[Technical Field]

[0001] The present invention relates to a system, an apparatus and a method for performing information processing to implement a digital signature for an electronic file. [Background technology]

[0002] Conventionally, electronic signatures that affix an electronic signature to an electronic file such as a contract have been widely used for the purposes of identity verification and prevention of tampering with the electronic file. For example, Patent Document 1 describes a technology that affixes an electronic signature to an electronic contract to which video conference data that uniquely represents the content of a video conference held between the parties to the contract is attached, thereby verifying not only identity verification and non-tampering but also the authenticity of the establishment of the electronic contract. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2022-134582 Summary of the Invention [Problem to be solved by the invention]

[0004] When applying an electronic signature to an electronic file, it is necessary to reliably prevent the signer from accidentally signing an electronic file that is different from the one originally intended (mis-signing). However, the technology described in Patent Document 1 is a technology for verifying the authenticity of the establishment of an electronic contract, and therefore cannot prevent mis-signing.

[0005] The present invention has been made in light of the above background, and has as its object to prevent erroneous signing with electronic signatures. [Means for solving the problem]

[0006] An information processing system according to the present invention comprises a signature application server connected to a first terminal device and receiving a signature instruction for data to be signed selected by a signer on the first terminal device, an authentication and authorization server having information on a signature key owned by the signer, and a remote signature server that uses the signature key to digitally sign the data to be signed and generates a signature value indicating that the data to be signed has been signed by the signer, wherein when the signer selects the data to be signed, the signature application server causes the first terminal device to display a signature instruction screen including a document ID corresponding to the data to be signed, and the signature application server receives the signature instruction from the first terminal device on which the signature instruction screen is displayed. and transmits a signature authorization request including information about the document ID to the authentication and authorization server, and upon receiving the signature authorization request from the signature application server, the authentication and authorization server displays a signing intention confirmation screen including the document ID on a second terminal device, and upon receiving a signing intention confirmation result transmitted from the second terminal device when the signer performs a predetermined operation on the second terminal device on which the signing intention confirmation screen is displayed, the authentication and authorization server generates a token for authorizing use of the signature key and transmits it to the signature application server, and upon receiving the token from the signature application server, the remote signature server digitally signs the data to be signed to generate the signature value. An information processing device according to the present invention comprises a storage device that stores information on a signing key owned by a signer; a signing intention confirmation request unit that, in response to a signature authorization request from the signer for data to be signed selected by the signer, causes a terminal device to display a signing intention confirmation screen including a document ID corresponding to the data to be signed; and a signature authorization unit that generates a token for authorizing the use of the signing key in response to a signing intention confirmation result sent from the terminal device when the signer performs a predetermined operation on the terminal device on which the signing intention confirmation screen is displayed. An information processing method according to the present invention is an information processing method using a first terminal device, a second terminal device, a signature application server that receives a signing instruction for data to be signed selected by a signer, an authentication and authorization server that has information on a signature key owned by the signer, and a remote signature server that digitally signs the data to be signed using the signature key, wherein when the signer selects the data to be signed, a signature instruction screen including a document ID corresponding to the data to be signed is displayed on the first terminal device by the signature application server, and and transmits a signature authorization request including information about the document ID to the authentication and authorization server, and when the authentication and authorization server receives the signature authorization request from the signature application server, it displays a signing intention confirmation screen including the document ID on the second terminal device, and when the signer performs a predetermined operation on the second terminal device on which the signing intention confirmation screen is displayed, the authentication and authorization server generates a token for authorizing use of the signature key, and when the authentication and authorization server generates the token, the remote signature server digitally signs the data to be signed. [Effects of the Invention]

[0007] According to the present invention, it is possible to prevent erroneous signing with an electronic signature. [Brief explanation of the drawings]

[0008] [Figure 1A] 1 is a diagram showing the overall configuration of an electronic signature system, which is an example of an information processing system according to an embodiment of the present invention. [Figure 1B] FIG. 2 is a diagram showing an example of the hardware configuration of each information device that constitutes the electronic signature system. [Figure 2] FIG. 2 is a functional block diagram showing an example of the functional configuration of an authentication and authorization server. [Figure 3] FIG. 2 is a functional block diagram showing an example of the functional configuration of a remote signature server. [Figure 4] FIG. 2 is a functional block diagram showing an example of the functional configuration of a signature application server. [Figure 5] FIG. 10 is a diagram showing an example of a user information management table. [Figure 6] FIG. 10 is a diagram showing an example of a signing key management table. [Figure 7] FIG. 10 is a diagram showing an example of a signature authorization request management table. [Figure 8] FIG. 10 is a diagram showing an example of a key and certificate management table. [Figure 9] FIG. 10 is a diagram showing an example of a signature log management table. [Figure 10] Sequence diagram for service authentication. [Figure 11] Sequence diagram for selecting a signing key. [Figure 12] Sequence diagram for signature authorization. [Figure 13] Sequence diagram for signature generation. [Figure 14] Sequence diagram for viewing the signature log. [Figure 15] FIG. 10 is a diagram showing an example of a message indicating the contents of a signature authorization request. [Figure 16] FIG. 10 is a diagram showing an example of a token. [Figure 17] FIG. 10 is a diagram showing an example of a message indicating the content of a signature intention confirmation result. [Figure 18] FIG. 10 is a diagram showing an example of a signature instruction screen. [Figure 19] FIG. 10 is a diagram showing an example of a signature authorization push notification screen. [Figure 20] FIG. 10 is a diagram showing an example of a signing intention confirmation screen. [Figure 21] FIG. 10 is a diagram showing an example of a signature log viewing screen. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0010] Fig. 1A is a diagram showing the overall configuration of an electronic signature system, which is an example of an information processing system according to one embodiment of the present invention. The electronic signature system 1 shown in Fig. 1 is a system that issues an electronic signature to an electronic file in response to an operation by a signer. The electronic signature system 1 is configured by connecting a signer authorization terminal 11, a signer operation terminal 13, an authentication / authorization server 20, a remote signature server 30, and a signature application server 40 to each other via a network 15.

[0011] Signer approval terminal 11 and signer operation terminal 13 are terminal devices operated by the signer when signing an electronic signature. Signer approval terminal 11 is, for example, a smartphone, and signer operation terminal 13 is, for example, a PC (Personal Computer). A signer selects one or more arbitrary electronic files as data to be signed by operating signer operation terminal 13, and then operates signer approval terminal 11 to authenticate and confirm the electronic signature for the data to be signed, thereby being able to sign the desired electronic file. Note that signer approval terminal 11 and signer operation terminal 13 may be the same terminal device.

[0012] The authentication and authorization server 20 has information about the signature key owned by the signer. When the signer selects data to be signed on the signer operation terminal 13 and issues a sign instruction, the authentication and authorization server 20 confirms the signer's intention by displaying a signature intention confirmation screen on the signer authorization terminal 11. When the signer confirms on this signature intention confirmation screen that the intended electronic file has been designated as the data to be signed, the authentication and authorization server 20 generates a token (SAD: Signature Activation Data) to authorize the use of the signature key owned by the signer.

[0013] The remote signature server 30 digitally signs the data to be signed using the signature key owned by the signer, based on the token (SAD) generated by the authentication and authorization server 20. It then generates a signature value indicating that the data to be signed has been signed by the signer, and provides this to the signature application server 40. The signature application server 40 can generate a signed electronic file corresponding to the data to be signed selected by the signer, based on the signature value provided by the remote signature server 30.

[0014] The signature application server 40 is connected to the signer operation terminal 13 via the network 15, and receives a signing instruction for data to be signed selected by the signer on the signer operation terminal 13. Upon receiving a signing instruction from the signer, the signature application server 40 transmits a signature authorization request to the authentication and authorization server 20. By receiving the signature authorization request transmitted from the signature application server 40, the authentication and authorization server 20 detects that a signing instruction has been issued by the signer, and can cause the signer authorization terminal 11 to display a signing intention confirmation screen as described above.

[0015] 1A shows an example in which the electronic signature system 1 has one authentication and authorization server 20, one remote signature server 30, and multiple signature application servers 40, but the number of servers constituting the electronic signature system 1 is not limited to this. The electronic signature system 1 can be configured using any number of authentication and authorization servers 20, remote signature servers 30, and signature application servers 40. Furthermore, the authentication and authorization server 20, remote signature server 30, and signature application server 40 may be either a physical server or a cloud server, or a combination of these.

[0016] Fig. 1B is a diagram showing an example of the hardware configuration of each information device that constitutes the electronic signature system 1. Each of the information devices that constitute the electronic signature system 1 shown in Fig. 1A, namely, the signer authorization terminal 11, the signer operation terminal 13, the authentication / authorization server 20, the remote signature server 30, and the signature application server 40, is configured by, for example, a computer 101 that includes a processor 102, a main memory device 103, an auxiliary memory device 104, an input / output interface 105, an input device 106, and an output device 107. In the computer 101, these devices are connected to each other via a communication bus.

[0017] The processor 102 executes a predetermined program to control the operation of the computer 101 and cause the computer 101 to function as each information device (the signer authorization terminal 11, the signer operation terminal 13, the authentication / authorization server 20, the remote signature server 30, and the signature application server 40) of the electronic signature system 1. The processor 102 is configured using, for example, a central processing unit (CPU), a micro processing unit (MPU), a graphics processing unit (GPU), etc. The main memory device 103 is a volatile storage medium and is used as a work area when the processor 102 executes a program. The auxiliary memory device 104 is a recording medium capable of storing various programs and data and is configured using, for example, a hard disk drive (HDD), a solid state drive (SSD), etc. The input / output interface 105 is a part that performs interface processing for input and output data. The input device 106 is a device that accepts data input from a user to the computer 101 and is configured using, for example, a keyboard, a mouse, a touch panel, a microphone, etc. The output device 107 is a device that outputs information to the user, and is configured using, for example, a display, a printer, a speaker, and the like.

[0018] Fig. 2 is a functional block diagram showing an example of the functional configuration of authentication and authorization server 20. As shown in Fig. 2, authentication and authorization server 20 is configured to include, for example, the following functional blocks: account management unit 21, service authentication unit 22, signature key information response unit 23, signature authorization unit 24, signature authorization notification unit 25, signature intention confirmation request unit 26, account information management store 27, and signature authorization request management store 28.

[0019] The account management unit 21 manages account information when a signer accesses the authentication / authorization server 20 using the signer operation terminal 13. The service authentication unit 22 authenticates services available to the signer on the authentication / authorization server 20. The signature key information response unit 23 provides signature key information related to the signature key owned by the signer in response to a request from the remote signature server 30. The signature authorization unit 24 determines whether the remote signature server 30 should approve or deny the use of the signer's signature key by signing an electronic signature in response to the signer's signature intention confirmation result transmitted from the signer authorization terminal 11. If the determination is approved, the signature authorization notification unit 25 generates a token (SAD) for permitting the remote signature server 30 to use the signature key. In response to a request from the signature application server 40, the signature authorization notification unit 25 provides the token (SAD) generated by the signature authorization unit 24 to the signature application server 40. When the signer selects data to be signed on the signer operation terminal 13 and issues a signing instruction, the signature intention confirmation request unit 26 issues a notification to display the above-mentioned signature intention confirmation screen on the signer authorization terminal 11 in response to this. In the authentication / authorization server 20, the functions of the account management unit 21, the service authentication unit 22, the signature key information response unit 23, the signature authorization unit 24, the signature authorization notification unit 25, and the signature intention confirmation request unit 26 are each realized by, for example, the processor 102 in FIG. 1B executing a predetermined program.

[0020] The account information management store 27 stores a user information management table 271 and a signature key management table 272. The signature authorization request management store 28 stores a signature authorization request management table 281. The user information management table 271 is a table for managing information on each user (signer) who issues an electronic signature using the electronic signature system 1. The signature key management table 272 is a table for managing information on the signature key owned by each user (signer). The signature authorization request management table 281 is a table for managing the contents of a signature authorization request from each user (signer) and the issuance status of a token (SAD) in response to the request. Specific examples of these tables will be described later. In the authentication and authorization server 20, the functions of the account information management store 27 and the signature authorization request management store 28 are respectively realized by, for example, the auxiliary storage device 104 of FIG. 1B.

[0021] Fig. 3 is a functional block diagram showing an example of the functional configuration of the remote signature server 30. As shown in Fig. 3, the remote signature server 30 is configured to include, for example, functional blocks such as a signature key management unit 31, a signature key list response unit 32, a signature request reception unit 33, a signature value generation unit 34, a signature value response unit 35, a signature log management unit 36, a signature key information management store 37, and a signature log information management store 38.

[0022] The signature key management unit 31 manages the signature keys owned by each user (signer). The signature key list response unit 32 provides each user (signer) with a list of signature keys owned by that user in response to a request from the signer operation terminal 13 via the signature application server 40. The signature request acceptance unit 33 accepts a signature request from the signature application server 40 and receives the token (SAD) included in the signature request. The signature value generation unit 34 uses the token (SAD) received by the signature request acceptance unit 33 to apply an electronic signature to the data to be signed using the signature key owned by the signer, and generates a signature value corresponding to the signed data to be signed. The signature value response unit 35 returns the signature value generated by the signature value generation unit 34 to the signature application server 40. The signature log management unit 36 ​​manages a signature log that represents the execution history of electronic signatures by the signature value generation unit 34. In addition, in the remote signature server 30, the functions of the signature key management unit 31, the signature key list response unit 32, the signature request acceptance unit 33, the signature value generation unit 34, the signature value response unit 35 and the signature log management unit 36 ​​are each realized, for example, by the processor 102 in Figure 1B executing a predetermined program.

[0023] The signature key information management store 37 stores a key and certificate management table 371. The signature log information management store 38 stores a signature log management table 381. The key and certificate management table 371 is a table for managing information on the signature keys owned by each user (signer) and the certificates corresponding to each signature key. The signature log management table 381 is a table for managing a signature log that represents the execution history of electronic signatures by the signature value generation unit 34. Specific examples of these tables will be described later. In the remote signature server 30, the functions of the signature key information management store 37 and the signature log information management store 38 are each realized by, for example, the auxiliary storage device 104 of FIG. 1B.

[0024] Fig. 4 is a functional block diagram showing an example of the functional configuration of the signature application server 40. As shown in Fig. 4, the signature application server 40 is configured to include, for example, the following functional blocks: a user screen response unit 41, a service authentication request unit 42, a signature target document management unit 43, a signature key request unit 44, a signature authorization request unit 45, a signature request unit 46, a signed document generation unit 47, a signature log request unit 48, and a signed document management store 49.

[0025] The user screen response unit 41 controls the content of the screens displayed on the signer authorization terminal 11 and the signer operation terminal 13, detects operation inputs by each user on these display screens, and accepts instructions and requests from each user. The service authentication request unit 42 makes an authentication request to the authentication and authorization server 20 for the service when each user (signer) uses the electronic signature system 1. The signature target document management unit 43 manages documents specified as data to be signed. The signature key request unit 44 requests information on the signature key owned by each user (signer) from the remote signature server 30 in response to a request from each user (signer) made using the signer operation terminal 13. The signature authorization request unit 45 requests authorization to execute an electronic signature using the signature key from the authentication and authorization server 20 in response to a signing instruction from each user (signer) made using the signer operation terminal 13. When the authentication and authorization server 20 authorizes the execution of an electronic signature, the signature request unit 46 requests the remote signature server 30 to execute an electronic signature on the data to be signed by transmitting a token (SAD) provided by the authentication and authorization server 20 to the remote signature server 30. The signed document generation unit 47 receives a signature value transmitted from the remote signature server 30 as a result of the execution of the electronic signature by the remote signature server 30, and generates a signed document corresponding to the document (electronic file) designated as the data to be signed based on the signature value. The signature log request unit 48 requests the remote signature server 30 for a signature log managed for each user in the remote signature server 30. In the signature application server 40, the functions of the user screen response unit 41, the service authentication request unit 42, the signature target document management unit 43, the signature key request unit 44, the signature authorization request unit 45, the signature request unit 46, the signed document generation unit 47, and the signature log request unit 48 are respectively realized by, for example, the processor 102 of FIG. 1B executing a predetermined program.

[0026] The signed document management store 49 stores a signed document management table 491 and a signed document management table 492. The signed document management table 491 is a table for managing documents (electronic files) designated by each user (signer) as data to be signed. The signed document management table 492 is a table for managing signed documents generated by the signed document generation unit 47. In the signature application server 40, the function of the signed document management store 49 is realized by, for example, the auxiliary storage device 104 in FIG. 1B.

[0027] Fig. 5 is a diagram showing an example of a user information management table 271 stored in the account information management store 27 of Fig. 2. As shown in Fig. 5, the user information management table 271 is configured to include, for example, service authentication information 201 recording the ID and password of each user, and authorization terminal information 202 recording the ID of the signer authorization terminal 11 registered in advance by each user and information on a notification token. Note that the configuration of the user information management table 271 is not limited to the example shown in Fig. 5. Furthermore, information other than that shown in Fig. 5 may be included in the user information management table 271.

[0028] Fig. 6 is a diagram showing an example of the signing key management table 272 stored in the account information management store 27 of Fig. 2. As shown in Fig. 6, the signing key management table 272 includes, for example, a signing key ID 211 that records the ID of the signing key owned by each user, an owner 212 that records the ID of the user who owns each signing key, and a key scope 213 that records the scope of use of each user's signing key. Note that the configuration of the signing key management table 272 is not limited to the example shown in Fig. 6. Furthermore, the signing key management table 272 may include information other than that shown in Fig. 6.

[0029] 7 is a diagram showing an example of a signature authorization request management table 281 stored in the signature authorization request management store 28 of FIG. 2. As shown in FIG. 7, the signature authorization request management table 281 includes, for example, a signature authorization request ID 221 recording an ID assigned to each piece of signature target data for which a signature authorization request has been made, a group ID 222 recording a group ID assigned to each signature authorization request when multiple signature authorization requests have been made for the same signature target data, a signature count 223 recording the number of signatures required for each piece of signature target data, a hash value count 224 recording the number of hash values ​​for each piece of signature target data, and a token issuance status 225 recording the issuance status of a token (SAD) for each piece of signature target data. Note that the configuration of the signature authorization request management table 281 is not limited to the example shown in FIG. 7. Furthermore, the signature authorization request management table 281 may include information other than that shown in FIG. 7.

[0030] 8 is a diagram showing an example of a key and certificate management table 371 stored in the signature key information management store 37 of FIG. 3. As shown in FIG. 8, the key and certificate management table 371 includes, for example, a signature key ID 231 recording the ID of the signature key owned by each user, an actual PIN 232 recording a personal identification number (PIN) that each user must enter to activate the signature key, identification information 233 recording identification information of a public key certificate corresponding to each signature key, and a file name 234 recording the file name of the public key certificate corresponding to each signature key. Note that the configuration of the key and certificate management table 371 is not limited to the example shown in FIG. 8. Furthermore, information other than that shown in FIG. 8 may be included in the key and certificate management table 371.

[0031] FIG. 9 is a diagram showing an example of a signature log management table 381 stored in the signature log information management store 38 of FIG. 3. As shown in FIG. 9, the signature log management table 381 includes, for example, a document number ID 241 that records the document number assigned to each document (electronic file) in the signature target data that has been digitally signed; a signature processing log 242 that indicates the name of a log file in which the execution details of the electronic signature for each document are recorded; and a signature intention confirmation result 243 that records the result of the signer's intention confirmation for each document. The document number ID 241 is formed by combining the ID of each user who is the signer, the date the electronic signature was executed, and the document ID assigned to each document that has been digitally signed. Note that the configuration of the signature log management table 381 is not limited to the example shown in FIG. 9. Furthermore, the signature log management table 381 may include information other than that shown in FIG. 9.

[0032] Next, the flow of information between the information devices in the electronic signature system 1 will be described below with reference to the sequence diagrams of FIGS.

[0033] 10 is a sequence diagram of service authentication, which is the first stage of authentication and authorization processing. When a user (signer) selects to display a menu screen on signer operation terminal 13, a request to display the menu screen is sent from signer operation terminal 13 to signature application server 40. In response to this request, signature application server 40 causes user screen response unit 41 to display the menu screen on signer operation terminal 13 (step S11).

[0034] After the menu screen is displayed, when the user (signer) selects a signature service on the signer operation terminal 13, a remote signature service request is sent from the signer operation terminal 13 to the signature application server 40 (step S12). In response to this request, the signature application server 40 generates an authorization request for the authentication / authorization server 20 by the service authentication request unit 42 (step S13) and sends it to the signer operation terminal 13 together with a redirect URL.

[0035] When the signer operation terminal 13 receives the authorization request and redirect URL transmitted from the signature application server 40, it uses these to redirect to the authentication and authorization server 20 (step S14), and transmits an authorization request for the remote signature service to the authentication and authorization server 20. When the authentication and authorization server 20 receives the authorization request for the remote signature service from the signer operation terminal 13, it makes a login request to the signer operation terminal 13 (step S15), and displays a login screen (step S16).

[0036] After the login screen is displayed, when the user (signer) enters predetermined authentication information (user ID, password) at signer operation terminal 13, this authentication information is transmitted from signer operation terminal 13 to authentication / authorization server 20. Authentication / authorization server 20 verifies the authentication information transmitted from signer operation terminal 13 using service authentication unit 22 (step S17), and if the content is correct, generates an authorization code (step S18) and transmits it to signer operation terminal 13 together with a redirect URL.

[0037] When the signer operation terminal 13 receives the authorization code and redirect URL transmitted from the authentication / authorization server 20, it uses these to redirect to the signature application server 40 (step S19) and transmits the authorization code to the signature application server 40. When the signature application server 40 receives the authorization code from the signer operation terminal 13, it transmits the authorization code to the authentication / authorization server 20 and makes an access token request (step S20). The authentication / authorization server 20 verifies the authorization code transmitted from the signature application server 40 using the service authentication unit 22 (step S21), and if the code is correct, generates an access token (step S22) and transmits it to the signature application server 40. When the signature application server 40 receives the access token transmitted from the authentication / authorization server 20, it saves it (step S23), and causes the user screen response unit 41 to display a signature service screen on the signer operation terminal 13 (step S24).

[0038] After the signature service screen is displayed, when the user (signer) selects one or more documents (electronic files) to be signed on the signer operation terminal 13 and instructs uploading (step S25), the data of the electronic files of the documents to be signed is transmitted from the signer operation terminal 13 to the signature application server 40 as data to be signed. The signature application server 40 receives the data to be signed transmitted from the signer operation terminal 13 via the signature target document management unit 43, saves the documents to be signed (step S26), and writes the information to the signature target document management table 491. Furthermore, a hash value and a document ID corresponding to the saved documents to be signed are generated (steps S27 and S28).

[0039] The hash value generated in step S27 is an irregular string of characters assigned to the document to be signed, so the user (signer) cannot easily identify the document to be signed by looking at it. On the other hand, the document ID generated in step S28 is a regular string of characters that can be recognized by humans, such as "A001," so the user (signer) can easily identify the document to be signed by checking it.

[0040] Signature application server 40 transmits the processing result including the generated document ID to signer operation terminal 13, and causes signer operation terminal 13 to display the document ID (step S29).

[0041] 11 is a sequence diagram for selecting a signature key. When a user (signer) performs an operation on signer operation terminal 13 to request information about the signature key he or she owns (step S31), a request for a signature key is sent from signer operation terminal 13 to signature application server 40. In response to this request, signature application server 40 generates a signature key request using signature key request unit 44 (step S32) and sends it to remote signature server 30 together with the access token saved in step S23 of FIG. 10.

[0042] The remote signature server 30 verifies the access token sent from the signature application server 40 using the signature key list response unit 32 (step S33), and if the contents are correct, acquires the user ID corresponding to the access token (step S34).The remote signature server 30 then transmits the acquired user ID to the authentication and authorization server 20 and requests signature key information (step S35).In response to the request for signature key information from the remote signature server 30, the authentication and authorization server 20 responds with signature key information linked to the received user ID (step S36), and returns the ID of the signature key to the remote signature server 30.

[0043] When the remote signature server 30 receives the signature key ID transmitted from the signature application server 40, the signature key list response unit 32 generates a list of signature keys corresponding to the user ID transmitted in step S35 (step S37) and returns the list to the signature application server 40. When the signature application server 40 receives the list of signature keys from the remote signature server 30, it generates a screen showing the list (step S38) and displays it on the signer operation terminal 13 (step S39). The user (signer) can select a signature key to use for an electronic signature by selecting any signature key from the list on the screen displayed on the signer operation terminal 13 (step S40).

[0044] Fig. 12 is a sequence diagram for signature authorization, which is the second stage of authentication and authorization processing. After a user (signer) uploads one or more documents (electronic files) to be signed according to the sequence diagram of Fig. 10 and selects a signature key according to the sequence diagram of Fig. 11, the user issues a signature instruction on the signer operation terminal 13 (step S41). The signer operation terminal 13 transmits a signature key ID and a document ID to the signature application server 40, and an instruction to sign the data to be signed is issued. The signature application server 40 generates a linking code corresponding to this signature instruction (step S42) and returns it to the signer operation terminal 13 as the processing result for the signature instruction. The signer operation terminal 13 displays the linking code returned from the signature application server 40 together with the document ID (step S43), prompting the user (signer) to confirm it.

[0045] Thereafter, the signature application server 40 makes a signature authorization request to the authentication and authorization server 20 (step S44). Upon receiving the signature authorization request from the signature application server 40, the authentication and authorization server 20 generates a temporary response in response to the request (step S45) and returns the temporary response to the signature application server 40. The signature application server 40 saves the token request data included in the temporary response from the authentication and authorization server 20 (step S46).

[0046] After saving the token request data, the signature application server 40 enters a state of waiting for token generation, and periodically requests the authentication and authorization server 20 to obtain the signature intention confirmation result and the token (SAD) (step S47). At this point, the token (SAD) has not yet been generated in the authentication and authorization server 20, so an error is returned from the authentication and authorization server 20 to the signature application server 40.

[0047] After the temporary response to the signature application server 40, the authentication and authorization server 20 generates a dynamic link for signing intention confirmation by the signing intention confirmation request unit 26 (step S48), and further generates a signature authorization push notification (step S49), and sends the push notification to the signer authorization terminal 11. Upon receiving the push notification from the authentication and authorization server 20, the signer authorization terminal 11 displays the signature authorization push notification (step S50). In response to this notification, when the user (signer) performs an operation on the signer authorization terminal 11 to request the display of a signing intention confirmation screen, the authentication and authorization server 20 causes the signer authorization terminal 11 to display the signing intention confirmation screen (step S51).

[0048] When the user (signer) confirms on the signing intention confirmation screen displayed on signer authorization terminal 11 that the electronic signature is as intended and performs a predetermined operation, the signing intention confirmation result is sent from signer authorization terminal 11 to authentication and authorization server 20 (step S52). Upon receiving the signing intention confirmation result from signer authorization terminal 11, authentication and authorization server 20 confirms, via signature authorization unit 24, whether or not the user (signer) intends to sign, and if there is an intention to sign, adds the signature of authentication and authorization server 20 to the received signing intention confirmation result (step S53), and generates a token (SAD) for authorizing the use of the signing key (step S54).

[0049] After the authentication and authorization server 20 generates the token (SAD) in step S54, the signature application server 40 utilizes the token request data to request the authentication and authorization server 20 to obtain the signature intention confirmation result and the token (SAD) (step S55). The authentication and authorization server 20 then returns the signature intention confirmation result and the generated token (SAD) to the signature application server 40 via the signature authorization notification unit 25 (step S55).

[0050] 13 is a sequence diagram for generating a signature. When the signature application server 40 receives the signature intention confirmation result and the token (SAD) transmitted from the authentication / authorization server 20 in step S55 of FIG. 12, the signature request unit 46 generates a signature request based on these (step S61) and transmits it to the remote signature server 30. When the remote signature server 30 receives the signature request transmitted from the signature application server 40, the signature request reception unit 33 analyzes the received signature request (step S62) and verifies the signature intention confirmation result and the contents of the token (SAD) (step S63). If the contents are valid, the signature value generation unit 34 activates the signature key using the token (SAD) (step S64) and generates a signature value (step S65). After saving the signature intention confirmation result and a log of the signature process (step S66), the signature value response unit 35 sends the signature value generated in step S65 to the signature application server 40 (step S67).

[0051] When the signature value is transmitted from the remote signature server 30, the signature application server 40 receives it and stores it (step S68). Then, the signed document generation unit 47 generates a signed document using the received signature value and stores it (step S69). Upon completing generation of the signed document, the signature application server 40 causes the user screen response unit 41 to display the generated signed document on the signer operation terminal 13 (step S70), prompting the user (signer) to confirm it.

[0052] In the digital signature system 1, each information device operates in accordance with the sequence diagrams of FIGS. 10 to 13 described above, whereby a digital signature is issued to an electronic file selected by a user (signer) as data to be signed.

[0053] Fig. 14 is a sequence diagram for viewing a signature log. After the signer operation terminal 13, the signature application server 40, and the authentication / authorization server 20 have each executed the processes of steps S11 to S24 in Fig. 10 (step S71), when the user requests display of an arbitrary signed document at the signer operation terminal 13 (step S72), this request is transmitted from the signer operation terminal 13 to the signature application server 40. In response to the request from the signer operation terminal 13, the signature application server 40 causes the signer operation terminal 13 to display the saved signed document.

[0054] Furthermore, when the user makes a request for a signature log for an arbitrary signed document at the signer operation terminal 13 (step S73), a signature log request including the document ID of the specified signed document is transmitted from the signer operation terminal 13 to the signature application server 40. Upon receiving the signature log request from the signer operation terminal 13, the signature application server 40 uses the signature log request unit 48 to identify the document number corresponding to the document ID included in the received signature log request, thereby generating a signature log request to the remote signature server 30 (step S74), and transmits the request to the remote signature server 30 together with an access token for accessing the signature log management table 381 held by the remote signature server 30.

[0055] The remote signature server 30 verifies the access token sent from the signature application server 40 using the signature log management unit 36 ​​(step S75), and if the contents are correct, receives and acquires the sent document number (step S76).Then, the remote signature server 30 acquires the signature processing log and the signature intention confirmation result corresponding to the acquired document number from the signature log management table 381 (step S77), and returns these to the signature application server 40 as a signature log.

[0056] When the signature log is sent from the remote signature server 30, the signature application server 40 receives it, verifies it, and stores it (step S78). Then, an outline of the stored signature log is displayed on the signer operation terminal 13 (step S79) for the user (signer) to confirm. Furthermore, depending on the operation performed by the user (signer) on the signer operation terminal 13 thereafter, the signature processing log is displayed (step S80), the intention confirmation result is displayed (step S81), an additional menu is displayed (step S82), etc.

[0057] Next, examples of information transmitted and received between the signature application server 40, the signer authorization terminal 11, and the authentication and authorization server 20 in the sequence diagram of FIG. 12 will be described below with reference to FIGS.

[0058] 15 shows an example of a message representing the contents of a signature authorization request sent from the signature application server 40 to the authentication / authorization server 20 when the signature application server 40 makes a signature authorization request to the authentication / authorization server 20 in step S44 of FIG. 12. In FIG. 15, (a) shows a signature authorization request message 301 when the data to be signed contains one document (electronic file), (b) shows a signature authorization request message 302 that consolidates multiple documents (electronic files) contained in the data to be signed into one, and (c) shows signature authorization request messages 303, 304, and 305 that separate multiple documents (electronic files) contained in the data to be signed by each document. These messages include the ID of the signer and the signature key, the number of documents (electronic files) contained in the data to be signed, the hash value and document number corresponding to each document to be signed, and the value of the linking code generated in step S42 of FIG. 12. As mentioned above, the document number includes the document ID corresponding to each document (electronic file).

[0059] Fig. 16 shows an example of a token (SAD) sent from the authentication and authorization server 20 to the signature application server 40 in step S55 of Fig. 12. In Fig. 16, (a) shows token 311 when the data to be signed contains one document (electronic file), (b) shows token 312 that combines multiple documents (electronic files) included in the data to be signed into one, and (c) shows tokens 313 and 314 that separate multiple documents (electronic files) included in the data to be signed for each document. These tokens also include the token ID, expiration date, issuance time, signature value, and so on, in addition to the information included in each signature authorization request message shown in Fig. 15.

[0060] Fig. 17 shows an example of a message indicating the contents of the signing intention confirmation result sent from signer authorization terminal 11 to authentication / authorization server 20 in step S52 of Fig. 12. In Fig. 17, (a) shows message 321 of the signing intention confirmation result when the data to be signed contains one document (electronic file), (b) shows message 322 of the signing intention confirmation result that consolidates multiple documents (electronic files) included in the data to be signed, and (c) shows message 323 of the signing intention confirmation result that separates multiple documents (electronic files) included in the data to be signed by document. These messages include the ID of the user who is the signer, the date on which the user input the signing intention confirmation result, and the confirmation result of whether the user consents to signing the document for the document ID of each document (electronic file) included in the data to be signed.

[0061] Next, examples of screens displayed on signer approval terminal 11 and signer operation terminal 13 in the sequence diagram of FIG. 12 explained above will be described below with reference to FIGS.

[0062] Fig. 18 shows an example of a signature instruction screen displayed on the signer operation terminal 13 when the user (signer) issues a signing instruction to the signature application server 40 in step S41 of Fig. 12. In Fig. 18, (a) shows a signature instruction screen 401 when issuing a signing instruction for one document (electronic file), (b) shows a signature instruction screen 402 when issuing a signing instruction for multiple documents (electronic files) at once, and (c) shows a signature instruction screen 403 when issuing a signing instruction for multiple documents (electronic files) individually and consecutively. These screens contain document IDs corresponding to each document (electronic file) included in the signature target data as a signature instruction target.

[0063] Fig. 19 shows an example of a signature authorization push notification screen displayed on the signer authorization terminal 11 in step S50 of Fig. 12. The signature authorization push notification screen 411 shown in Fig. 19 includes the value of the linking code generated in step S42 of Fig. 12, a redirect URL for redirecting to the authentication and authorization server 20, and the like.

[0064] Fig. 20 shows an example of a signing intention confirmation screen displayed on the signer approval terminal 11 in step S51 of Fig. 12. In Fig. 20, (a) shows a signing intention confirmation screen 421 when confirming the intention to sign for one document (electronic file), (b) shows a signing intention confirmation screen 422 when confirming the intention to sign for multiple documents (electronic files) at once, and (c) shows a signing intention confirmation screen 423 when confirming the intention to sign for multiple documents (electronic files) individually. These screens include the ID of the user who is the signer, the ID of the signature key used for the electronic signature, the document ID corresponding to each document (electronic file) for which the intention to sign is to be confirmed, and a check box for the user to indicate whether or not they intend to sign each document.

[0065] Note that in the signature instruction screens 401-403 shown in Fig. 18 and the signature intention confirmation screens 421-423 shown in Fig. 20, each document (electronic file) to be signed is represented by a common document ID. This allows the user (signer) to easily associate each document for which a signature instruction has been given on the signature instruction screens 401-403 with each document for which the intention to sign is subsequently confirmed on the signature intention confirmation screens 421-423. This reduces the burden on the user when confirming the intention to sign after giving a signature instruction, and makes it possible to reliably prevent erroneous signing with an electronic signature.

[0066] FIG. 21 shows an example of a signature log viewing screen displayed on signer operation terminal 13 when the signature log is viewed as described in the sequence diagram of FIG.

[0067] 14, when the user requests display of the signed document, signed document display screen 431 is displayed on signer operation terminal 13. When the user selects an arbitrary signed document to view the signature log on this screen 431 and selects "Get signature log," the processing of step S80 in Fig. 14 is executed, and signature log display screen 432 is displayed on signer operation terminal 13. This screen 432 includes a signature log 433 when the selected signed document was digitally signed.

[0068] When the user selects "Intention Confirmation Result" on the signature log display screen 432, the processing of step S81 in Fig. 14 is executed, and an intention confirmation result display screen 434 is displayed on the signer operation terminal 13. This screen 434 includes a signature intention confirmation result 435 by the user when the electronic signature was applied to the selected signed document.

[0069] When the user selects "Additional Menu" on intention confirmation result display screen 434, the processing of step S82 in Fig. 14 is executed, and additional menu screen 436 is displayed on signer operation terminal 13. This screen 436 includes operation buttons for instructing the execution of various additional menus.

[0070] According to the embodiment of the present invention described above, the following advantageous effects can be obtained.

[0071] (1) Electronic signature system 1, which is an information processing system for performing electronic signatures, includes a signature application server 40 connected to signer operation terminal 13 (first terminal device) and accepting a signature instruction for data to be signed selected by the signer on signer operation terminal 13, an authentication and authorization server 20 having information on the signature key owned by the signer, and a remote signature server 30 that uses the signature key to electronically sign the data to be signed and generates a signature value indicating that the data to be signed has been signed by the signer. When the signer selects data to be signed, signature application server 40 causes signer operation terminal 13 to display signature instruction screens 401 to 403 including a document ID corresponding to the data to be signed (step S41). Furthermore, signature application server 40 accepts a signature instruction from signer operation terminal 13 on which signature instruction screens 401 to 403 are displayed, and transmits a signature authorization request including information on the document ID to authentication and authorization server 20 (step S44). When the authentication / authorization server 20 receives a signature authorization request from the signature application server 40, it displays signature intention confirmation screens 421-423, including a document ID, on the signer authorization terminal 11 (second terminal device). When the signer performs a predetermined operation on the signer authorization terminal 11 on which the signature intention confirmation screens 421-423 are displayed, the authentication / authorization server 20 receives a signature intention confirmation result transmitted from the signer authorization terminal 11 (step S52). The authentication / authorization server 20 generates a token for authorizing the use of the signature key (step S54) and transmits it to the signature application server 40 (step S55). When the remote signature server 30 receives the token from the signature application server 40 (step S61), it digitally signs the data to be signed to generate a signature value (step S65). This configuration allows the signer to easily associate the data to be signed between the signature instruction screens 401-403 and the signature intention confirmation screens 421-423 using the common document ID displayed on these screens, thereby enabling the signer to confirm their intention to sign. This prevents erroneous signing with an electronic signature.

[0072] (2) The signature application server 40 allows the signer to select one or more electronic files from the plurality of electronic files on the signer operation terminal 13, and sets the one or more electronic files selected by the signer as data to be signed (step S25). In this way, the signer can select one or more arbitrary electronic files as data to be signed and apply an electronic signature to the electronic files.

[0073] (3) When the data to be signed includes multiple electronic files, the authentication / authorization server 20 displays signature intention confirmation screens 422, 423 including document IDs corresponding to the multiple electronic files on the signer authorization terminal 11. This allows the signer to reliably confirm his or her intention to sign even when digitally signing multiple electronic files.

[0074] (4) On the signer authorization terminal 11 where the signature intention confirmation screen 423 is displayed, the authentication / authorization server 20 allows the signer to select whether or not to permit electronic signatures for each of the multiple electronic files included in the data to be signed, using check boxes provided for each document ID corresponding to each document. As a result, in step S54, tokens are generated for electronic files for which the signer has permitted electronic signatures, and tokens are not generated for electronic files for which the signer has not permitted electronic signatures. In this manner, when a signer instructs electronic signatures for multiple electronic files, it is possible to confirm the intention to sign for each electronic file individually and generate a token for each electronic file according to the confirmation results.

[0075] (5) In step S61, the signature application server 40 transmits the token of the data to be signed and the document ID to the remote signature server 30, requesting that the data be digitally signed. In this way, the remote signature server 30 can reliably digitally sign the electronic file designated by the signer.

[0076] (6) The remote signature server 30 records the electronic signature history information, including the result of the signer's signature intention confirmation and the document ID, as a signature processing log (step S66). By doing so, when the signer later checks the electronic signature history information, it becomes possible to easily confirm which electronic file the electronic signature was applied to.

[0077] It goes without saying that the present invention is not limited to the above-described embodiments and can be modified in various ways without departing from the spirit of the present invention. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those having all of the described configurations. Furthermore, it is possible to add, delete, or replace part of the configuration of the above-described embodiments with other configurations.

[0078] Furthermore, the above-mentioned configurations, functional units, processing units, processing means, etc. may be partially or entirely implemented in hardware, for example, by designing them as integrated circuits. The above-mentioned configurations, functions, etc. may also be implemented in software, with a processor interpreting and executing a program that implements each function. Information such as the programs, tables, and files that implement each function can be stored in a memory, a hard disk, a recording device such as an SSD, an IC card, an SD card, a DVD, or other recording media.

[0079] In addition, in the above figures, the control lines and information lines shown are those that are considered necessary for explanation, and do not necessarily show all the control lines and information lines that are actually implemented. For example, it can be considered that almost all components are actually connected to each other. [Explanation of symbols]

[0080] 1: Electronic signature system 11: Signer authorization terminal 13: Signer operation terminal 15: Network 20: Authentication and authorization server 21: Account Management Department 22: Service authentication section 23: Signature key information response part 24: Signature Authorization Department 25: Signature approval notification section 26: Signature intention confirmation request section 27: Account information management store 28: Signature Authorization Request Management Store 30: Remote signing server 31:Signing key management section 32: Signing key list response part 33: Signature request reception unit 34: Signature value generation unit 35: Signature value response part 36: Signature log management unit 37: Signing key information management store 38: Signature log information management store 40: Signature application server 41: User screen response section 42: Service authentication request part 43: Signature target document management section 44:Signing key request section 45: Signature authorization request section 46:Signature request section 47: Signed document generation unit 48: Signature log request section 49: Signature document management store

Claims

1. a signature application server connected to a first terminal device and configured to accept a signature instruction for signature target data selected by a signer on the first terminal device; an authentication and authorization server having information on a signature key owned by the signer; a remote signature server that uses the signature key to digitally sign the data to be signed and generates a signature value indicating that the data to be signed has been signed by the signer; When the signer selects the signature target data, the signature application server causes the first terminal device to display a signature instruction screen including a document ID corresponding to the signature target data; the signature application server accepts the signature instruction from the first terminal device on which the signature instruction screen is displayed, and transmits a signature authorization request including information about the document ID to the authentication and authorization server; When the authentication / authorization server receives the signature authorization request from the signature application server, it causes a second terminal device to display a signature intention confirmation screen including the document ID; the authentication / authorization server, upon receiving a signing intention confirmation result transmitted from the second terminal device when the signer performs a predetermined operation on the second terminal device on which the signing intention confirmation screen is displayed, generates a token for authorizing use of the signing key and transmits the token to the signature application server; The information processing system is configured such that, upon receiving the token from the signature application server, the remote signature server digitally signs the data to be signed and generates the signature value.

2. 2. The information processing system according to claim 1, The signature application server: having the signer select one or more electronic files from a plurality of electronic files on the first terminal device; An information processing system in which the signer sets one or more electronic files selected from the plurality of electronic files as the signature target data.

3. 3. The information processing system according to claim 2, In an information processing system, when the data to be signed includes multiple electronic files, the authentication / authorization server causes the second terminal device to display the signature intention confirmation screen including the document ID corresponding to each of the multiple electronic files.

4. 4. The information processing system according to claim 3, The authentication and authorization server the second terminal device on which the signing intention confirmation screen is displayed allows the signer to select whether or not to permit the electronic signature for each of the plurality of electronic files included in the signature target data; An information processing system that generates the token for electronic files for which the signer has authorized the electronic signature, among the data to be signed, and does not generate the token for electronic files for which the signer has not authorized the electronic signature.

5. 2. The information processing system according to claim 1, The signature application server transmits the token and the document ID to the remote signature server to request the electronic signature for the signature target data.

6. 6. The information processing system according to claim 5, The remote signature server is an information processing system that records the signing intention confirmation result and the electronic signature history information including the document ID.

7. a storage device that stores information about a signing key owned by a signer; a signing intention confirmation request unit that, in response to a signature authorization request from the signer for the signature target data selected by the signer, displays on a terminal device a signing intention confirmation screen including a document ID corresponding to the signature target data; an information processing device comprising: a signature authorization unit that generates a token to authorize the use of the signature key in accordance with a signing intention confirmation result sent from the terminal device when the signer performs a predetermined operation on the terminal device on which the signing intention confirmation screen is displayed.

8. a first terminal device; a second terminal device; a signature application server that accepts a signing instruction for data to be signed selected by a signer; an authentication and authorization server having information on a signature key owned by the signer; a remote signature server that digitally signs the signature target data using the signature key, When the signer selects the data to be signed, a signature instruction screen including a document ID corresponding to the data to be signed is displayed on the first terminal device; The signature application server accepts the signature instruction from the first terminal device on which the signature instruction screen is displayed, and transmits a signature authorization request including information about the document ID to the authentication and authorization server; When the authentication / authorization server receives the signature authorization request from the signature application server, it displays a signature intention confirmation screen including the document ID on the second terminal device; When the signer performs a predetermined operation on the second terminal device on which the signing intention confirmation screen is displayed, the authentication and authorization server generates a token for authorizing use of the signing key; When the authentication / authorization server generates the token, the remote signature server digitally signs the data to be signed.

Images