JP6343425B2 - Authentication infrastructure system with user authority confirmation function - Google Patents

Description

  The present invention relates to an authentication infrastructure system with a user authority confirmation function for a user who needs to be revoked within a validity period for a user who is authenticated by a certificate authority.

  Conventionally, in order to revoke users who need to be revoked within the expiration date, users who have been authenticated by a certificate authority can use revocation lists or use OCSP (Online Certificate Status Protocol). The operation method is widely used. In order to check the validity of a user, a service providing system that provides various services via the Internet not only checks the validity of a certificate but also checks whether it is listed on a revocation list or OCSP. It is common to check the validity of a user by using.

  As methods for confirming the effectiveness of such a user, there are methods disclosed in Patent Document 1 and Patent Document 2. Patent Document 1 discloses a mutual authentication system in which users are mutually authenticated by using an authentication server that is mutually trusted among users, and encrypted data is delivered and received safely. In Patent Document 1, a composite key is generated from a secret key and a public key, stored in an authentication server, and the management number and public key of the composite key issued by the authentication server are sent to the other user. At the time of authentication, the other user generates a composite key using the sent public key and his / her private key, and verifies whether it matches the composite key registered in the authentication server.

Japanese Patent Laid-Open No. 2002-300155 JP 2005-500740 A

  However, the methods disclosed in Patent Document 1 and Patent Document 2 are based on the premise that the system is operating normally, and when communication tampering or tampering is performed on the way, or when decryption program analysis or tampering is performed. In such a case, the validity of the user cannot be confirmed correctly, and there is a problem that the same processing as that of a valid user can be executed for an ineffective user. For example, when an employee who belongs to a company retires, there is a case where it is not possible to prevent the act of taking out a secret key and an electronic certificate, obtaining secret information, and decrypting it.

  Therefore, the present invention can prevent decryption by an unauthorized user by allowing the user to decrypt the encrypted data only when the authority of the user attempting to decrypt the encrypted data can be confirmed. The purpose is to provide an authentication infrastructure system with a user authority confirmation function.

(1) An authentication infrastructure system with a user authority confirmation function according to the present invention provides encrypted data to a user belonging to a predetermined organization authenticated by a certificate authority via a user terminal device used by the user. An authentication infrastructure system with a user authority confirmation function provided with a service providing system for providing a service necessary for decryption of the user, wherein the user terminal includes a decryption execution unit for decrypting the encrypted data A validity determining unit that determines whether or not authentication by the user's certificate authority is valid when the user uses the service providing system via the user terminal, and the validity determination The service providing system does not provide the user with the service if the user is not authenticated using the unit, and the user has the authority to decrypt the encrypted data. And generating a user authentication ticket data indicating whether or not, and generating a tally data having a part of the user authentication ticket data and having the user ID, and the tally data An authority management station storage unit for storing, wherein the certificate authority stores revocation information of the user ID, and the decryption execution unit includes an electronic signature having the user ID. The data can be transmitted to the validity determination unit, and when the validity determination unit receives the inquiry data, the revocation information of the user ID includes the electronic signature in the inquiry data. It is determined whether or not the user ID is registered, and it is determined that the user ID related to the electronic signature in the inquiry data is registered in the revocation information of the user ID. If it is determined that the user is not valid, and it is determined that the user ID in the inquiry data is not registered in the revocation information of the user ID, the electronic signature It is determined whether or not the user ID and the user ID in the tally data stored in the authority management station storage unit match, and whether or not the authentication in the user certificate authority is valid. It is characterized by determining .

  According to the present invention, it is possible to prevent decryption by an unauthorized user by permitting the user to decrypt the encrypted data only when the authority of the user attempting to decrypt the encrypted data can be confirmed. it can.

