JP4582030B2 - Authentication infrastructure system with CRL issue notification function - Google Patents

Description

  The present invention provides an authentication infrastructure system comprising a certificate authority that issues a revocation list of a public key certificate, a certificate verification server that verifies the validity of the public key certificate, and a client that uses the certificate verification server. About.

  In order to clarify the creator of an electronic document including a government authentication infrastructure (hereinafter referred to as GPKI) and to ensure that the electronic document has not been tampered with, public key infrastructure (Public Key Infrastructure) , Hereinafter referred to as PKI) has become widespread (for example, see Non-Patent Document 1). In a system using PKI, an electronic signature is applied to an electronic document with a key called a private key held only by a person who performs an electronic signature (hereinafter referred to as a signer). When an electronic document with an electronic signature is received, the electronic signature is verified to confirm that the electronic document creator and the electronic document have not been tampered with.

  In applications where high trust is required, in order to verify an electronic signature, a key called a public key included in the public key certificate of the signer (hereinafter referred to as a certificate) is used. In addition to verifying the electronic signature, it is necessary to confirm whether the signer's certificate is a valid certificate for the person who verifies the electronic signature (hereinafter referred to as a verifier). . In order to verify whether or not the signer's certificate is valid for the verifier, processes of (1) construction of an authentication path and (2) verification of the authentication path are required.

The certification path is a chain of trust from the verifier to the signer, and is expressed as a certificate chain. In particular, when certificate authorities issue certificates to each other, a special certificate called a mutual authentication certificate is issued. When the nine certification authority from the certification authority 1 ₁ to the certification authority 1 ₉ has a mutual authentication relationship as shown in FIG. 2, the verifier with a certificate by the certificate authority 1 ₂ issued certification path up signer with the certificate by the certificate authority 1 ₁ is issued one second mutual authentication certificate 9 _18, the second mutual authentication certificate 9 _68, third mutual authentication certificate 9 _46, four The certificate chain is in the order of the mutual authentication certificate 9 ₂₄ and the last certificate of the verifier. The method for verifying the verification path thus constructed is described in detail in Non-Patent Document 1 above.

  In addition, the GPKI specification describes an end entity model and a certificate verification server model as models for verifying the validity of a certificate. (For example, see Non-Patent Document 2.) The certificate verification server model provides a function for checking the validity of a certificate online on behalf of a client in order to verify the validity of the certificate. Use verification server.

  The certificate validation server model has the following advantages over the end entity model. First, in the certificate verification server model, since it is not necessary to mount the certification path construction function for constructing the certification path on the client, the signature verification program of the client can be made small. In addition, since the client trusts the determination result of the certificate verification server, the client can flexibly cope with changes in the system configuration simply by changing the setting of the certificate verification server. According to the non-patent document 2, in order to determine whether or not a certificate has been revoked, a certificate revocation list (hereinafter referred to as CRL) issued by the certificate authority or an OCSP responder Is used.

  Since it is inefficient to obtain the CRL from the certificate authority every time verification is performed, in Patent Document 1, the certificate verification server caches the certificate, the CRL, and the verification path to obtain the certificate. A method for speeding up the validity determination process is disclosed.

  By the way, in order to verify an electronic signature or to build a verification path, it is necessary to obtain a signer's certificate. There are two main ways to obtain a signer's certificate.

  One is a method in which an electronic document with an electronic signature is only sent from the signer, and the certificate of the signer is obtained separately. For example, a method of notifying a URL indicating a location where a certificate for verifying the electronic signature is stored together with the electronic document with the electronic signature is applicable. In this method, the verifier needs to access a location where the certificate is stored (hereinafter referred to as a certificate repository) and obtain the certificate. The other is a method in which a signer sends an electronic document with an electronic signature together with a certificate used for verifying the electronic signature.

