JP2015230520A - Authentication device, authentication method, authentication program and authentication system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide authentication that can alleviate a load of a user, and can reduce a possibility of an information leakage.SOLUTION: An authentication device according to the present application has: a reception unit; and an authentication unit. The reception unit is configured to receive a public key serving as authentication information corresponding to a device of a transmission source, and a signature serving as request information encrypted by non-disclosure information stored in the device and to be decrypted by the authentication information. The authentication unit is configured to authenticate a user corresponding to the device on the basis of the authentication information and the request information.

Description

The present invention relates to an authentication device, an authentication method, an authentication program, and an authentication system.

  Conventionally, login authentication using an ID and a password, authentication using a token such as so-called OAuth authentication, and the like are used. In OAuth authentication, an authentication device such as a service provider returns an issued access token to a consumer who is a third party authorized by the user, and the authentication device performs authentication based on the access token from the consumer. In addition, authentication using information related to devices and users used by users such as mobile phones is used. For example, individual identification information of a mobile phone is registered in advance in the database device as that of each member, and the authentication host computer has the individual identification information included in the authentication request message from the mobile phone to the authentication host computer registered in the database. An authentication method is provided for confirming that the message is an authentication request message from a specific member by confirming that it matches the existing one.

  There is also provided a user authentication system that can perform authentication using a public key authentication method between a user terminal and a number of service providers. In this system, in response to a registration request from the user terminal, the user management system generates a first user identifier, a first public key and first private key pair, and a public key certificate and transmits them to the user terminal. To do. Then, the user terminal generates a second user identifier and a pair of the second public key and the second private key, issues a proxy certificate of the second public key signed with the public key certificate, and sends it to the service providing server. Send a service request that includes a proxy certificate. Thereafter, the service providing server requests the user management system to verify the proxy certificate, and the user management system extracts the public key certificate corresponding to the received proxy certificate, and obtains the public key certificate and the proxy certificate. The result is verified, and the result is transmitted to the service providing server.

JP 2008-146363 A JP 2006-31425 A

  However, in the above-described conventional technology, there is a possibility that the load on the user who is authenticated is large and information is leaked from the authentication device. Specifically, the user manages the ID and password for each service to be authenticated, and when performing login authentication using the ID and password, the user inputs the ID and password. large. In addition, since information used for authentication such as an access token, individual identification information, and first secret key is stored in an authentication device such as an authentication host computer or a user management system in a secret state for other users, Information used for authentication may be leaked from the authentication device.

  The present application has been made in view of the above, and includes an authentication device, an authentication method, an authentication program, and an authentication system that can reduce the load on the user and reduce the possibility of information leakage. The purpose is to provide.

  The authentication apparatus according to the present application receives authentication information corresponding to a transmission source device and request information decrypted by the authentication information, which is information encrypted by private information stored in the device And an authentication unit that authenticates a user corresponding to the device based on the authentication information and the request information.

  According to one aspect of the embodiment, it is possible to reduce the load on the user and reduce the possibility of information leakage.

FIG. 1 is a diagram illustrating an outline of functions of the authentication system according to the embodiment. FIG. 2 is a diagram illustrating a configuration example of the authentication device according to the embodiment. FIG. 3 is a diagram illustrating a configuration example of the user management apparatus according to the embodiment. FIG. 4 is a diagram illustrating an example of related authentication information according to the embodiment. FIG. 5 is a flowchart of user information registration according to the embodiment. FIG. 6 is a diagram illustrating an example of request information according to the embodiment. FIG. 7 is a sequence diagram illustrating authentication processing by the authentication system according to the embodiment. FIG. 8 is a flowchart of the recovery process according to the embodiment. FIG. 9 is a diagram illustrating a functional outline of an authentication system according to a modification. FIG. 10 is a flowchart of resource access according to the modification. FIG. 11 is a diagram illustrating an example of related authentication information according to a modification. FIG. 12 is a diagram illustrating a configuration example of an authentication system according to a modification. FIG. 13 is a hardware configuration diagram illustrating an example of a computer that realizes the function of the authentication device.

  Hereinafter, an embodiment for realizing an authentication apparatus, an authentication method, an authentication program, and an authentication system according to the present application (hereinafter referred to as “embodiment”) will be described in detail with reference to the drawings. Note that the authentication apparatus, the authentication method, the authentication program, and the authentication system according to the present application are not limited to the embodiment. Moreover, in the following each embodiment, the same site | part is attached | subjected the same code | symbol and the overlapping description is abbreviate | omitted.

[1. Authentication system)
First, an example of an authentication system according to the embodiment will be described with reference to FIG. FIG. 1 is a diagram illustrating an outline of functions of the authentication system according to the embodiment. The authentication apparatus 100 shown in FIG. 1 provides a user authentication service based on authentication information and request information. In the following, an example in which the authentication information is a public key used in the public key cryptosystem and a signature encrypted using a secret key used in the public key cryptosystem as request information is shown. That is, in the following example, the authentication information corresponding to the transmission source device corresponds to the public key, and the private information stored in the device corresponds to the secret key.

[1-1. Configuration of authentication system]
First, the configuration of the authentication system according to the embodiment will be described. An authentication system 1 shown in FIG. 1 is an authentication system that performs authentication without using an ID and a password. As shown in FIG. 1, the authentication system 1 includes a user terminal 10, a user management device 20, and an authentication device 100. The user terminal 10, the user management device 20, and the authentication device 100 are communicably connected via a predetermined communication network (not shown) in a wired or wireless manner. The authentication system 1 shown in FIG. 1 may include a plurality of user terminals 10, a plurality of user management devices 20, and a plurality of authentication devices 100.

  The user terminal 10 is an information processing device used by a user. For example, the user terminal 10 transmits a public key that is authentication information and a signature that is request information to the authentication device 100 or information that requests registration of the public key to the user management device 20 according to an operation by the user. To do. Hereinafter, the user terminal 10 may be referred to as a user. That is, in the following, the user can be read as the user terminal 10.

  The user management device 20 is, for example, a web server. When the user management apparatus 20 receives the request information requesting the authentication of the public key from the authentication apparatus 100, the user management apparatus 20 responds to the authentication apparatus 100 with information related to the result of the public key authentication. In addition, the user management apparatus 20 executes a process for registering a public key in response to an input from the user terminal 10.

  The authentication device 100 is a web server or the like, for example. The authentication device 100 provides a user authentication service.

  The above-described user terminal 10 is realized by, for example, a smartphone, a tablet terminal, a mobile phone, a PDA (Personal Digital Assistant), a notebook PC (Personal Computer), a desktop PC, or the like.