It is explanatory drawing which shows the outline | summary of the authentication infrastructure system with a user authority confirmation function. It is a functional block diagram of an authentication infrastructure system. It is explanatory drawing which shows an example of the authentication information memorize | stored in the memory | storage part of 1 A of user terminal devices. It is explanatory drawing which shows an example of the authentication information memorize | stored in the memory | storage part of the user terminal device 1B. It is explanatory drawing which shows an example of the authentication information memorize | stored in an authority management station memory | storage part. It is explanatory drawing which shows an example of the authentication information memorize | stored temporarily in a encryption production | generation part. It is explanatory drawing which shows an example of the authentication information memorize | stored temporarily in a decoding implementation part. It is explanatory drawing which shows an example of the authentication information memorize | stored temporarily in a tally reception part. It is explanatory drawing which shows an example of the authentication information memorize | stored temporarily in a user validity confirmation part. It is a figure which shows the flowchart of the encryption processing routine which the encryption production | generation part of a user terminal device performs. It is a figure which shows the flowchart of the decoding process routine which the decoding implementation part of a user terminal device performs. It is a figure which shows the flowchart of the tally reception process routine which the tally reception part of an authority management station performs. It is a figure which shows the flowchart of the user validity confirmation processing routine which the user validity confirmation part of an authority management station performs. One pattern of the method of confirming revocation is shown. One pattern of the method of confirming revocation is shown. One pattern of the method of confirming revocation is shown. One pattern of a use form in the case of dividing a user authentication ticket into a plurality is shown.

  Hereinafter, an authentication infrastructure system with a user authority confirmation function according to an embodiment of the present invention will be specifically described with reference to the drawings.

(Overall configuration of authentication infrastructure system 100 with user authority confirmation function)
As shown in FIG. 1, an authentication infrastructure system 100 with a user authority confirmation function includes a user terminal device 1, an authentication authority 2, an authority management authority 3 that is a third party who trusts the authentication authority 2, and a service provision System 4.

(Configuration of user terminal device 1)
As shown in FIG. 1, the user terminal device 1 (1A, 1B) is a terminal device used by a user 500 (users 500A, 500B in this embodiment) to use the service providing system 4. The authority for using the service providing system 4 by using the authority management station 3 can be managed. As illustrated in FIG. 2, the user terminal device 1 (1A, 1B) includes a storage unit 101, an encryption generation unit 102, a decryption execution unit 103, and a service providing system client unit 104. In the following, among a plurality of users 500 belonging to the same organization, the user 500A creates encrypted data using the user terminal device 1A, and the partner user 500B uses the user terminal device 1B as the encrypted data. The case where decoding is performed will be described. Note that the user terminal devices 1A and 1B are not originally required to be specifically distinguished from each other (the storage unit 101, the encryption generation unit 102, and the decryption execution unit 103), but in the present embodiment, For the convenience of describing the operation of decrypting the encrypted data generated by the encryption generation unit 102 of the user terminal device 1A by the decryption execution unit 103 of the user terminal device 1B, the operation is stored in the storage unit 101A of the user terminal device 1A. The authentication information stored in the storage unit 101B of the user terminal device 1B and the authentication information stored in the storage unit 101B of the user terminal device 1B are shown separately in FIGS. Similarly, FIG. 6 illustrates only temporary data in the encryption generation unit 102 of the user terminal device 1A, and FIG. 7 illustrates only temporary data in the decryption execution unit 103 of the user terminal device 1B. Decline in advance.

(Configuration of storage unit 101)
As shown in FIGS. 3 and 4, the storage unit 101 stores a personal certificate 12 (PKI (Public Key Infrastructure), ID-based encryption, attribute-based encryption, etc.) of the user 500 and a secret corresponding to the personal certificate 12. The key 10, the public key 11, the public key 21 of the certificate authority 2, and the certificate 22 of the certificate authority 2 can be stored. Note that the portion of the storage unit 101 that stores the secret key 10 may be an external storage device such as an IC card. In addition, the security performance can be further improved by providing the portion storing the secret key 10 with tamper resistance.

(Configuration of the encryption generation unit 102)
The cipher generation unit 102 is configured to receive a request from the service providing system client unit 104, perform cryptographic processing, and return the result to the service providing system client unit 104. Furthermore, the encryption generation unit 102 is configured to be able to temporarily store various types of authentication information. FIG. 6 is an explanatory diagram illustrating an example of authentication information temporarily stored in the encryption generation unit 102. As shown in FIG. 6, the encryption generation unit 102 includes a user private key 10A, a user public key 11A, a partner user public key 11B, a user personal certificate 12A, and a partner user's public key 11A. The personal certificate 12B, the user ID 13A, and the partner user ID 13B are temporarily stored. Further, secret information 40, common key 41, encrypted data 42, user authentication ticket data 43, tally data 46, and encrypted data 48 are temporarily stored in the encryption generation unit 102.