JP 2002-72876 A ITU, ITU-T Recommendation X. 509 "Information technology-Open systems interconnection-The Directory: Public-key and attribute certified frameworks", ITU, March 2000, p. 7-53 “Government Authentication Infrastructure (GPKI) Government Authentication Infrastructure Interoperability Specification” p. 18-20, 27-29, [online], April 25, 2001, Approved by the Subcommittee on Basic Issues, [Search March 14, 2003], Internet <URL: http: // www. soumu. go. jp / gyoukan / kanri / 010514_2. pdf>

  If the CRL is cached in order to speed up the certificate validity determination process, the cached CRL is not up-to-date when the certificate authority urgently issues the CRL. Patent Document 1 does not mention this point.

  One method for solving the above problem is that the certificate verification server can store the CRL (hereinafter referred to as a CRL repository) in order to perform validity verification correctly even when the CRL is issued urgently. The CRL is periodically accessed to check whether the CRL has been updated. The above methods further include two types: a method in which the certificate verification server itself performs confirmation via a network, and a method in which confirmation is performed by installing CRL issuance confirmation software in the CRL repository.

  In order to improve the accuracy of the validity verification result of the certificate by using a method for periodically checking whether the CRL has been updated, it is necessary to shorten the check interval as much as possible. . However, in the method in which the certificate verification server itself performs confirmation via the network, there is a problem that if the confirmation interval is shortened, the load on the network increases.

  On the other hand, in the case of introducing a CRL issuance confirmation software for confirming to the CRL repository, if the CRL repository operator and the certificate verification server operator are different, the CRL issuance confirmation software There is a problem that installation is not permitted and the above confirmation cannot be performed.

  In an environment where there are a plurality of the certificate verification servers, all the certificate verification servers are the same unless all the certificate verification servers use the CRL issuance confirmation software installed in the CRL repository. Since certificate validity verification cannot be performed with high accuracy, it is necessary to change the setting of the CRL issuance confirmation software in order to increase or decrease the number of certificate verification servers in operation. If the repository operator and the certificate verification server operator are different, there is a problem that it is difficult to flexibly change the number of certificate verification servers.

  Furthermore, even if the verification path is cached, if the old mutual certification certificate is discarded by the certificate authority and a new mutual certification certificate has been issued, the verification path including the new mutual certification certificate is changed. Need to build.

  In an environment where a plurality of certificate verification servers exist, even when a plurality of the certificate verification servers verify the validity of the same certificate, each of the certificate verification servers constructs the certification path. In addition, since the CRL is acquired, access may be concentrated on the specific CRL repository or the certificate repository, or the load on the network may increase. Patent Document 1 does not mention these.

  In the method of separately obtaining the certificate, the client first accesses the certificate repository and obtains the certificate in order to request the certificate validation server to verify the validity of the certificate. There is a problem that it must be.

  Therefore, a new method for solving the above-described problems is demanded.

  The present invention provides a certificate authority comprising a certificate issuing means for issuing the certificate, a CRL issuing means for issuing the CRL, and a certificate storage means for storing the certificate issued by the certificate authority. Acquired from the CRL repository, the CRL repository provided with the CRL storage means for storing the CRL issued by the certificate authority, the certificate validity verification means for verifying the validity of the certificate, CRL cache means for caching the CRL, and verification path cache means for caching a verification path constructed by the certificate validity verification means for verifying the validity of the certificate. And electronic signature verification means for verifying the electronic signature, and certificate validity verification request means for requesting the certificate verification server to verify the validity of the certificate; A CRL issuance notification in an authentication infrastructure system comprising: a client comprising: a CRL issuance notification that simultaneously issues the CRL to the certificate authority and notifies the certificate verification server that the CRL has been issued And a CRL issuance notification transmitting means, and the CRL issuance notification receiving means for receiving the CRL issuance notification from the certificate authority is provided in the certificate verification server.

  In the present invention, the CRL cache unit of the certificate verification server receives the CRL issue notification by the CRL issue notification reception unit, and the CRL repository newly issues the CRL issued by the certificate authority. It is what is acquired from.

  Further, when the present invention discovers that the CRL has been newly issued to the certificate verification server, the present invention can provide a “CRL has been issued” to another certificate verification server registered in advance. A CRL issuance notification transmitting unit for notifying that is provided.

  Further, the present invention provides a certificate issuance notification for notifying the certificate verification server that the certificate has been issued when the certificate is issued by the certificate issuing means. A certificate issuance notification transmitting means is provided, the certificate verification server is provided with a certificate issuance notification receiving means for receiving the certificate issuance notification, and the certificate validity verification means is When the notification receiving unit receives the certificate issuance notification, it creates the verification path including the newly issued certificate, and the verification path cache unit caches the verification path. It is what it does.

  Furthermore, the present invention provides a verification path transmitting means for transmitting the verification path to another certificate verification server registered in advance when the verification path is constructed in the certificate verification server, The path cache means caches the verification path when the verification path is received from another certificate verification server.

  Furthermore, the present invention provides a certificate acquisition request means for requesting the certificate verification server to acquire the certificate necessary for verifying the electronic signature, and the client verifies the certificate verification. When the server obtains the certificate requested for acquisition from the client from the certificate repository, and the certificate verification means determines that the certificate is valid, the client receives the certificate. A certificate acquisition means for transmitting a certificate is provided.

  Further, the present invention provides means for creating a message to “request transmission of the CRL issue notification” in the certificate verification server, means for receiving the CRL issue notification request message in the certificate authority, Further, the CRL issuance notification transmission means of the certification authority transmits the CRL issuance notification to the certificate verification server that has transmitted the CRL issuance notification request message to the certification authority. .

  Further, the present invention provides a CRL issuance notification transmitting means for transmitting a CRL issuance notification indicating that “CRL has been issued”, and “the above CRL issuance” when a new CRL is stored in the CRL repository. The CRL repository is provided with a CRL issuance notification request receiving means for receiving a CRL issuance notification request message stating “Request transmission of notification”.

  The CRL issuance confirmation software of the present invention implements a means for monitoring CRL issuance and transmitting a CRL issuance notification when a new CRL is issued, and receives a CRL issuance notification request message. The CRL issue notification transmitting means transmits the CRL issue notification to the transmission source of the CRL issue notification request message that has been received.

  Further, the certificate verification server according to the present invention is characterized in that means for receiving the CRL issue notification request message created by the CRL issue notification request creation means is provided.

  Therefore, according to the present invention, the validity of the certificate can be surely performed with high accuracy and a small load.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the present invention is not limited thereby.

FIG. 1 is a diagram showing a configuration of an electronic document exchange system with an electronic signature according to an embodiment of the present invention. Nine certification authority from the certification authority _{1 1} to the certification authority _{1 9} (hereinafter, collectively describe the certification authority 1, and), and the certificate repository 2, a CRL repository 3, the certificate validation server _{4 1 N} certificate verification servers up to certificate verification server 4 _n (hereinafter collectively referred to as certificate verification server 4), and request the certificate verification server 4 to verify the validity of the certificate. , m-number of the client terminal from the client terminal 5 ₁ to the client terminal 5 _m (hereinafter, collectively, the client terminal 5, and described) and, are coupled with each other through the network 0.

  The certificate authority 1 issues a certificate 509 to the client terminal 5 and stores a copy of the certificate 509 in the certificate repository 2 and a list of the revoked certificates 509 The CRL issuing function 102 that stores the CRL 7 in the CRL repository and the CRL issue notification 8 that notifies that the CRL 7 has been issued are transmitted to the certificate verification server 4. A CRL issuance notification function 103 and a CRL issuance notification request receiving function 105 for receiving the CRL issuance notification request message 10 to “request transmission of the CRL issuance notification 8”.