[1-2. (Authentication process)
Next, an example of the authentication process according to the embodiment will be described with reference to FIG. In the example illustrated in FIG. 1, the authentication device 100 stores a public key including the public key ok12 and the public key ok13, which are authentication information, as authentication information. Further, the authentication device 100 stores resources, which are information about users corresponding to each public key, in association with the public key. In the example shown in FIG. 1, the resource r121, the resource r122, and the like are stored in association with the public key ok12, and the resource r131 and the like are stored in the public key ok13.

  Here, the user management apparatus 20 associates user information with a plurality of pieces of information and comprehensively manages a variety of information. In the present embodiment, user information may be expressed as NID (Neural Identifier). That is, in the following, user information can be read as NID. The user management device 20 stores NIDid1, NIDid2, and the like. NID is information that is associated with a plurality of pieces of information and used for comprehensively managing a variety of information. The user management device 20 stores NIDid1, NIDid2, and the like. In the present embodiment, the NID that is user information is associated with a plurality of public keys. Further, the user management apparatus 20 stores a public key that is authentication information corresponding to each NID in association with the NID. In the example shown in FIG. 1, public key ok11, public key ok12, and the like are stored in association with NIDid1, and public key ok21 and the like are stored in association with NIDid2.

  As illustrated in FIG. 1, the user terminal 10 generates a signature sg12 by encrypting information to be transmitted to the authentication device 100 using a secret key sk12 that is private information (step s11). Here, the information included in the signature may include processing contents requested of the authentication apparatus 100 and the user management apparatus 20 that are transmission destinations, an expiration date of the signature itself, and the like. Details of the information included in the signature will be described later. The secret key sk12 and the public key ok12 are generated by the user terminal 10. The user terminal 10 stores the secret key sk12 in a secret state.

  Here, the information encrypted with the secret key sk12 can be decrypted using the public key ok12. Therefore, it is possible to determine that the signature sg12 that can be decrypted using the public key ok12 is encrypted by the user terminal 10 that is a user device having the secret key sk12. In other words, when the signature sg12 can be decrypted using the public key ok12, the authentication device 100 can identify the user terminal 10 that is the transmission source.

  Next, the user terminal 10 transmits the signature sg12 and the public key ok12 to the authentication device 100 (step s12). That is, the user terminal 10 transmits the signature sg12 encrypted with the secret key sk12, which is a pair of the public key ok12, and the public key ok12 as a set. At this time, the user terminal 10 may transmit together with the signature sg12 and the public key ok12, or may transmit at different timings. Here, transmitting together with the signature sg12 and the public key ok12 includes transmitting the signature sg12 and the public key ok12 at the same time, transmitting the signature sg12 and the public key ok12 together, and the like.

  When receiving the signature sg12 and the public key ok12 from the user terminal 10, the authentication device 100 decrypts the signature sg12 using the received public key ok12 (step s13). As described above, when the signature sg12 is correctly decrypted with the public key ok12, the authentication apparatus 100 can determine that the user terminal 10 that is the transmission source of the signature sg12 has the secret key sk12 corresponding to the public key ok12. When the signature sg12 cannot be correctly decrypted with the public key ok12, the authentication apparatus 100 determines that the user terminal 10 that is the transmission source of the signature sg12 is not the transmission source corresponding to the public key ok12, and stops the authentication process. At this time, the authentication device 100 may notify the user terminal 10 that the authentication process has failed by an appropriate method.

  Next, when the signature sg12 is correctly decrypted with the public key ok12, the authentication device 100 checks whether or not the public key corresponding to the public key ok12 is stored in the authentication device 100 (step s14). As described above, the authentication device 100 stores a public key as authentication information. If the authentication device 100 confirms that the public key ok12 is stored in the authentication device 100, the authentication device 100 completes the authentication process. At this time, the authentication device 100 may notify the user terminal 10 that the authentication process has been successful by an appropriate method.

  Here, a case where the authentication device 100 determines that the public key corresponding to the public key ok12 is not stored in the authentication device 100 will be described. In this case, the authentication device 100 transmits request information for requesting authentication of the public key ok12 to the user management device 20 (step s15). Then, the user management apparatus 20 responds with information related to the result of authentication of the public key ok12. Upon receiving a response from the user management apparatus 20 that the public key ok12 is stored in the user management apparatus 20 and that the public key ok12 has been successfully authenticated, the authentication apparatus 100 stores the public key ok12 as authentication information. On the other hand, when receiving a response from the user management device 20 that the public key ok12 has failed to be authenticated because the public key ok12 is not stored in the user management device 20, the authentication process is stopped.

  For example, in the example illustrated in FIG. 1, when the authentication device 100 receives the public key ok11 from the user terminal 11 (see FIG. 4), the authentication device 100 does not store the public key ok11 and thus is disclosed to the user management device 20. Request information for requesting authentication of the key ok11 is transmitted. Since the public key ok11 is stored in the user management apparatus 20, the authentication apparatus 100 that has received a response from the user management apparatus 20 that the authentication of the public key ok11 has succeeded newly uses the public key ok11 as authentication information. Remember as.

  Here, the authentication device 100 confirms that the public key ok12 is stored in the authentication device 100 and the authentication is completed (step s14). At this time, the authentication device 100 specifies a resource based on the decrypted signature sg12. Furthermore, when the acquisition of the resource is requested by the decrypted signature sg12, the authentication device 100 transmits the resource r121 stored corresponding to the public key ok12 to the user terminal 10 (step s16). At this time, the authentication apparatus 100 may transmit the resource r121 encrypted using the public key ok12 to the user terminal 10. Thereby, since the resource r121 encrypted with the public key ok12 can be decrypted only by the user terminal 10 having the secret key sk12, the authentication device 100 can improve communication security.

  Thus, since the authentication apparatus 100 according to the embodiment performs the authentication process using the signature and the public key received from the user terminal, it is possible to reduce the possibility of information leaking from the authentication apparatus 100. Specifically, the authentication device 100 performs authentication using a signature encrypted using a secret key held by a user terminal that is a transmission source and a public key that has been made public. In addition, the signature is information that is generated only when the user terminal accesses the authentication apparatus 100 and is effective only in a very short time, such as being used for only one access. Therefore, since the public key and signature need not be kept secret from other users or the like, even if the public key and signature, which are authentication information, are leaked from the authentication device 100, they are misused and resources are stolen or impersonated. The possibility of being reduced can be reduced. Even if the authentication apparatus 100 does not store the public key that is the received authentication information, the authentication apparatus 100 requests the user management apparatus 20 to authenticate the public key, and the result of the public key authentication from the user management apparatus 20 By receiving this, authentication can be performed. That is, the authentication apparatus 100 can authenticate the user even when the public key that is the received authentication information is not stored. Further, by performing authentication processing using the signature and public key received from the user terminal by the authentication apparatus 100 and performing resource identification, authentication and processing can be performed collectively. Thereby, the authentication device 100 can improve usability. In addition, when the signature includes information requesting acquisition of the resource stored in the authentication device 100, processing for transmitting the requested information to the user terminal together with the authentication can be performed. The number of times of communication with the user terminal can be reduced, the communication load can be reduced, and the processing speed can be increased. In addition, the authentication apparatus 100 can provide authentication that does not require login using an ID and a password, and thus can reduce the burden on the user. Further, even when there are a plurality of services that require authentication, the user does not need to manage his / her ID and password for each service, and the user does not need to manage the ID and password. Therefore, in order to avoid the complexity of managing IDs and passwords used for login, it is possible to prevent a user from using the same IDs and passwords for a plurality of services and lowering the security.

[2. Configuration of authentication device]
Next, the configuration of the authentication device 100 according to the embodiment will be described with reference to FIG. FIG. 2 is a diagram illustrating a configuration example of the authentication device 100 according to the embodiment. As illustrated in FIG. 2, the authentication device 100 includes a communication unit 110, a storage unit 120, and a control unit 130. Note that the authentication device 100 includes an input unit (for example, a keyboard and a mouse) that receives various operations from an administrator of the authentication device 100 and a display unit (for example, a liquid crystal display) for displaying various types of information. May be.

(Communication unit 110)
The communication unit 110 is realized by a NIC (Network Interface Card), for example. The communication unit 110 is connected to a predetermined communication network by wire or wireless. And the communication part 110 transmits / receives information between the user terminal 10 and the user management apparatus 20 via a predetermined | prescribed communication network.

(Storage unit 120)
The storage unit 120 is realized by, for example, a semiconductor memory device such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk. In the storage unit 120, public keys are stored as authentication information, and resources that are information about users corresponding to the respective public keys are stored in association with the public keys. For example, in the example illustrated in FIG. 1, the storage unit 120 stores the resources r121, r122, and the like associated with the public key ok12, and stores the resources r131, etc., associated with the public key ok13.

  The control unit 130 is configured such that, for example, various programs (corresponding to an example of an authentication program) stored in a storage device inside the authentication apparatus 100 are stored in a work area by a CPU (Central Processing Unit), an MPU (Micro Processing Unit), or the like. This is realized by being executed as The control unit 130 is realized by an integrated circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

  As illustrated in FIG. 2, the control unit 130 includes a reception unit 131, an authentication unit 132, a specification unit 133, a request unit 134, and a transmission unit 135, and functions and functions of information processing described below. Realize or execute. The internal configuration of the control unit 130 is not limited to the configuration illustrated in FIG. 2, and may be another configuration as long as the information processing described later is performed. In addition, the connection relationship between the processing units included in the control unit 130 is not limited to the connection relationship illustrated in FIG. 2, and may be another connection relationship.

(Reception unit 131)
The accepting unit 131 accepts a public key as authentication information and a signature as request information from the user terminal 10 that is a user who desires authentication. The accepting unit 131 can accept the public key and the signature at the same time, and can accept the public key and the signature at different timings.

(Authentication unit 132)
The authentication unit 132 authenticates the user corresponding to the device based on the public key and signature received by the reception unit 131. First, the authentication unit 132 decrypts the signature using the public key received by the reception unit 131. At this time, if the authentication unit 132 can decrypt the signature using the public key received by the reception unit 131, the authentication unit 132 proceeds to the next process. On the other hand, if the signature cannot be decrypted by the public key accepted by the accepting unit 131, the authenticating unit 132 stops the authentication process.

  Here, the above process will be described based on the example shown in FIG. 1. The authentication unit 132 authenticates the user corresponding to the device based on the public key ok12 and the signature sg12 received by the reception unit 131. First, the authentication unit 132 decrypts the signature sg12 using the public key ok12. At this time, if the authentication unit 132 can decrypt the signature sg12 with the public key ok12 received by the reception unit 131, the authentication unit 132 proceeds to the next process. On the other hand, if the authentication unit 132 cannot decrypt the signature sg12 with the public key ok12 received by the reception unit 131, the authentication unit 132 determines that the user terminal 10 that is the transmission source of the signature sg12 is not the transmission source corresponding to the public key ok12. , Cancel the authentication process.

  Next, the authentication unit 132 confirms whether the public key corresponding to the public key received by the reception unit 131 is stored in the storage unit 120. When the authentication unit 132 confirms that the public key accepted by the acceptance unit 131 is stored in the storage unit 120, the authentication unit 132 completes the authentication process.

  The above process will be described based on the example shown in FIG. 1. The authentication unit 132 confirms whether the public key corresponding to the public key ok12 is stored in the storage unit 120. When the authentication unit 132 confirms that the public key ok12 is stored in the storage unit 120, the authentication unit 132 completes the authentication process.

(Specification part 133)
When the authentication unit 132 confirms that the public key accepted by the accepting unit 131 is stored in the storage unit 120 and the authentication is completed, the identifying unit 133 decrypts the public key accepted by the accepting unit 131. Check the signature information. Then, the specifying unit 133 specifies resources based on the decoded signature. At this time, when the acquisition of the resource is requested by the decrypted signature, the specifying unit 133 determines the resource requested by the decrypted signature from the resources stored corresponding to the accepted public key. Identify. Then, the specifying unit 133 transmits the specified resource to the user terminal that has requested the authentication process by an appropriate means such as via the transmission unit 135 described later.

  Here, the above process will be described based on the example shown in FIG. 1. When the authentication unit 132 confirms that the public key ok12 is stored in the storage unit 120 and the authentication is completed, The information of the signature sg12 decrypted with the key ok12 is confirmed. Then, the specifying unit 133 specifies the resource r121 based on the decrypted signature sg12. At this time, if the resource acquisition is requested by the decrypted signature sg12, the specifying unit 133 determines that the resource r121 requested by the decrypted signature sg12 from the resources stored corresponding to the public key ok12. Is transmitted to the user terminal 10 by an appropriate means.

(Request unit 134)
If the authentication unit 132 determines that the public key accepted by the accepting unit 131 is not stored in the storage unit 120, the request unit 134 requests the user management device 20 to authenticate the public key accepted by the accepting unit 131. Request information to be transmitted to the user management apparatus 20. Here, the request information may include a public key. The request unit 134 stores the public key requested for authentication from the user management apparatus 20 in the user management apparatus 20 and receives a response indicating that the authentication has been successful. Is stored in the storage unit 120 as authentication information. On the other hand, upon receiving a response from the user management device 20 that the public key that requested authentication is not stored in the user management device 20 because the public key that requested authentication has failed, authentication processing is performed. Discontinue.

  Here, the above process will be described based on the case where the authentication apparatus 100 receives the public key ok11 and the signature sg11 from the user terminal 11 (see FIG. 4) in FIG. When the authentication unit 132 determines that the public key ok11 is not stored in the storage unit 120, the request unit 134 transmits request information for requesting authentication of the public key ok11 to the user management device 20. When the request unit 134 receives a response indicating that the authentication of the public key ok11 is successful, the user management device 20 stores the public key ok11 that has been successfully authenticated in the storage unit 120 as authentication information. On the other hand, when receiving a response from the user management device 20 that the authentication of the public key ok11 has failed, the authentication process is stopped.

(Transmitter 135)
The transmission unit 135 transmits the resource specified by the specification unit 133 to the user terminal that has requested the authentication process, or notifies the user terminal that the authentication process has failed by the authentication unit 132 or the request unit 134.

[3-1. Configuration of user management device]
Next, the configuration of the user management apparatus 20 according to the embodiment will be described with reference to FIG. FIG. 3 is a diagram illustrating a configuration example of the user management apparatus 20 according to the embodiment. As illustrated in FIG. 3, the user management apparatus 20 includes a communication unit 210, a storage unit 220, and a control unit 230. The user management device 20 includes an input unit (for example, a keyboard and a mouse) that receives various operations from an administrator of the user management device 20 and a display unit (for example, a liquid crystal display) for displaying various types of information. You may have.

(Communication unit 210)
The communication unit 210 is realized by, for example, a NIC (Network Interface Card). The communication unit 210 is connected to a predetermined communication network by wire or wireless. The communication unit 210 transmits and receives information to and from the user terminal 10 and the authentication device 100 via a predetermined communication network.

(Storage unit 220)
The storage unit 220 is realized by, for example, a semiconductor memory device such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk. In the storage unit 220, an NID is stored as user information regarding the user, and a public key is stored in association with the corresponding NID as related authentication information related to the user. For example, in the example illustrated in FIG. 1, the storage unit 220 stores the public key ok11, the public key ok12, and the like associated with NIDid1, and the public key ok21 and the like associated with NIDid2.

  The control unit 230 is configured such that, for example, various programs (corresponding to an example of an authentication program) stored in a storage device inside the user management device 20 by a CPU (Central Processing Unit), an MPU (Micro Processing Unit), or the like store the RAM in the work area. This is realized by being executed as Further, the control unit 230 is realized by an integrated circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

  As shown in FIG. 3, the control unit 230 includes a management unit 231, an authentication underwriting unit 232, a response unit 233, a sending unit 234, and a determination unit 235. Realize or execute the action. Note that the internal configuration of the control unit 230 is not limited to the configuration illustrated in FIG. 3, and may be another configuration as long as the information processing described below is performed. Further, the connection relationship between the processing units included in the control unit 230 is not limited to the connection relationship illustrated in FIG. 3, and may be another connection relationship.

(Management unit 231)
The management unit 231 stores user information related to the user and related authentication information that is authentication information related to the user in the storage unit 220 in association with each other. That is, in the present embodiment, the management unit 231 stores the NID that is user information and the public key that is related authentication information in association with each other and stores them in the storage unit 220. In addition, the management unit 231 registers related authentication information and new user information, which will be described later. That is, in the present embodiment, the management unit 231 performs public key registration and new NID registration.

(Authentication underwriting unit 232)
When the authentication underwriting unit 232 receives request information for requesting authentication of a public key from the authentication device 100, the authentication undertaking unit 232 confirms whether the public key requested to be authenticated is stored in the storage unit 220. Specifically, if the public key requested for authentication is stored in the storage unit 220, the authentication underwriting unit 232 determines that the authentication is successful, and stores the public key requested for authentication in the storage unit 220. If not, it is determined that the authentication has failed.

  Here, the above processing will be described based on the example shown in FIG. 1. When the authentication underwriting unit 232 receives request information requesting authentication of the public key ok12 from the authentication device 100, the public key ok12 is stored in the storage unit 220. Therefore, it is determined that the public key ok12 has been successfully authenticated. For example, when request information requesting authentication of the public key ok15 that is not stored in the storage unit 220 is received, the authentication underwriting unit 232 determines that the public key ok15 authentication has failed.

(Response unit 233)
The response unit 233 responds to the authentication apparatus 100 with the result of authentication of the public key requested for authentication based on the authentication result by the authentication underwriting unit 232. Specifically, when the authentication underwriting unit 232 determines that the authentication of the public key requested for authentication has succeeded, the response unit 233 responds to the authentication apparatus 100 with information indicating that the authentication has been successful, and the authentication underwriting unit When 232 determines that the authentication of the public key requested to be authenticated has failed, information indicating that the authentication has failed is returned to the authentication apparatus 100.

  Here, the above processing will be described based on the example shown in FIG. 1. The response unit 233 receives request information requesting authentication of the public key ok12 from the authentication device 100, and the authentication underwriting unit 232 succeeds in authentication. If it is determined that the authentication is successful, the authentication apparatus 100 responds with information that the authentication of the public key ok12 is successful. For example, when request information requesting authentication of the public key ok15 not stored in the storage unit 220 is received and the authentication underwriting unit 232 determines that the authentication has failed, the information that the authentication of the public key ok15 has failed is authenticated. Respond to device 100. Note that the information that authentication has succeeded may include a public key that is related authentication information.

(Sending part 234)
The sending unit 234 sends the association information used for associating the user information related to the user with the new authentication information to the destination specified by the destination information related to the user when it becomes necessary to perform a recovery process described later. To do. In other words, in this embodiment, the sending unit 234 associates information used for associating an NID that is user information related to a user and a public key that is new authentication information when a recovery process described later needs to be performed. The information is sent to the destination specified by the destination information regarding the user.

(Determination unit 235)
When it is necessary to perform a recovery process described later, the determination unit 235 determines the user information, the new public key, and the user information based on the association information received from the transmission source corresponding to the destination, the new public key, and the signature. It is determined whether to perform the association. In other words, in the present embodiment, the determination unit 235, based on the association information received from the transmission source corresponding to the destination, the new public key, and the signature when the recovery process described later needs to be performed, It is determined whether to associate the NID that is information with a new public key.

[3-2. (User management device and user terminal)
Here, the relationship between the NID, which is user information stored in the user management apparatus 20, and the public key, which is related authentication information, and the public key generated by the user terminal will be described based on the example shown in FIG. In the example illustrated in FIG. 4, in the user management apparatus 20, public key ok11 and public key ok12 are stored in association with NIDid1, and public key ok21 and the like are stored in association with NIDid2. The user terminal 10 generates and stores a secret key sk12 and a public key ok12, and the user terminal 11 generates and stores a secret key sk11 and a public key ok11.

  The public key ok12 of the user terminal 10 and the public key ok11 of the user terminal 11 are stored in association with the same NIDid1 in the user management device 20. Therefore, in the example shown in FIG. 4, it can be seen that the user terminal 10 and the user terminal 11 are devices owned by the same user indicated by NIDid1. As described above, even when the user owns a plurality of devices, it can be determined that the device is used by the same user, and the user can be associated with the device.

[3-3. Registration of user information]
Next, with reference to FIG. 5, a description will be given of a processing procedure when a user whose NID, which is user information, is not registered in the user management apparatus 20 is requested to register NID. FIG. 5 is a flowchart showing an NID registration procedure by the user management apparatus 20. Such NID registration is executed, for example, when an application that uses the authentication system 1 is downloaded to the user terminal 10.

  First, the user who registers the NID in the user management apparatus 20 generates a public key and a secret key (step s101). Then, a signature is generated using the generated secret key (s102). FIG. 6A shows an example of a signature format. In the example shown in FIG. 6A, the signature includes information related to an expiration date and information such as a resource path. FIG. 6B shows an example in which specific information is included. The information regarding the expiration date includes information indicating the expiration date, and the public key is registered in the information such as the resource path. Contains information that requires you to do so. The user calls the registration API of the user management apparatus 20 using the generated public key and signature (step s103).

  In the user management apparatus 20 for which the registration API has been called, the management unit 231 decrypts the signature using the public key received from the user. Then, if the signature can be decrypted, the management unit 231 pays out a new NID (step s104). Next, the management unit 231 registers the new NID and the received public key in association with each other in the storage unit 220 (step s105).

[4. (Authentication procedure)
Next, a procedure of authentication processing by the authentication system 1 according to the embodiment will be described with reference to FIG. FIG. 7 is a sequence diagram illustrating an authentication processing procedure by the authentication system 1 according to the embodiment.

  As shown in FIG. 7, the user generates a secret key and a public key using the user terminal 10, and generates a signature using the secret key (step S201).

  When the authentication apparatus 100 receives the public key and signature from the user terminal 10 (step s202), the authentication apparatus 100 decrypts the signature with the public key and checks whether the signature can be correctly decrypted (step s203).

  Subsequently, the authentication device 100 identifies the corresponding public key and identifies the resource based on the signature (step s204). At this time, if there is no corresponding public key, the authentication device 100 requests the user management device 20 to authenticate the public key (step s205). The user management apparatus 20 that has received the request from the authentication apparatus 100 responds to the authentication apparatus 100 with an authentication result that is information relating to the corresponding public key (step s206).

  Subsequently, when there is a resource requested by the signature, the authentication device 100 transmits the identified resource to the user terminal 10 (step s207).

[5. (Recovery process)
Here, a recovery process that is performed when a public key is newly associated with an NID that is user information registered in the user management apparatus 20 will be described with reference to FIG. Examples of performing the recovery process include a case where the model is changed, a case where the private key and the public key are erased by reset, and the like. Further, as a premise for performing the recovery process, the NID registered in the user management apparatus 20 needs to store the destination to which the association information is sent in association with it. In the example shown in FIG. 8, a mail address is stored in association with the NID as a destination. The destination may be anything that can transmit information such as a telephone number.

  First, a user who wants to perform recovery processing inputs a mail address from the user terminal (step s301), and calls a recovery API using the mail address (step s302).

  The user management apparatus 20 that has called the recovery API specifies the NID associated with the received mail address by reverse lookup (step s303). Then, the user management device 20 creates a common key associated with the mail address and a code used for authentication (step s304). The user management device 20 encrypts the association information with the created common key and generates a recovery key (step s305). Note that the association information may include information such as an expiration date, a code, a mail address, and an NID. Then, the user management apparatus 20 sends the code by e-mail with the input e-mail address as the destination by the sending unit 234 and passes the recovery key to the user by e-mail (step s306).

  The user who has received the mail including the code, the recovery key, etc. inputs the received code, for example, into an authentication screen provided by the user management apparatus 20 and transmits it to the user management apparatus 20 (step s307). Then, the user whose code has been authenticated generates a new public key and secret key, and generates a signature using the generated secret key (step s308). Thereafter, the user calls the recovery API using the code, mail address, recovery key, new public key, signature, and the like (step s309).

  The user management apparatus 20 that has called the recovery API decrypts the signature using the new public key received by the determination unit 235, and checks whether it can be decrypted correctly (step s310). Then, the user management apparatus 20 decrypts the recovery key received by the determination unit 235 with the common key associated with the mail address, and confirms the match between the code and the mail address (step s311). If the above steps s310 and s311 are successful, the user management apparatus 20 associates the new public key with the corresponding NID as related authentication information (step s312). As a result, the NID and the new public key can be associated with each other. Therefore, a new terminal can be easily associated with the user by performing the recovery process.

[6. (Modification)
The authentication system 1 according to the above-described embodiment may be implemented in various different forms other than the above-described embodiment. Therefore, in the following, another embodiment of the authentication system 1 will be described.

[6-1. (Storing authentication device user information)
In the above embodiment, an example has been described in which the authentication apparatus 100 stores resources in association with the public key that is authentication information. However, the authentication apparatus may store resources in association with the NID that is user information. Hereinafter, an example of the authentication process of the authentication system 2 in which the authentication apparatus stores resources in association with the NID will be described with reference to FIG. In the example illustrated in FIG. 9, the authentication apparatus 101 stores resources that are information about users corresponding to NIDs that are user information including NIDid1, NIDid3, and the like in association with NIDs. In the example shown in FIG. 9, NIDid1 stores resources r121 and r122 in association with each other, and NIDid3 stores resources r131 in association with each other.

  Here, the user management apparatus 21 stores NIDid1, NIDid2, and the like. Further, the user management device 21 stores a public key corresponding to each NID in association with the NID. In the example shown in FIG. 9, public key ok11, public key ok12, and the like are stored in association with NIDid1, and public key ok21 and the like are stored in association with NIDid2.

  As illustrated in FIG. 9, the user terminal 10 generates a signature sg12 by encrypting information to be transmitted to the authentication apparatus 101 using the secret key sk12 (step s21). The secret key sk12 and the public key ok12 are generated by the user terminal 10. The user terminal 10 stores the secret key sk12 in a secret state.

  Here, the information encrypted with the secret key sk12 can be decrypted using the public key ok12. Therefore, it is possible to determine that the signature sg12 that can be decrypted using the public key ok12 is encrypted by the user terminal 10 that is a user device having the secret key sk12. In other words, when the signature sg12 can be decrypted using the public key ok12, the authentication device 101 can specify the user terminal 10 that is the transmission source.

  Next, the user terminal 10 transmits the signature sg12 and the public key ok12 to the authentication device 101 (step s22). That is, the user terminal 10 transmits the signature sg12 encrypted with the secret key sk12, which is a pair of the public key ok12, and the public key ok12 as a set. At this time, the user terminal 10 may transmit together with the signature sg12 and the public key ok12, or may transmit at different timings. Here, transmitting together with the signature sg12 and the public key ok12 includes transmitting the signature sg12 and the public key ok12 at the same time, transmitting the signature sg12 and the public key ok12 together, and the like.

  When receiving the signature sg12 and the public key ok12 from the user terminal 10, the authentication apparatus 101 decrypts the signature sg12 using the received public key ok12 (step s23). As described above, when the signature sg12 is correctly decrypted with the public key ok12, the authentication apparatus 101 can determine that the user terminal 10 that is the transmission source of the signature sg12 has the secret key sk12 corresponding to the public key ok12. When the signature sg12 cannot be correctly decrypted with the public key ok12, the authentication apparatus 101 determines that the user terminal 10 that is the transmission source of the signature sg12 is not the transmission source corresponding to the public key ok12, and stops the authentication process. At this time, the authentication apparatus 101 may notify the user terminal 10 that the authentication process has failed by an appropriate method.

  Next, when the signature sg12 is correctly decrypted with the public key ok12, the authentication apparatus 101 checks whether the public key corresponding to the public key ok12 is stored in the authentication apparatus 101. When the public key corresponding to the public key ok12 is stored in the authentication device 101, the authentication device 101 calls and stores the API of the user management device 21 that returns the NID corresponding to the input public key. If not, the authentication apparatus 101 transmits request information for requesting authentication of the public key ok12 to the user management apparatus 21 (step s24). Thereby, the authentication device 101 can acquire the NID corresponding to the received public key from the user management device 21 (step s25). If the NID corresponding to the public key transmitted to the user management apparatus 21 cannot be acquired or the authentication of the public key transmitted by the user management apparatus 21 fails, the authentication apparatus 101 stops the certification process. At this time, the authentication apparatus 101 may notify the user terminal 10 that the authentication process has failed by an appropriate method.

  In the example shown in FIG. 9, when the public key corresponding to the public key ok12 is stored in the authentication device 101, the authentication device 101 calls the API of the user management device 21 that returns the NID using the public key ok12. NIDid1 corresponding to the public key ok12 is acquired. If the public key corresponding to the public key ok12 is not stored in the authentication apparatus 101, request information requesting the authentication of the public key ok12 is transmitted to the user management apparatus 21, and the public key ok12 is transmitted from the user management apparatus 21. Receive authentication results. At this time, the authentication apparatus 101 stores the public key ok12 in association with the corresponding NIDid1.

  Next, the authentication apparatus 101 identifies a resource based on the decrypted signature sg12. Furthermore, when the acquisition of the resource is requested by the decrypted signature sg12, the authentication apparatus 101 transmits the resource r121 stored in association with NIDid1 corresponding to the public key ok12 to the user terminal 10 (step s26). At this time, the authentication apparatus 101 may transmit the resource r121 encrypted using the public key ok12 to the user terminal 10. As a result, the resource r121 encrypted with the public key ok12 can be decrypted only by the user terminal 10 having the secret key sk12, so that the authentication apparatus 101 can improve communication security.

  Here, the above processing procedure will be described with reference to the flowchart shown in FIG. First, a user who requests authentication and resources generates a signature using a secret key stored in the user terminal (step s401). Then, the resource API of the authentication apparatus 101 is called using the public key and signature corresponding to the secret key (step s402).

  The authentication apparatus 101 called with the resource API decrypts the signature using the received public key, checks the signature to verify whether it can be decrypted correctly, and verifies it (step s403). Then, the authentication apparatus 101 specifies the NID by reverse lookup from the public key (step s404). When the authentication apparatus 101 specifies the corresponding NID from the public key, the authentication apparatus 101 requests the user management apparatus 21 to acquire the NID associated with the public key, and specifies the NID based on information from the user management apparatus 21.

  Subsequently, the authentication apparatus 101 searches for resources from the specified NID (step s405). Then, the specified resource is returned to the user (step s406). Thereby, even if the user accesses the authentication apparatus 101 from a different user terminal, the user can always acquire resources associated with the same NID.

[6-2. User management device and authentication device]
Here, the relationship between the NID, which is user information stored in the user management device 21 in the authentication system 2 shown in FIG. 9, and the NID stored in the plurality of authentication devices 101, 102 is based on the example shown in FIG. I will explain. In the example illustrated in FIG. 11, in the user management apparatus 21, public key ok11 and public key ok12 are stored in association with NIDid1, and public key ok21 and the like are stored in association with NIDid2. Further, as shown in FIG. 9, the authentication devices 101 and 102 each store a resource in association with the NID.

  The public key ok12 of the user terminal 10 and the public key ok11 of the user terminal 11 are stored in association with the same NIDid1 in the user management device 21. Therefore, in the example illustrated in FIG. 11, the authentication devices 101 and 102 may return resources associated with the same NID regardless of whether the user terminal 10 or the user terminal 11 requests authentication and resources. it can. In other words, it can be seen that the authentication devices 101 and 102 are the devices owned by the same user indicated by NIDid1 in the user terminal 10 and the user terminal 11. Thus, even when a user owns a plurality of devices, it can be determined that the device is used by the same user, and resources related to the user can be returned.

[6-3. (Signature)
The information included in the signature may include information related to the user's authority. For example, when the signature includes information indicating whether access to the resource specified by the signature that is the request information is permitted as the information related to the user's authority, the specifying unit 133 responds to the information related to the user's authority. Judge whether access to the resource is possible. Then, the authentication unit 132 specifies a resource only when access is permitted. Thereby, a user's authority can be set finely.

[6-4. (Revocation of authentication information)
The management unit 231 of the user management apparatus 20 may revoke the public key that is authentication information stored in the storage unit 220 when a predetermined condition is satisfied. For example, when an NID that is user information is deleted, a public key that is related authentication information associated with the NID is revoked. Describing based on the example shown in FIG. 1, when NIDid1 is deleted from the user management apparatus 20, all public keys associated with NIDid1, such as public key ok11 and public key ok12, are revoked. Also, for example, when the secret key used for encrypting the signature that is the request information is deleted or leaked from the user terminal that is the transmission source, the public key that is the related authentication information corresponding to the transmission source is revoked. . If it demonstrates based on the example shown in FIG. 1, when the private key sk12 is deleted or leaked from the user terminal 10 which is a transmission source, the user management apparatus 20 is related authentication information corresponding to the user terminal 10. The public key ok12 is revoked. That is, it is not necessary to revoke a public key that is authentication information on a plurality of authentication devices, and it is only necessary to revoke a public key that is related authentication information of the user management device. Thereby, unauthorized access and the like can be prevented. Note that the user management device 20 may notify the authentication device 100 storing the public key revoked by an appropriate means that the public key has been revoked. Further, the authentication device 100 that has received the notification regarding the public key revoked by the user management device 20 may revoke the corresponding public key.

[6-5. Authorization delegation)
In the above embodiment, authentication is performed using the public key and signature received from the user terminal that generated the public key and private key pair, but the user terminal delegates the authority to receive authentication to other user terminals. May be. As an example, there is a case where authority is transferred from a user terminal possessed by a user who enters the store to a store terminal which is another user terminal. FIG. 12 shows an example of the authentication system 3 when the authority for authentication is delegated, and the process will be described below. In FIG. 12, the user terminal 13, which is a store terminal to which authority has been transferred from the user terminal 12 possessed by the user, requests authentication from the user management device 22, and acquires a mail address as a resource from the user management device 22. It is shown as an example. The resource is not limited to an e-mail address, but may be personal information such as an address or name, or image information such as a face photo.

  In the example shown in FIG. 12, the user management apparatus 22 stores NIDid1, NIDid2, etc. as user information. Further, the user management device 22 stores a mail address corresponding to each NID in association with the NID. In the example shown in FIG. 12, the mail address m1 is stored in association with NIDid1, and the mail address m2 is stored in association with NIDid2. Although illustration is omitted, in the example shown in FIG. 12, each NID is associated with a corresponding public key or resource.

  As illustrated in FIG. 12, the user terminal 12 generates a signature sg14 by encrypting information to be transmitted to the authentication apparatus 101 using the secret key sk14 (step s31). The user terminal 12 transmits the signature sg14 and the public key ok14 to the user terminal 13 (step s32).

  The user terminal 13 transmits the signature sg14 and the public key ok14 received from the user terminal 12 to the user management device 22 (step s33).

  The user management apparatus 22 that has received the signature sg14 and the public key ok14 from the user terminal 13 decrypts the signature sg14 using the received public key ok14, and confirms whether or not the signature sg14 can be correctly decrypted (step s34). When the signature sg14 cannot be correctly decrypted with the public key ok14, it is determined that the user terminal 13 is not the transmission source to which the authority is delegated from the user terminal 12, and the authentication process is stopped. At this time, the user management apparatus 22 may notify the user terminal 12 or the user terminal 13 that the authentication process has failed by an appropriate method.

  Next, when the signature sg14 is correctly decrypted with the public key ok14, the user management apparatus 22 checks whether the NID corresponding to the public key ok14 is stored in the user management apparatus 22 (step s35). If the user management device 22 determines that the NIDid1 corresponding to the public key ok14 is stored in the user management device 22, the user management device 22 determines that the public key ok14 has been successfully authenticated, and sets the mail address m1 associated with the NIDid1 to the user. It transmits to the terminal 13 (step s36). As a result, the user terminal 13 to which authority has been delegated from the user terminal 12 can acquire resources related to the user terminal 12 from the user management device 22. When the user management device 22 determines that the NID corresponding to the public key ok14 is not stored in the user management device 22, the user management device 22 transmits a response to the user terminal 13 that the authentication of the public key ok14 has failed, and authentication. Cancel processing.

[6-6. Device configuration〕
Further, the authentication device 100 illustrated in FIG. 2 may not include the storage unit 120. Specifically, the authentication device 100 may be connected to a database server that holds the storage unit 120. Further, the user management apparatus 20 illustrated in FIG. 3 may not include the storage unit 220. Specifically, the user management device 20 may be connected to a database server that holds the storage unit 220.

[6-7. program〕
Further, the authentication device 100 and the user management device 20 according to the above-described embodiments are realized by a computer 1000 having a configuration as shown in FIG. 13, for example. FIG. 13 is a hardware configuration diagram illustrating an example of a computer 1000 that implements the functions of the authentication device 100. The computer 1000 includes a CPU 1100, RAM 1200, ROM 1300, HDD 1400, communication interface (I / F) 1500, input / output interface (I / F) 1600, and media interface (I / F) 1700.

  The CPU 1100 operates based on a program stored in the ROM 1300 or the HDD 1400 and controls each unit. The ROM 1300 stores a boot program executed by the CPU 1100 when the computer 1000 is started up, a program depending on the hardware of the computer 1000, and the like.

  The HDD 1400 stores programs executed by the CPU 1100, data used by the programs, and the like. The communication interface 1500 receives data from other devices via the communication network 30 and sends the data to the CPU 1100, and transmits data generated by the CPU 1100 to other devices via the communication network 30.

  The CPU 1100 controls an output device such as a display and a printer and an input device such as a keyboard and a mouse via the input / output interface 1600. The CPU 1100 acquires data from the input device via the input / output interface 1600. In addition, the CPU 1100 outputs the generated data to the output device via the input / output interface 1600.

  The media interface 1700 reads a program or data stored in the recording medium 1800 and provides it to the CPU 1100 via the RAM 1200. The CPU 1100 loads such a program from the recording medium 1800 onto the RAM 1200 via the media interface 1700, and executes the loaded program. The recording medium 1800 is, for example, an optical recording medium such as a DVD (Digital Versatile Disc) or PD (Phase change rewritable disk), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory. Etc.

  For example, when the computer 1000 functions as the authentication device 100 according to the embodiment, the CPU 1100 of the computer 1000 implements the function of the control unit 130 by executing a program loaded on the RAM 1200. The HDD 1400 stores data in the storage unit 120. The CPU 1100 of the computer 1000 reads these programs from the recording medium 1800 and executes them. However, as another example, these programs may be acquired from other devices via the communication network 30.

[6-8. Others]
In addition, among the processes described in the above embodiment, all or part of the processes described as being automatically performed can be performed manually, or the processes described as being performed manually can be performed. All or a part can be automatically performed by a known method. In addition, the processing procedures, specific names, and information including various data and parameters shown in the document and drawings can be arbitrarily changed unless otherwise specified. For example, the various types of information illustrated in each drawing is not limited to the illustrated information.

  Further, each component of each illustrated apparatus is functionally conceptual, and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. For example, the reception unit 131 and the transmission unit 135 illustrated in FIG. 2 may be integrated.

  Moreover, each embodiment mentioned above can be combined suitably in the range which does not contradict a process content.

[6-9. effect〕
As described above, the authentication device 100 according to the embodiment includes the reception unit 131 and the authentication unit 132. The receiving unit 131 uses authentication information (in the embodiment, a public key; the same applies hereinafter) corresponding to the transmission source device and private information (a secret key in the embodiment; the same applies hereinafter) stored in the device. Request information (in the embodiment, signature, the same applies hereinafter) that is encrypted information and decrypted by the authentication information is received. The authentication unit 132 authenticates a user corresponding to the device based on the authentication information and the request information.

  Thereby, since the authentication apparatus 100 performs the authentication process using the signature and the public key received from the user terminal, the possibility that information is leaked from the authentication apparatus 100 can be reduced. The authentication device 100 performs authentication using a signature encrypted using a secret key held by a user terminal that is a transmission source and a public key that has been made public. Therefore, even if a public key or signature, which is authentication information, leaks from the authentication device 100, it is possible to reduce the possibility of resources being stolen or spoofed. In addition, the authentication apparatus 100 can provide authentication that does not require login using an ID and a password, and thus can reduce the burden on the user.

  In the authentication device 100 according to the embodiment, the reception unit 131 receives both authentication information and request information. The authentication unit 132 authenticates the user based on the authentication information and the request information received together with the authentication information.

  Thereby, the authentication apparatus 100 according to the embodiment can confirm that the authentication information and the request information are transmitted from the same transmission source, and that the transmission source surely holds the secret key paired with the public key. Therefore, it can authenticate correctly by authenticating based on authentication information and request information. Therefore, the authentication device 100 can further reduce the possibility of being impersonated.

  In the authentication device 100 according to the embodiment, the reception unit 131 receives request information including information related to an expiration date. The authentication unit 132 authenticates the user corresponding to the device when it is determined that it is before the expiration date based on the information regarding the expiration date included in the request information.

  Thereby, since the authentication apparatus 100 according to the embodiment accepts authentication only when the expiration date has not elapsed, user authentication with a higher security level can be performed.

  In addition, the authentication device 100 according to the embodiment includes a request unit 134. The request unit 134 sends authentication information to the user management apparatus 20 that manages user information related to the user (NID in the embodiment; the same applies hereinafter) and related authentication information that is authentication information related to the user. Request authentication. The authentication unit 132 authenticates the user corresponding to the device based on the authentication information and the request information when the authentication of the authentication information is successful by the user management apparatus 20.

  Thereby, in the authentication device 100 according to the embodiment, a user whose authentication information is not stored in the authentication device 100 can be authenticated. In other words, this enables the authentication apparatus 100 to add new authentication information.

  The authentication device 101 according to the modification includes a specifying unit. The identifying unit identifies a resource requested by the request information among resources stored in association with user information.

  Thereby, the authentication device 101 according to the modified example can improve usability by performing authentication and performing resource identification by using information used for authentication.

  The authentication device 100 according to the embodiment includes a specifying unit 133. The identifying unit 133 identifies a resource requested by the request information among resources stored in association with authentication information.

  Accordingly, the authentication device 100 according to the embodiment can improve usability by performing authentication and performing resource identification based on information used for authentication.

  In the authentication device 100 according to the embodiment, the reception unit 131 receives request information including information related to the user authority. The authentication unit 132 determines whether access to the resource specified by the request information is permitted based on the information regarding the authority included in the request information.

  Thereby, the authentication device 100 according to the embodiment can finely set the authority of the user, and can prevent access to unnecessary resources.

  In addition, the authentication device 100 according to the embodiment includes a transmission unit 135. The transmission unit 135 transmits information on the resource specified based on the request information to the transmission source.

  Thereby, in the authentication apparatus 100 which concerns on embodiment, a resource can be provided to a user.

  Further, the user management apparatus 20 according to the embodiment includes a management unit 231, an authentication underwriting unit 232, and a response unit 233. The management unit 231 associates and manages user information related to the user and related authentication information that is authentication information related to the user. The authentication underwriting unit 232 authenticates the authentication information based on the received request information. The response unit 233 responds with information related to the authentication result of the authentication information.

  Thereby, the user management apparatus 20 according to the embodiment can respond the authentication result to the authentication apparatus 100.

  In the user management device 20 according to the embodiment, the management unit 231 expires related authentication information associated with user information when the user information is deleted.

  Thereby, the user management apparatus 20 according to the embodiment can prevent unauthorized access and the like.

  Further, in the user management device 20 according to the embodiment, the management unit 231 may relate the related authentication information corresponding to the transmission source when the private information used for encrypting the request information is deleted or leaked from the transmission source. Expires.

  As a result, it is not necessary to revoke a public key that is authentication information on a plurality of authentication devices, and it is only necessary to revoke a public key that is related authentication information of the user management device 20. Therefore, the user management apparatus 20 according to the embodiment can prevent unauthorized access and the like.

  In addition, the user management apparatus 20 according to the embodiment includes a sending unit 234 and a determination unit 235. The sending unit 234 sends association information used for associating user information related to the user with new authentication information to a destination specified by the destination information related to the user. The determination unit 235 determines whether to associate the user information with the new authentication information based on the association information received from the transmission source corresponding to the destination, the new authentication information, and the request information. When the determination unit 235 determines to perform association, the management unit 231 associates new authentication information with user information as new related authentication information.

  Thereby, the user management apparatus 20 according to the embodiment can newly add related authentication information.

  As described above, some of the embodiments of the present application have been described in detail with reference to the drawings. However, these are merely examples, and various modifications based on the knowledge of those skilled in the art, including the aspects described in the disclosure line of the invention. It is possible to implement the present invention in other forms with improvements.

  In addition, the “section (module, unit)” described above can be read as “means” or “circuit”. For example, the reception unit can be read as reception means or a reception circuit.

DESCRIPTION OF SYMBOLS 1 Authentication system 10 User terminal 20 User management apparatus 100 Authentication apparatus 120 Storage part 131 Reception part 132 Authentication part 133 Identification part 134 Request part 135 Transmission part 220 Storage part 231 Management part 232 Authentication acceptance part 233 Response part 234 Sending part 235 Determination part

Claims (14)

A receiving unit that receives authentication information corresponding to a transmission source device, and request information that is information encrypted by private information stored in the device and decrypted by the authentication information;
An authentication unit that authenticates a user corresponding to the device based on the authentication information and the request information;
An authentication apparatus comprising: The reception unit
Accepting both the authentication information and the request information;
The authentication unit
Authenticating the user based on the authentication information and the request information received with the authentication information;
The authentication apparatus according to claim 1. The reception unit
Accepting the request information including information about the expiration date;
The authentication unit
Authenticating a user corresponding to the device when it is determined that it is before the expiration of the expiration date based on the information regarding the expiration date included in the request information;
The authentication apparatus according to claim 1 or 2, characterized in that A request unit that requests authentication of the authentication information to a user management apparatus that manages user information related to the user and related authentication information that is authentication information related to the user in association with each other,
The authentication unit authenticates a user corresponding to the device based on the authentication information and the request information when the authentication of the authentication information is successful by the user management device.
The authentication device according to any one of claims 1 to 3, wherein A specifying unit for specifying a resource requested by the request information among resources stored in association with the user information;
The authentication apparatus according to claim 4, further comprising: A specifying unit for specifying a resource requested by the request information among resources stored in association with the authentication information;
The authentication device according to claim 1, further comprising: The reception unit
Accepting the request information including information about the user's authority;
The specific part is:
Determining whether access to a resource specified by the request information is permitted based on information on the authority included in the request information;
The authentication apparatus according to claim 5 or 6, characterized in that A transmission unit for transmitting information on the resource specified based on the request information to the transmission source;
The authentication apparatus according to claim 5, further comprising: An authentication method performed by a computer,
An accepting step of accepting authentication information corresponding to a transmission source device and request information decrypted by the authentication information, which is information encrypted by non-public information stored in the device;
An authentication step of authenticating a user corresponding to the device based on the authentication information and the request information;
An authentication method characterized by comprising: An acceptance procedure for receiving authentication information corresponding to a transmission source device and request information decrypted by the authentication information, which is information encrypted by non-public information stored in the device;
An authentication procedure for authenticating a user corresponding to the device based on the authentication information and the request information;
An authentication program characterized by comprising: An authentication system including an authentication device and a user management device,
The authentication device
A receiving unit that receives authentication information corresponding to a transmission source device, and request information that is information encrypted by private information stored in the device and decrypted by the authentication information;
A request unit that transmits request information for requesting authentication of the authentication information to the user management device;
An authentication unit that authenticates a user corresponding to the device based on the authentication information and the request information when the authentication of the authentication information is successful by the user management device;
The user management device includes:
A management unit that associates and manages user information related to the user and related authentication information that is authentication information related to the user;
An authentication underwriting unit that authenticates the authentication information based on the received request information;
A response unit that responds with information on the authentication result of the authentication information;
An authentication system characterized by comprising: The management unit
Revoking the related authentication information associated with the user information when the user information is deleted;
The authentication system according to claim 11. The management unit
When the private information used for encrypting the request information is deleted or leaked from the transmission source, the related authentication information corresponding to the transmission source is revoked.
The authentication system according to claim 11 or 12, characterized in that: The user management device includes:
A sending unit that sends association information used for associating user information about a user and new authentication information to a destination specified by the destination information about the user;
A determination unit that determines whether to associate the user information with the new authentication information based on the association information received from the transmission source corresponding to the destination, the new authentication information, and the request information; Prepared,
The management unit
When it is determined that the association is performed by the determination unit, the new authentication information is associated with the user information as new related authentication information,
The authentication system according to any one of claims 11 to 13, characterized in that:

Images