(Configuration of Decoding Implementation Unit 103)
The decryption execution unit 103 is configured to receive a request from the service providing system client unit 104, perform a decryption process, and return the result to the service providing system client unit 104. Furthermore, the decryption execution unit 103 is configured to be able to temporarily store various types of authentication information. FIG. 7 is an explanatory diagram showing an example of authentication information temporarily stored in the decryption execution unit 103. As shown in FIG. 7, the decryption execution unit 103 includes a user private key 10B, a user certificate 12B, a user ID 13B, a public key 21 of the certificate authority 2, and a certificate of the certificate authority 2. The book 22 is temporarily stored. Further, in the decryption execution unit 103, encrypted data 48, inquiry data 49, tally data 46, user authentication ticket data 43, common key 41, encrypted data 42, and secret information 40 are temporarily stored.

(Configuration of service providing system client unit 104)
The service providing system client unit 104 transmits a request for causing the encryption generation unit 102 to perform encryption processing to the encryption generation unit 102, and transmits a request for causing the decryption execution unit 103 to perform decryption processing. The processing result of the cipher generation unit 102 or the decryption execution unit 103 can be received.

(Configuration of Certificate Authority 2)
The certificate authority 2 is a general certificate authority used in a public key authentication infrastructure, an ID-based encryption method, an attribute-based encryption method, and the like, and is configured to be able to authenticate a user 500 for using the service providing system 4. ing. As shown in FIGS. 1 and 2, the certificate authority 2 stores validity information 20, a certificate authority public key 21, and a certificate authority certificate 22. Here, “validity information” is information indicating that the user 500 has the authority to decrypt encrypted data, and includes attribute information such as revocation information and expiration date of the user 500.

(Authority management station 3)
As shown in FIGS. 1 and 2, the authority management station 3 has an effectiveness determining unit 300 that can determine the effectiveness of the user 500 who uses the service providing system 4. As shown in FIG. 2, the validity determination unit 300 includes an authority management station storage unit 301, a tally reception unit 302, and a user validity confirmation unit 303.

(Configuration of authority management station storage unit 301)
The authority management station storage unit 301 includes a tally DB (Data Base) 30 as shown in FIG. As shown in FIG. 5, the tally DB 30 is configured to be able to record the message ID and tally data sent from the user terminal device 1.

(Configuration of tally accepting unit 302)
The tally accepting unit 302 is configured to be able to store the tally data 46 in response to a request from the user terminal device 1. FIG. 8 is an explanatory diagram showing an example of authentication information temporarily stored in the tally accepting unit 302. As shown in FIG. 8, tally data 46 and a message ID 47 are temporarily stored in the tally accepting unit 302.

(Configuration of user validity checking unit 303)
The user validity confirmation unit 303 is configured to be able to confirm the validity of the user 500 in response to a request from the user terminal device 1. FIG. 9 is an explanatory diagram showing an example of authentication information temporarily stored in the user validity checking unit 303. As shown in FIG. 9, inquiry data 49 and tally data 46 are temporarily stored in the user validity confirmation unit 303.

(Configuration of service providing system 4)
The service providing system 4 is configured to be able to provide a service based on a request from the service providing system client unit 104 incorporated in the user terminal device 1. The “service” here means that the user (user 500B in the present embodiment) decrypts the encrypted data created by the other user (user 500A in the present embodiment) and is necessary for decrypting the encrypted data. In addition to services that relay and store messages, such as mail servers, for example, services such as file sharing servers and database servers that store data and are provided according to predetermined rules are included. Further, the service providing system 4 includes a service providing system server unit 401 as shown in FIG.

(Configuration of service providing system server unit 401)
Although the encrypted data 48 is sent to the service providing system server unit 401, the service providing system server unit 401 does not recognize that it is encrypted information, and handles it as simple binary data. If the authentication system is incorporated on the client side of the service providing system 4, the service providing system server unit 401 is not affected by the authentication infrastructure system and can be used within the range of existing services. For example, in the case of a mail server, binary data is stored as an attached material, and browsing can be performed only at the client unit. It can also be used for file management systems. In a system that cannot handle binary data, it can be converted into a text file and used. However, there are cases where it cannot be used if there is a limit on the data capacity.

(Operation procedure of authentication infrastructure system 100 with user authority confirmation function)
Next, the operation procedure of the authentication infrastructure system with user authority confirmation function 100 will be described with reference to the flowcharts of FIGS.