Further, from the certificate authority 1 ₁ to the certification authority 1 _9, the certification authority 1, mutually issues a mutual authentication certificate 9, as shown in FIG. 2, a relationship of mutual authentication.

  The certificate repository 2 receives the certificate DB 201 that holds the certificate 509, the certificate 509 from the certificate authority 1, stores the certificate 509 in the certificate DB 201, and A certificate DB management function 202 that retrieves the designated certificate 509 from the certificate DB 201 and sends it back.

  The CRL repository 3 receives the CRLDB 301 that holds the CRL 7 and the CRL 7 from the certificate authority 1, stores the CRL in the CRLDB 301, and further retrieves the specified CRL 7 from the CRLDB 301. And a certificate DB management function 302 for replying.

The certificate verification server 4
A CRL cache 401 that caches the CRL 7;
A verification path cache 402 that caches a verification path, which is used to verify the validity of the certificate 509;
A certificate verification function 403 that receives the request from the client terminal 5 and verifies the validity of the certificate;
Upon receipt of the request from the client terminal 5, the certificate 509 is acquired from the certificate repository 2, and the validity of the certificate 509 is verified by the certificate verification function 403. A certificate acquisition function 404 that returns to the client terminal 5 when the certificate 509 is valid;
A CRL management function 405 for acquiring the CRL 7 from the CRL repository 3 and storing the CRL 7 in the CRL cache 401;
When the CRL issue notification 8 is received from the certificate authority 1 and the CRL issue notification 8 is received from the certificate authority 1, the CRL issue notification request message 10 registered in advance or the CRL issue notification request message 10 is transmitted. A CRL issue notification management function 406 that transfers the CRL issue notification 8 to another certificate verification server 4 that has requested transfer of the CRL issue notification 8 by
The verification path created by the certificate verification function 403 is cached in the verification path cache 402, and the verification path is transmitted to another certificate verification server 4 registered in advance. A verification path management function 407 that caches the verification path received from the certificate verification server 4 in the verification path cache 402;
A CRL issuance notification request creation function 410 that creates a CRL issuance notification request message 10 that requests the certificate authority 1 to transmit the CRL issuance notification 8;
A CRL issuance notification request receiving function 411 that receives the CRL issuance notification request message 10 from another certificate verification server 4.

The client terminal 5
An electronic document exchange function 501 for exchanging an electronic document 6 with another client terminal 5;
An electronic signature function 502 for performing an electronic signature on the electronic document 6 and verifying an electronic signature performed on the electronic document 6 received from another client terminal 5;
A certificate verification request function 503 that requests the certificate verification server 4 to verify the validity of the certificate 509 and receives the result of the validity verification of the certificate 509 from the certificate verification server 4; ,
If the URL indicating the storage location of the certificate 509 is attached to the electronic document 6 instead of the certificate 509, the certificate 509 is used to obtain the certificate 509 stored in the URL. A certificate acquisition request function 506 that transmits the certificate identification information to the verification server 4 and receives the certificate 509 from the certificate verification server 4;
A secret key 508 used by the electronic signature creation function 502;
And the certificate 509 issued by the certificate authority 1.

Note that the certificate 509 ₁ of the client terminal _{5 1} is issued from the certification authority _{1 1,} the certificate 509 ₂ of the client terminal _{5 2} is issued from the certification authority _{1 2.}

Further, in the present embodiment, the above-described certificate validation request function 503, the certificate validation server 4 and the certificate acquisition request function 506, is utilized, the certificate validation server 4 from the certificate validation server 4 ₁ Among the certificate verification servers 4 up to _n , a predetermined specific certificate verification server 4 is used.

For example, the client terminal 5 ₂ utilizes the certificate validation server 4 _1.

  The certificate authority 1, the certificate repository 2, the CRL repository 3, the certificate verification server 4, and the client terminal 5 illustrated in FIG. 1 include, for example, a CPU 91, a memory 92, and the like illustrated in FIG. An external storage device 93 such as a hard disk, a reading device 94 for reading information from a portable storage medium 99 such as a CD-ROM, a communication device 95 for communicating with other devices via a network, a keyboard and a mouse In a general electronic computer having an input device 96 such as a monitor, an output device 97 such as a monitor or a printer, and an interface 98 for transmitting and receiving data between these devices, a CPU 91 is loaded on a memory 92. This can be realized by executing a predetermined program.

  That is, the certificate issuing function 101, the CRL issuing function 102, the CRL issuing notification function 103, the CRL issuing notification request receiving function 105, the certificate DB management function 202, the CRLDB management function 302, the certificate verification function 403, and the certificate acquisition function 404. , CRL management function 405, CRL issue notification management function 406, verification path management function 407, CRL issue notification request creation function 410, CRL issue notification request reception function 411, electronic document exchange function 501, electronic signature function 502, certificate verification request The function 503 and the certificate acquisition request function 504 can be realized as processes by the CPU 91 executing a predetermined program. The certificate DB 201, CRLDB 301, CRL cache 401, and verification path cache 402 can be realized by the CPU 91 using the memory 92 or the external storage device 63.

  On such an electronic computer, a predetermined program for realizing each of the above devices may be introduced from a storage medium 99 that can be used by the electronic computer via a reader 94, or the communication device 96 may be installed. It may be introduced from another server via a communication medium that can be used by an electronic computer, such as a network or a carrier wave propagating through the network.

  At the time of introduction, the data may be temporarily stored in the external storage device 93 and then loaded onto the memory 92 and executed by the CPU 91, or may be directly stored in the memory 92 without being stored in the external storage device 93. It may be loaded on top and executed by the CPU 91.

  Next, the operation of the electronic signature using system of FIG. 1 will be described with reference to the drawings when the certificate verification server 4 requests the certificate authority 1 to transmit the CRL issue notification 8.

  FIG. 7 illustrates the certificate verification server 4 and the authentication when the certificate verification server 4 requests the certificate authority 1 to transmit the CRL issue notification 8 in the electronic signature utilization system of FIG. The operation of station 1 is shown.

  In the certificate verification server 4, the CRL issuance notification request creation function 410 creates the CRL issuance notification request message 10 (step 7101) and transmits it to the certificate authority 1 (step 7102).

  The CRL issue notification request message 10 illustrated in FIG. 8A includes a message “Request transmission of the CRL issue notification 8” and an address on the network 0 that is the transmission destination of the CRL issue notification 8. It consists of a certain host name.

  In the certificate authority 1, when the CRL issuance notification request receiving function 105 receives the CRL issuance notification request message 10 (step 7201), the certificate verification server 4 that has transmitted the CRL issuance notification request message 10 has been transmitted. Are added to the CRL issuance notification transmission destination list 104 (step 7202).

When requesting the transfer of the CRL issuance notification 8 from the certificate validation server 4 ₁ to the certificate validation server 4 _2, first, the certificate validation server 4 ₁ of the CRL issuance notification request generation function 410 create the CRL issuance notification request message 10, transmitted to the certificate validation server 4 _2.

The certificate validation server 4 ₂ CRL issuance notification request reception function 411 receives the CRL issuance notification request message 10, the host name of the certificate validation server 4 that is the sender to the CRL issuance notification forwarding destination list 408 to add.

  When the certificate verification server 4 requests the certificate authority 1 to stop transmitting the CRL issuance notification 8, the CRL issuance notification request message 10 illustrated in FIG. Transmit to station 1.

  The CRL issuance notification request message 10 in FIG. 8B is composed of a message “requests to stop transmission of the CRL issuance notification 8” and the host name of the transmission destination of the CRL issuance notification 8. .

  When the certificate authority 1 receives the CRL issuance notification request message 10 in FIG. 8B, the certificate authority 1 deletes the host name of the certificate verification server 4 described from the CRL issuance notification transfer destination list 408.

  When the certificate verification server 4 requests another certificate verification server 4 to transfer the CRL issuance notification 8 or requests to stop the transfer, the certificate verification server 4 requests the certificate verification server 4 to A CRL issue notification request message 10 is transmitted.

  Next, the operations of the certificate authority 1, the CRL repository 3, and the certificate verification server 4 when the CRL 7 is issued in the electronic signature utilization system of FIG. 1 will be described with reference to the drawings. To do.

  FIG. 3 is a diagram illustrating operations of the certificate authority 1, the CRL repository 3, and the certificate verification server 4 when the CRL 7 is issued in the electronic signature utilization system of FIG.

  First, the operation of the certificate authority 1 will be described.

  In the certificate authority 1, when the CRL issuing function 102 creates the CRL 7 (step 3101), the CRL issuing function 102 transmits the CRL 7 to the CRL repository 3 (step 3102).

  Next, the CRL issue notification function 103 creates the CRL issue notification 8 and requests transmission of the CRL issue notification 8 by transmitting the CRL issue notification request message 10 which is determined in advance. And sent to the certificate verification server 4 (step 3103).

  In this embodiment, the certificate authority 1 transmits the CRL issue notification 8 to the certificate verification server 4 whose host name is described in the CRL issue notification transmission destination list 104.

(A) in FIG. 6 is an example of a CRL issuance notification transmission destination list 104 in which the certification authority 1 manages the host name of the certificate validation server 4 _1, the host of the certificate validation server 4 _n And the name.

Therefore, the CRL issue notification function 103 of the certificate authority ₁ transmits the CRL issue notification 8 to the certificate verification server ₄₁ and the certificate verification server 4 _n .

  Next, the operation of the CRL repository 3 will be described.

  The CRLDB management function 302 of the CRL repository 3 waits for access from the certificate authority 1 or the certificate verification server 4 and receives the CRL 7 from the certificate authority 1 (step 3301). The CRLDB 301 is stored (step 3302), and the access from the certificate authority 1 or the certificate verification server 4 is awaited again.

  On the other hand, when a request is received from the certificate verification server 4 to transmit the CRL 7 (step 3303), the CRL 7 is retrieved from the CRLDB 301 (step 3304), and the CRL 7 is transmitted to the certificate verification server 4. (Step 3305), and again waits for access from the certificate authority 1 or the certificate verification server 4.

  Next, the operation of the certificate verification server 4 will be described.

Here, by the operation of the certificate validation servers 4 ₁ for receiving the CRL issuance notification 8 from the authentication station 1, the operation of the certificate validation server 4.

First, in the certificate validation server _{4 1,} the CRL issuance notification management function 406, the certification authority 1, or other certificate validation server 4 receives the CRL issuance notification 8 (step 3401), First, it is checked whether or not the CRL issuance notification 8 has been received (step 3402). If the CRL issuance notification 8 has already been received, the processing is terminated as it is.

  On the other hand, when the CRL issue notification 8 is received for the first time, the CRL management function 405 accesses the CRL repository 3 (step 3403), acquires the CRL 7 (step 3404), and caches the CRL cache 401. (Step 3405).

  Next, the CRL issue notification management function 406 is registered in advance or another certificate verification server 4 that has requested transfer of the CRL issue notification 8 by transmitting the CRL issue notification request message 10. Then, the CRL issue notification 8 is transferred (step 3406).

  The certificate verification server 4 manages the certificate verification server 4 that transfers the CRL issue notification 6 using a list called a CRL issue notification transfer destination list 408.