(Prerequisite for operation explanation)
Here, as a precondition for explaining the operation, it is assumed that all users 500 who use the service providing system 4 have issued personal information from the common certificate authority 2. That is, it is assumed that the certificate authority 2 is trusted by all users 500, and the authority management station 3 that trusts the certificate authority 2 is also trusted by all users 500. In the following, using the authentication infrastructure system with user authority confirmation function 100, the encrypted data for the user 500B created by the user 500A is shared using the service providing system 4 until the user 500B decrypts it. Shows the procedure.

(Explanation of cryptographic processing flow)
FIG. 10 is a diagram illustrating a flowchart of an encryption processing routine executed by the encryption generation unit 102 of the user terminal device 1A.

  The cipher generation unit 102 receives the secret information 40 from the service providing system client unit 104 and stores it in the storage unit 101 (S1).

  A common key used for encryption is randomly generated and used as a common key 41 (S2).

  The secret information 40 is encrypted using the common key 41 to generate encrypted data 42 (S3).

  The common key 41 is encrypted by using the public key 11B of the partner user 500B to obtain user authentication ticket data 43 (S4). Here, the “user authentication ticket data” is data used for confirming whether or not the decryption person is an authorized user.

  The user authentication ticket data 43 is divided into two by a method such as a secret sharing method, one of which is user authentication tally data A44 and the other is user authentication tally data B45 (S5).

  The ID 13B of the partner user 500B and the user authentication tally data A44 are combined to form tally data 46 (S6).

  The tally data 46 is transmitted to the tally accepting unit 302 of the authority management station 3, and the message ID 47 returned from the tally accepting unit 302 is received (S7). Here, the “message ID” is a unique ID generated in units of tally data 46 sent to the authority management station 3.

  The message ID 47, the encrypted data 42, and the user authentication tally data B45 are combined to generate encrypted data 48 (S8).

  The encrypted data 48 is returned to the service providing system client unit 104 as the request source as encrypted data of this encryption function (S9).

(Description of decryption process flow)
FIG. 11 is a diagram illustrating a flowchart of a decryption processing routine executed by the decryption execution unit 103 of the user terminal device 1B.

  The decryption execution unit 103 receives the encrypted data 48 from the service providing system client unit 104 (T1).

  The message ID 47, the encrypted data 42, and the user authentication tally data B45 are extracted from the encrypted data 48 (T2).

  The message ID 47 is digitally signed with the user's private key 10B, and the generated digital signature 50 of the message ID is concatenated with the message ID 47 to obtain inquiry data 49 (T3).

  The inquiry data 49 is sent to the authority management station 3 (T4).

  The processing is divided according to the response from the authority management station 3 (T5).

  If the response from the authority management station 3 is abnormal, an error is returned to the service providing system client unit 104 that is the request source as having no authority (T6).

  If the response from the authority management station 3 is normal, the tally data 46 is received from the authority management station 3 as having authority (T7).

  The user authentication tally data A44 is extracted from the tally data 46 and combined with the user authentication tally data B45 to generate user authentication ticket data 43 (T8).

  The user authentication ticket data 43 is decrypted using the user's private key 10B, and the common key 41 is extracted (T9).

  The encrypted data 42 is decrypted using the common key 41, and the secret information 40 is extracted (T10).

  The secret information 40 is returned to the service providing system client unit 104, which is the request source, as decrypted data of this encryption function (T11).

(Explanation of tally acceptance processing flow)
FIG. 12 is a flowchart of the tally acceptance processing routine executed by the tally acceptance unit 302 of the authority management station 3.

  The tally accepting unit 302 receives the tally data 46 from the encryption generating unit 102 of the user terminal device 1A (U1).

  A message ID 47 is generated so that the tally data 46 to be registered in the tally DB 30 is unique (U2).

  The tally data 46 is stored in the authority management station storage unit 301 using the message ID 47 as a key. (U3)

  The message ID 47 is returned to the encryption generation unit 102 of the user terminal device 1A that is the request source (U4).