(B) in FIG. 6 is an example of the CRL issuance notification forwarding destination list 408 the certificate validation server 4 ₁ manages the host name of the certificate validation server 4 _2, the certificate validation server 4 ₃ and the host name, the host name of the certificate validation server 4 _n is described.

Therefore, the CRL issuance notification management function 406, the CRL issuance notification 6, and the certificate validation server _{4 2,} and the certificate validation server _{4 3,} and transfers to the certificate validation server _{4 n.}

In this embodiment, the host name of each of the above certificate validation server 4 ₁ to the certificate validation server 4 _n, the certificate validation from the certificate validation server 4 ₁ to the certificate validation server 4 _n Each of the CRL issuance notification transfer destination lists 408 held by the server 4 is surely described.

By doing this, if any one of the above certificate validation server 4 receive the CRL issuance notification 6 from the certification authority 1, all the certificates from the certificate validation server 4 ₁ to the certificate validation server 4 _n The certificate verification server 4 can receive the CRL issue notification 6.

Further, in the case of newly adding the certificate validation server 4, the certificate validation server 4 from the certificate validation server 4 ₁ to the certificate validation server 4 _n has in each the CRL issuance If the host name of the certificate verification server 4 is added to any of the notification transfer destination lists 408, there is no need to change the CRL issue notification transmission destination list 104.

  The above is the operation of the electronic signature utilization system in FIG. 1 when the CRL 7 is issued.

Then, the electronic signed electronic document exchange system of Figure 1, from the client terminal 5 _1, to the client terminal 5 _2, an operation of transmitting the electronic document 6 will be described with reference to the drawings.

  In the present embodiment, the certificate 509 for verifying the electronic signature applied to the electronic document 6 is attached to the electronic document 6 and not attached to the electronic document 6. There are two cases. First, the case where the certificate 509 for verifying the electronic signature applied to the electronic document 6 is attached to the electronic document 6 will be described.

FIG. 4 shows an example of the client when the certificate 509 for verifying the electronic signature applied to the electronic document 6 is attached to the electronic document 6 in the electronic document exchange system with an electronic signature shown in FIG. from the terminal 5 _1, to the client terminal 5 _2, when sending the electronic document 6, and the client terminal 5 _1, and the client terminal 5 _2, and the certificate validation server 4 _1, the certificate validation server 4 ₂ is a diagram showing the operation of.

First, the operation of the client terminal 5 _1.

The client terminal _{5 1,} the electronic document exchange function 501 transmits to the client terminal _{5 2,} to create the electronic document 6 (step 4501), the electronic signature function 502, the secret key 508 ₁ Using the electronic document 6, an electronic signature is applied to the electronic document 6 (step 4502).

Then, the electronic document exchange function 501, an electronic signature is applied, the electronic document 6, together with the certificate 509 ₁ is transmitted to the client terminal _{5 2} (step 4503).

Next, the operation of the client terminal 5 _2.

The client terminal 5 ₂ receives the electronic document 6 (step 4511), to verify the validity of the certificate 509 ₁ that has been transmitted together with the electronic document 6, the certificate validity checking functionality 503 but it requests the validation of the certificate 509 ₁ to the certificate validation server _{4 1} (step 4512), receives the result of the validation from the certificate validation server _{4 1} (step 4513).

Here, the efficacy results of the verification, the certificate 509 _1, the not valid for the client terminal 5 _2, when was that, the process ends.

On the other hand, the result of the validity verification, the certificate 509 ₁ is effective for the client terminal 5 ₂ case was that, the electronic signature function 503, a public key from the certificate 509 ₁ The digital signature applied to the electronic document 6 is verified (step 4515). If it is determined that the electronic signature is not correct, the process ends.

  On the other hand, if it is determined that the electronic signature is correct, the electronic signature 6 is stored (step 4516).

  Next, the operation of the certificate verification server 4 will be described.

First, the certificate validation server _{4 1} is asked to validation of the certificate 509 ₁ from the client terminal _{5 2} (step 4401), the certificate validation function 403, from the client terminal _{5 2} verification pass above to the client terminal 5 ₁ confirms whether present in the verification path cache 402 (step 4402).

  Here, if the verification path exists in the verification path cache 402, the process proceeds to step 4404. On the other hand, if the verification path does not exist in the verification path cache 402, the verification path is constructed (step 4403), and the process proceeds to step 4404.

In step 4404, the certificate verification 403 retrieves the CRL 7 from the CRL cache 401 and determines whether or not the verification path is valid. Then sends the determination result to the client terminal _{5 2} (step 4405).

  If the verification path is not newly constructed in step 4403, the process ends. On the other hand, if the verification path is newly constructed in step 4403, the verification path is transmitted to the certificate verification server 4 whose host name is described in the verification path destination list 409. (Step 4407), and the process is terminated.

  The verification path transmission destination list 409 is a list in which the host name of the certificate verification server 4 that transmits the newly constructed verification path is described. In this embodiment, the CRL issuance notification transfer destination list 408 is the above-described list. It is also used for the verification path transmission destination list 409.

Accordingly, in step 4407, the verification pass is a the certificate validation server 4 _2, and the certificate validation server 4 _3, is transmitted 4 and _n the certificate validation server to.

  In this embodiment, the same list is used for the CRL issuance notification transfer destination list 408 and the verification path transmission destination list 409. However, the present invention is not limited to this and is different for each. A list may be used.

On the other hand, these and certificate validation server 4 _2, these and certificate validation server 4 _3, the certificate validation server 4 _n receives the verification pass from the certificate validation server 4 ₁ (step 4411), the The verification path management function 407 confirms whether the verification path is cached in the verification path cache 402 (step 4412).

  Here, if the verification path is cached in the verification path cache 402, nothing is done and the process is terminated. On the other hand, if the verification path is not cached in the verification path cache 402, the verification path is cached in the verification path cache 402 (step 4413), and the host name is described in the verification path destination list 409. The verification path is transmitted to the certificate verification server 4 (step 4414), and the process ends.

  In the present embodiment, the verification path management function 407 of the certificate verification server 4 transmits / receives a verification path and caches it. However, the present invention is not limited thereto, Verification path information that can uniquely identify the verification path may be transmitted / received or cached, and a corresponding verification path may be configured from the verification path information when necessary.

Or, in the case where the certificate 509 to verify the electronic signature applied to the electronic document 6 is attached to the electronic document 6, the electronic document to the client terminal 5 ₂ from the client terminal 5 ₁ 6 Is an operation of the electronic document exchange system with an electronic signature of FIG.

Next, the case where the certificate 509 to verify the electronic signature applied to the electronic document 6 is not attached to the electronic document 6, the electronic document 6 to the client terminal 5 ₂ from the client terminal 5 ₁ The operation of the electronic document exchange system with an electronic signature in FIG. 1 at the time of transmission will be described with reference to the drawings.

FIG. 5 shows the client terminal when the certificate 509 for verifying the electronic signature applied to the electronic document 6 is not attached to the electronic document 6 in the electronic document exchange system with an electronic signature shown in FIG. 5 ₁ from when sending the electronic document 6 to the client terminal 5 _2, and the client terminal 5 _1, and the client terminal 5 _2, and the certificate validation server 4, and the certificate repository 2, the operation FIG.

First, the operation of the client terminal 5 _1.

The client terminal _{5 1,} the electronic document exchange function 501 transmits to the client terminal _{5 2,} to create the electronic document 6 (step 5501), the electronic signature function 502, the secret key 508 ₁ By using the electronic document, an electronic signature is applied to the electronic document 6 (step 5502).

Then, the electronic document exchange function 501, an electronic signature is applied, the electronic document 6, together with the URL showing the location of the certificate 509 ₁ is transmitted to the client terminal _{5 2} (step 5503) .

  In the present embodiment, a URL indicating the storage location of the certificate 509 is transmitted together with the electronic document 6. However, the present invention is not limited to this, and the certificate 509 is stored in the certificate 509. A part of the described information may be transmitted.

Next, the operation of the client terminal 5 _2.

The client terminal 5 ₂ receives the electronic document 6 (step 5511), the certificate acquisition request function 504, the said certificate 509 ₁ corresponding to the URL transmitted together with the electronic document 6 asked to obtain the certificate validation server _{4 1} (step 5512), receives the request result from the certificate validation server _{4 1} (step 5513).

Here, if it was not the certificate 509 ₁ included in the request results, i.e., the certificate 509 ₁ indicated by the URL is not valid for the client terminal 5 _2, and the certificate validation server 4 _{If 1} is determined, the process is terminated. On the other hand, if you have the certificate 509 ₁ included in the request result, the electronic signature function 503 extracts the public key from the certificate 509 _1, verifies the electronic signature has been applied to the electronic document 6 (Step 5515). If it is determined that the electronic signature is not correct, the process ends. On the other hand, if it is determined that the electronic signature is correct, the electronic signature 6 is stored (step 5516), and the process is terminated.

  Next, the operation of the certificate verification server 4 will be described.

The certificate validation server _{4 1} of the certificate obtaining function 404, from the client terminal _{5 2,} when receiving a request to acquire the certificate 509 ₁ (step 5401), transmitted from the client terminal _{5 2} by using the above URL, it accesses the certificate repository 2 (step 5402), obtains the certificate 509 ₁ (step 5403).

Next, it is determined by the certificate validation function 403, the certificate 509 _1, taken on the client terminal _{5 2,} whether it is valid certificate (step 5404).

  Here, the operation of the certificate verification function 403 is the same as the operation from step 4402 to step 4409 in FIG.

By the determination, the certificate 509 _1, taken on the client terminal 5 _2, when it is determined that a valid certificate, and creates a request results including the certificate 509 ₁ (step 5405), the client to the terminal _{5 2} (step 5407). On the other hand, the certificate 509 _1, taken on the client terminal 5 _2, if it is determined not a valid certificate, and is the client terminal as to create a request result indicating "not valid" effect (step 5406) 5 transmits ₂ (step 5407).

  Next, the operation of the certificate repository 2 will be described.

The certificate DB management function 202 of the certificate repository 2, from the certificate validation server _{4 1} receives a request to send the certificate 509 ₁ (step 5201), the certificate from the certificate DB201 Find the book 509 ₁ (step 5202) and sends the certificate 509 ₁ to the certificate validation server 4 (step 5203).