(Explanation of user validity check flow)
FIG. 13 is a flowchart of a user validity confirmation processing routine executed by the user validity confirmation unit 303 of the authority management station 3.

  The user validity confirmation unit 303 receives the inquiry data 49 from the decryption execution unit 103 of the user terminal device 1B (V1).

  The inquiry data 49 is decomposed into a message ID 47 and an electronic signature 50 of the message ID (V2).

  The electronic signature 50 of the message ID is verified (V3).

  The processing is divided according to the check result of the electronic signature 50 (V4).

  If there is a problem with the check result of the electronic signature 50, an error is returned to the request source as having no authority (V5).

  If there is no problem with the check result of the electronic signature 50, the user ID 13B is extracted from the electronic signature 50 (V6).

  It is confirmed whether the user ID 13B is registered in the revocation list of the certificate authority 2 (V7).

  The processing is divided depending on whether or not the user ID 13B is registered in the revocation list (V8).

  If the user ID 13B is registered in the revocation list, an error is returned to the request source as having no authority (V5).

  If the user ID 13B is not registered in the revocation list, the tally DB 30 is searched with the message ID 47 as having authority, and the corresponding tally data 46 is extracted (V9).

  It is checked whether or not the user ID 13 of the tally data 46 matches the user ID of the electronic signature, and the processing is divided according to the result (V10).

  If the user ID 13 of the tally data 46 does not match the user ID of the electronic signature, an error is returned to the request source as having no authority (V5).

  If the user ID 13 of the tally data 46 matches the user ID of the electronic signature, the tally data 46 is retrieved and returned to the decryption execution unit 103 that is the request source (V11).

  Note that when using a tamper-resistant device such as an IC card, the decryption execution unit 103 is arranged with a secret key inside the tamper-resistant device.

  The public key 11B, personal certificate 12B, and ID 13B of the partner user 500B may be acquired from the user terminal device 1B of the partner user 500B or may be acquired from the certificate authority 2. A plurality of the public key 11B, personal certificate 12B, and ID 13B of the partner user 500B may be stored in the storage unit 101. The public key 21 of the certificate authority and the certificate 22 of the certificate authority are preferably obtained from the certificate authority 2 and stored in the storage unit 101 when the system is introduced.

(Characteristics of the authentication infrastructure system 100 with a user authority confirmation function according to the present embodiment)
According to the above configuration, when the other user 500B decrypts the encrypted data created by the user 500A, the authority of the other user 500B attempting to decrypt the encrypted data is confirmed by the user validity checking unit 303. Only in some cases, the decryption of the encrypted data is permitted to the user 500B, so that decryption by an unauthorized user can be prevented. This is to confirm whether or not the user who decrypts the encrypted data has the authority at the time of decryption etc. Even if the communication data or logic is tampered with, It provides a mechanism in which confirmation cannot be avoided. This allows for secure user authentication.

  According to the above configuration, the user 500B obtains the key used for the decryption process of the encrypted data or the data from which the key can be taken out only after the validity of the user 500B is confirmed by the user validity confirmation unit 303. It can be obtained from the authority management station 3. This allows for secure user authentication.

  According to the above configuration, when there are a plurality of users 500 belonging to the same organization and there are a provider and a receiver of confidential information, the user 500A who provides the confidential information encrypts the confidential information. By passing the confidential information to the user 500B receiving the confidential information, the confidential information can be safely transferred. At this time, if the user 500B leaves his / her organization while having his / her own authority, the affiliated organization reports the revocation of the user 500B to the certificate authority 2, and the previously encrypted data and user The private key of 500B can be disabled.

  According to the above configuration, the user 500A can use the encryption that can be decrypted by the user 500B who trusts the same certificate authority 2 by performing encryption using the public key distributed from the certificate authority 2. . At the time of decryption, if the user 500B has been revoked within the validity period of the certificate, the user 500B who has been revoked is configured by inquiring the authority management station 3 when performing decryption processing by the user 500B. Can be prevented from being decrypted.

  As mentioned above, although embodiment of this invention was described based on drawing, it should be thought that a specific structure is not limited to these embodiment. The scope of the present invention is shown not by the above description of the embodiments but by the scope of claims for patent, and further includes all modifications within the meaning and scope equivalent to the scope of claims for patent.

  In the authentication infrastructure system with user authority confirmation function 100 of the above embodiment, as shown in FIG. 15, the user authentication ticket data is divided and the divided user authentication ticket data A is passed to the authority management station 3. Although an example has been described, the present invention is not limited to this, and a method of passing all user authentication ticket data to the authority management station 3 as shown in FIG.

  In the authentication infrastructure system with user authority confirmation function 100 of the above embodiment, as shown in FIG. 15, the user authentication ticket data is divided and the divided user authentication ticket data B is connected to the encrypted data. However, the present invention is not limited to this, and as shown in FIG. 16, a method of linking all user authentication ticket data with encrypted data may be used.

  In addition, as shown in FIG. 17, when the user authentication ticket data is divided, the user authentication tally data A, the user authentication tally data B, and the user authentication tally data C are decomposed into the user authentication tally data C. There may be a method in which the common key can be restored by leaving two of the user authentication tally data A, the user authentication tally data B, and the user authentication tally data C remaining in the user terminal device 1. Accordingly, even when the user 500B cannot connect to the authority management station 3, the user 500B can decrypt the encrypted data in an emergency evacuation manner by receiving the user authentication tally data C from the user 500A.

  In the above-described authentication infrastructure system with a user authority confirmation function, the validity determination unit 300 stores in advance all or part of the keys required when using or using the service providing system 4. In this case, it is preferable that all or a part of the key is not obtained unless the user 500 is authenticated using the validity determination unit 300.

  In the above-described authentication infrastructure system with user authority confirmation function, the validity determination unit 300 uses the key used when using the service providing system 4 as the public key of the authority management station 3 or the authentication station 2. The data is encrypted and attached as user authentication ticket data to the encrypted data or authentication data. When the user uses the service provision system, the user authentication ticket data is sent to the authority management station or the certificate authority to manage the authority. It is preferable to return the key when the station or the certificate authority can authenticate the user.

  In the authentication infrastructure system with a user authority confirmation function, it is preferable that user authentication ticket data can be used and extracted as part of data used in the service providing system 4.

  In the above-described authentication infrastructure system with a user authority confirmation function, the user 500A creates encrypted data using the user terminal device 1A, and the counterpart user 500B uses the user terminal device 1B. However, the present invention is not limited to this, and the user 500B creates encrypted data using the user terminal device 1B, and the partner user 500A uses the user terminal device 1A for the encrypted data. You may decode using.