Or, in the case where the certificate 509 to verify the electronic signature applied to the electronic document 6 is not attached to the electronic document 6, the electronic document 6 to the client terminal 5 ₂ from the client terminal 5 ₁ It is operation | movement of the electronic document exchange system with an electronic signature of FIG. 1 at the time of transmission.

  As described above, in the electronic document exchange system with an electronic signature according to the present embodiment, when the certificate authority 1 issues the CRL 7, the CRL issue notification 8 is described and the host name is described in the CRL issue notification transmission destination list 104. Sent to the certificate verification server 4 to notify the certificate verification server 4 that the CRL 7 has been issued, and the certificate verification server 4 that has received the CRL issue notification 8 The CRL 7 is acquired from the CRL repository 3 and cached.

  For this reason, even when the certificate authority 1 issues the CRL 7 urgently, since the CRL cached by the certificate verification server 4 is the latest, the validity verification result of the certificate 509 Accuracy can be guaranteed.

  In the electronic document exchange system with an electronic signature of this embodiment, the certificate verification server 4 that has received the CRL issuance notification 8 has a host name described in the CRL issuance notification transfer destination list 408. The CRL issue notification 8 is transferred to the certificate verification server 4.

  Therefore, even when a new certificate verification server 4 is added, the host name of the new certificate verification server 4 is simply described in the CRL issuance notification transfer destination list 408 of the certificate verification server 4. The CRL issue notification 8 can be received, and there is no need to change the setting on the certificate authority 1 side.

  Moreover, in the electronic document exchange system with an electronic signature of the present embodiment, when the certificate verification server 4 receives the verification path from another certificate verification server 4, the verification path is cached, and the above When the certificate verification server 4 newly constructs a verification path, the new verification path is transmitted to another certificate verification server 4 whose host name is described in the verification path transmission destination list 409. I am doing so.

  For this reason, since the verification path can be shared among the plurality of certificate verification servers 4, access to the certificate repository 2 and the CRL repository 3 is concentrated, and the load on the network increases. Can be prevented.

  Furthermore, in the electronic document exchange system with an electronic signature of the present embodiment, when the client terminal 5 receives a URL indicating the storage location of the certificate 509, the client terminal 5 does not access the certificate repository 2, The certificate verification server 4 is requested to acquire the certificate 509, and the certificate verification server 4 determines that the certificate 509 acquired from the certificate repository 2 is a certificate that is valid for the client terminal 5. The certificate 509 is returned to the client terminal 5 only in the case of

  For this reason, the client terminal 5 does not need to be equipped with a function for accessing the certificate repository 2.

  In the present embodiment, the CRL issue notification 8 includes only the notification that “CRL has been issued”, but the present invention is not limited to this.

  For example, the CRL issue notification 8 includes the newly issued CRL 7 itself, or includes difference information between the previously issued CRL 7 and the newly issued CRL 7. May be. Furthermore, a list of identification information of the newly revoked certificate 509 may be included.

  In the CRL issue notification 8, a list of the newly issued CRL 7 itself, difference information between the previously issued CRL 7 and the newly issued CRL 7, and identification information of the newly revoked certificate 509 are displayed. By including, the certificate verification server 4 that has received the CRL issue notification 8 can omit the process of accessing the CRL repository 3 and obtaining the newly issued CRL 7.

  In the present embodiment, the certificate authority 1 transmits the CRL issue notification 8 and receives the CRL issue notification request message 10. However, the present invention is not limited to this. For example, the CRL repository 3 may transmit the CRL issue notification 8 and receive the CRL issue notification request message 10.

  Alternatively, the CRL repository 3 is installed with CRL issuance confirmation software that implements a function of monitoring the issuance of the CRL 7 and transmitting the CRL issuance notification 8 when it is confirmed that a new CRL 7 has been issued. The CRL issuance confirmation software may realize the CRL issuance notification request reception function, and the CRL issuance notification transmission function may transmit the CRL issuance notification to the transmission source of the received CRL issuance notification request message.

  By using the CRL issue confirmation software, it is possible to use the certificate authority 1 and the CRL repository 3 that do not have the CRL issue notification transmission function. Furthermore, if the CRL issuance notification request receiving function manages the transmission destination of the CRL issuance notification, the number of the certificate verification servers can be set even if the operator of the CRL repository is different from the operator of the certificate verification server. It can be changed flexibly.

  According to the present embodiment, the CRL issuance notification is only issued from the certification authority to the certificate verification server when the certification authority issues the CRL. Therefore, the CRL is issued at regular intervals. It is not necessary to check whether the network 0 is present, and the load on the network 0 can be reduced.

  Further, since the CRL issuance notification 8 is performed by the certificate authority 1, even when the operators of the CRL repository 3 and the certificate verification server 4 are different, highly accurate certificate validity verification can be performed. .

  Further, since the certificate verification server 4 can request the transmission of the CRL issue notification 8 by transmitting the CRL issue notification request message 10, the operator of the CRL repository 3 and the certificate verification server can be requested. The number of certificate verification servers 4 can be flexibly changed even if the number of operators is different.

  Further, when the certificate verification server finds that a new CRL has been issued, the certificate verification server notifies the other certificate verification server that the new CRL has been issued.

  If you want to change the certificate verification server to be sent, you need to change the settings of the certificate verification server. Therefore, even if the CRL repository operator and the certificate verification server operator are different, the certificate The number of certificate verification servers can be flexibly changed.

  Further, when the certificate verification server newly builds a verification path, the verification path is transferred to other certificate verification servers and the verification path is shared, so that the specific CRL repository or the certificate repository is shared. Access concentration and network load can be reduced.

  In addition, when using a method of separately obtaining the certificate, the client does not access the certificate repository to obtain the certificate, but instead obtains the certificate from the certificate verification server. Since it is requested to acquire and verify the validity of the certificate, it is not necessary for the client to implement a function for accessing the certificate repository and acquiring the certificate.

It is a figure which shows the system configuration | structure of the electronic document exchange system with an electronic signature to which one Embodiment of this invention was applied. FIG. 2 is a diagram showing a mutual authentication relationship between certificate authorities 1 in the electronic document exchange system with an electronic signature in FIG. 1. FIG. 3 is a diagram illustrating an operation when a CRL 7 is issued in the electronic document exchange system with an electronic signature in FIG. 1. FIG. 7 is a diagram showing an operation when the client terminal 5 sends and receives the electronic document 6 when the certificate 509 is sent together with the electronic document in the electronic document exchange system with an electronic signature of FIG. 1. FIG. 6 is a diagram showing an operation when the client terminal 5 sends and receives the electronic document 6 when the certificate 509 is not sent together with the electronic document in the electronic document exchange system with an electronic signature of FIG. 1. 5 is a diagram illustrating an example of a CRL issue notification transmission destination list 104 and a CRL issue notification transfer destination list 408. FIG. FIG. 3 is a diagram showing an operation when the certificate verification server 4 requests the certificate authority 1 to transmit a CRL issue notification 8 in the electronic document exchange system with an electronic signature in FIG. 1. 6 is a diagram illustrating an example of a CRL issue notification request message 10. FIG. It is a figure which shows the hardware structural example of each of the certification authority 1, the certificate repository 2, the CRL repository 3, the certificate verification server 4, and the client terminal 5 which are shown in FIG.

Explanation of symbols

0 ... Network, 1, 1 ₁ to 1 ₉ ... Certificate Authority, 2 ... Certificate Repository, 3 ... CRL Repository, 4, 4 ₁ -4 _n ... Certificate Verification Server, 5 5 _{1 to} 5 _m: Client terminal, 6: Electronic document, 7: CRL, 8: CRL issuance notification, 9: Mutual authentication certificate, 10: CRL issuance notification request Message, 91 ... CPU, 92 ... Memory, 93 ... External storage device, 94 ... Reading device, 95 ... Communication device, 96 ... Input device, 97 ... Output device, 98 ... Interface, 99 ... Storage medium, 104 ... CRL issuance notification transmission destination list, 408 ... CRL issuance notification transfer destination list, 409 ... Verification path transmission destination list, 508, 508 _1- 508 _m: secret key, 509, 509 ₁ ~ 509 _m ... Certificate.

Claims (9)

A certificate validity verification means for verifying the validity of the certificate;
CRL management means for obtaining a CRL from the CRL repository device;
CRL caching means for caching the CRL;
CRL issue notification receiving means for receiving a CRL issue notification for notifying that "a new CRL has been issued" from another device, and
The certificate verification server device, wherein the CRL management unit acquires the newly issued CRL from the CRL repository device when the CRL issue notification reception unit receives the CRL issue notification. The certificate verification server device according to claim 1,
Monitoring the issuance of the CRL, triggered by the detection that a new CRL has been issued,
A certificate verification server apparatus comprising: a CRL issuance notification transmission unit configured to transmit the CRL issuance notification to another apparatus registered in advance. The certificate verification server device according to claim 1 or 2,
A certificate verification server apparatus, comprising: a CRL issuance notification request creating unit that requests the other apparatus to transmit the CRL issuance notification, creates a CRL issuance notification request message. The certificate verification server device according to claim 3,
CRL issue notification request receiving means for receiving the CRL issue notification request message from another device and adding the other device to the CRL issue notification transfer destination list;
CRL issue notification management means for transferring the CRL issue notification to a device described in the CRL issue notification transfer destination list upon receipt of the CRL issue notification. apparatus. A certificate validity verification means for verifying the validity of the certificate;
Verification path cache means for caching the verification path constructed by the certificate validity verification means for verifying the validity of the certificate;
A verification path destination list that describes devices that transfer the newly constructed verification path;
A verification path transmitting means for transmitting the verification path to a device described in the verification path transmission destination list when the verification path is constructed,
The certificate verification server apparatus, wherein the verification path cache means caches the verification path when the verification path is received from another apparatus. A CRL repository apparatus having a CRL storage means for storing a CRL issued by a certificate authority,
CR that is a list of devices that transmit a CRL issuance notification notifying that “CRL has been issued”
Manage L issue notification destination list,
The CRL storage means sends a CRL issuance notification when the new CRL is stored.
A CRL repository apparatus comprising: CRL issuance notification transmission means for transmitting to an apparatus described in the L issuance notification transmission destination list. The CRL repository apparatus according to claim 6 , wherein
A CRL issuance notification request receiving means for receiving a CRL issuance notification request message;
The CRL issuance notification request receiving means, when receiving a CRL issuance notification request message, adds a transmission source of the CRL issuance notification request message to the CRL issuance notification transmission destination list. An electronic signature verification means for verifying the electronic signature;
A certificate validity verification requesting means for requesting the certificate verification server device to verify the validity of the certificate;
Obtaining the certificate necessary for verifying the electronic signature and transmitting the information for obtaining the certificate stored in a certificate repository to the certificate verification server device, thereby verifying the certificate. And a certificate acquisition requesting means for requesting the server device. In the computer,
Monitor CRL issuance,
CR that is a list of devices that transmit a CRL issuance notification notifying that “CRL has been issued”
Manage L issue notification destination list,
Triggered by the detection that a new CRL has been issued, the CRL issue notification is sent to the CRL
CRL issuance notification transmission means for transmitting to the device described in the issuance notification transmission destination list;
CRL issue notification request receiving means for receiving a CRL issue notification request message and adding a transmission source of the CRL issue notification request message to the CRL issue notification transmission destination list. .

Images