DESCRIPTION OF SYMBOLS 1 User terminal device 2 Certificate authority 3 Authority management station 4 Service providing system 10 User private key 11 User public key 12 User personal certificate 20 Validity information 21 Certificate authority public key 22 Certificate authority certification 30 Tally DB
40 Secret information 41 Common key (randomly generated common key)
42 Encryption data (encrypted with a common key)
43 User authentication ticket data (data encrypted with the other user's public key)
44 User authentication tally data A (divide user authentication ticket data 1/2)
45 User authentication tally data B (split user authentication ticket data 2/2)
46 Tally data 47 Message ID
48 Encryption data (with confirmation data)
49 Inquiry data (with electronic signature)
50 Electronic Signature 100 of Message ID 100 Authentication Infrastructure System with User Authority Confirmation Function 101 Storage Unit 102 Encryption Generation Unit 103 Decryption Execution Unit 104 Service Providing System Client Unit 300 Validity Determination Unit 301 Authority Management Station Recording Unit 302 Tally Accepting Unit 303 Use User validity checking unit 401 Service providing system server unit 500 User

Claims (1)

A user having a service providing system for providing a service required for decrypting encrypted data to a user belonging to a predetermined organization authenticated by a certificate authority via a user terminal device used by the user An authentication infrastructure system with an authority confirmation function,
The user terminal includes a decryption execution unit that decrypts the encrypted data,
When the user uses the service providing system via the user terminal, the user has an effectiveness determination unit that determines whether authentication by the user's certificate authority is valid, and the effectiveness determination unit If the user is not authenticated using the service, the service providing system does not provide the service to the user .
Generating user authentication ticket data indicating whether or not the user has the authority to decrypt the encrypted data; and tally data having a part of the user authentication ticket data and having the user ID A cryptographic generation unit to generate,
An authority management station storage unit for storing the tally data;
With
The certificate authority stores revocation information of the user ID,
The decryption execution unit is capable of transmitting inquiry data including an electronic signature having the user ID to the validity determination unit;
The effectiveness determining unit
When the inquiry data is received, it is determined whether or not the user ID related to the electronic signature in the inquiry data is registered in the revocation information of the user ID, and the revocation information of the user ID is determined. If it is determined that the user ID related to the electronic signature in the inquiry data is registered, it is determined that the user is not valid, and the inquiry data is included in the revocation information of the user ID. If the ID of the user is not registered, the ID of the user in the electronic signature and the ID of the user in the tally data stored in the authority management station storage unit are An authentication infrastructure system with a user authority confirmation function, characterized by determining whether or not they match, and determining whether or not authentication by the user's certificate authority is valid .