WO2017029708A1

WO2017029708A1 - Personal authentication system

Info

Publication number: WO2017029708A1
Application number: PCT/JP2015/073094
Authority: WO
Inventors: 大河　克好
Original assignee: 株式会社Ｐｉｐｓ
Priority date: 2015-08-18
Filing date: 2015-08-18
Publication date: 2017-02-23
Also published as: JPWO2017029708A1

Abstract

In this personal authentication system, when an authentication server 3 has received a login request for a particular service from a terminal device 1, the authentication server 3 generates a service code associated with the particular service, and transmits the service code to the terminal device 1. Upon receiving this service code, the terminal device 1 outputs the service code in a predetermined format. A user authentication device 4 receives the service code output from the terminal device 1 and transmits the received service code to the authentication server 3. Then if the authentication server 3 succeeds in authenticating the user authentication device 4, which has transmitted the service code to the authentication server 3, then the authentication server 3 permits the user associated with the user authentication device 4 to log in for the particular service.

Description

Personal authentication system

The present invention relates to a personal authentication system.

There is a system in which a seed such as a random number is updated each time the client and the server are successfully authenticated, a one-time ID is generated from the seed at the next authentication, and the client and the server authenticate each other. (For example, refer to Patent Document 1).

JP 2004-282295 A

In the above-described system, it is possible to identify the client and server devices and authenticate the devices (that is, authenticate that the communication partner device is a legitimate device).

However, when logging in to a specific service provided from the client side to the server side, service-specific fixed user authentication data (for example, a pair of user ID and password) for user identification in the specific service May be illegally acquired by a malicious third party by man-in-the-middle attacks, man-in-the-browser attacks, screen capture attacks by malware, keylogger attacks, etc. is there.

The present invention has been made in view of the above problems, and identifies a user without transmitting / receiving fixed user authentication data required for user authentication for service login via a communication path such as the Internet. An object of the present invention is to obtain a personal authentication system that permits a service login to a regular user.

The personal authentication system according to the present invention includes an authentication server that determines whether or not a user can log in to a specific service, a terminal device that is operated by the user and receives data of the specific service, and a user authentication device that is associated with the user by the authentication server With. (A) The terminal device transmits a service login request for the specific service to the authentication server without transmitting fixed user authentication data. (B) When the authentication server receives the service login request, the terminal device responds to the specific service. A service code is generated and transmitted to the terminal device that is the source of the service login request. (C) Upon receiving the service code, the terminal device outputs the received service code in a predetermined form, and (d) user authentication. When the device receives the input of the service code output by the terminal device in a predetermined form, the device transmits the input service code to the authentication server without transmitting the fixed user authentication data, and (e) the authentication server When the service code is received, device authentication of the user authentication device that is the transmission source of the service code is performed, and user authentication is performed. Successful vice device authentication, the user associated with the user authentication device, permits login of the specific service specified by the service code received.

The authentication server according to the present invention includes a communication device, an authentication processing unit, and a service code generation unit. The service code generation unit authenticates the service login request for the specific service without receiving the fixed user authentication data from the terminal device operated by the user and receiving the data of the specific service using the communication device of the authentication server. When received by the server, it generates a service code corresponding to the specific service, and the authentication processing unit transmits the generated service code to the terminal device that is the transmission source of the service login request using the communication device, The authentication processing unit uses (a) a service code output by the terminal device without receiving fixed user authentication data from the user authentication device associated with the user by the authentication server using the communication device. (B) execute device authentication of the user authentication device that is the transmission source of the received service code, Upon successful device authentication over The authentication device, the user associated with the user authentication device, permits login of the specific service specified by the service code received.

The authentication program according to the present invention causes a computer in the authentication server to function as a server-side authentication processing unit and a service code generation unit. The service code generation unit authenticates the service login request for the specific service without receiving the fixed user authentication data from the terminal device operated by the user and receiving the data of the specific service using the communication device of the authentication server. When received by the server, it generates a service code corresponding to the specific service, and the server-side authentication processing unit uses the communication device of the authentication server to send the generated service code to the terminal that is the source of the service login request The server-side authentication processing unit does not receive fixed user authentication data from the user authentication device associated with the user by the authentication server using the communication device of the authentication server (a). (B) the source of the received service code. Run the device authentication of the user authentication device, if successful the device authentication of the user authentication device, the user associated with the user authentication device, permits login of the specific service specified by the service code received.

The authentication program according to the present invention causes a computer in the terminal device to function as a service code output unit and an authentication processing unit. The authentication processing unit (a) transmits a service login request for a specific service to the authentication server without transmitting fixed user authentication data, and (b) is transmitted from the authentication server in response to the service login request. When the service code is received, the service code output unit outputs the received service code in a predetermined form that can be input to the user authentication device. The authentication device is associated with the user by the authentication server, and upon receiving the input of the service code output by the terminal device, transmits the input service code to the authentication server without transmitting user authentication data.

The authentication program according to the present invention causes a computer in the user authentication device to function as an authentication processing unit. The authentication processing unit accepts, in a predetermined form, an input of a service code received from an authentication server and output in a predetermined form by a terminal apparatus operated by a user and receiving data of a specific service, and (b) a terminal apparatus When the input of the service code output by is received, the input service code is transmitted to the authentication server without transmitting the fixed user authentication data, and the device authentication of the user authentication device that is the transmission source of the service code is performed. When the device authentication of the user authentication device is successful, the user associated with the user authentication device is permitted to log in the specific service specified by the received service code.

According to the present invention, personal authentication that identifies a user and permits service login to a regular user without transmitting / receiving user authentication data required for user authentication for service login via a communication path such as the Internet. A system is obtained.

The above and other objects, features and advantages of the present invention will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings.

FIG. 1 is a block diagram showing a configuration of a one-time authentication system according to an embodiment of the present invention. FIG. 2 is a block diagram showing the configuration of the terminal device 1 in FIG. FIG. 3 is a block diagram showing a processing unit realized in the terminal device 1 shown in FIG. FIG. 4 is a block diagram showing the configuration of the authentication server 3 in FIG. FIG. 5 is a block diagram showing a processing unit realized in the authentication server 3 shown in FIG. FIG. 6 is a block diagram showing the configuration of the user authentication device 4 in FIG. FIG. 7 is a block diagram showing a processing unit realized in the user authentication device 4 shown in FIG. FIG. 8 is a sequence diagram for explaining processing at the time of service login in the system shown in FIG. FIG. 9 is a sequence diagram illustrating details of one-time authentication between terminal device 1 and authentication server 3 in the embodiment of the present invention. FIG. 10 is a sequence diagram illustrating details of one-time authentication between the user authentication device 4 and the authentication server 3 in the embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.

FIG. 1 is a block diagram showing a configuration of a one-time authentication system according to an embodiment of the present invention.

In the system shown in FIG. 1, a terminal device 1 as a client is connected to a network 2 such as the Internet, and an authentication server 3 is connected to the network 2. The user possesses a user authentication device 4 that can be connected to the network 2, and can operate the terminal device 1 and the user authentication device 4.

The terminal device 1 is operated by the user and receives data of the specific service from the authentication server 3 or the like. The authentication server 3 is a server device that determines whether a user can log in to a specific service. The user authentication device 4 is a device associated with the user by the authentication server 3.

The terminal device 1 is a device incorporating a computer such as a personal computer or a kiosk terminal. In this embodiment, the terminal device 1 can be used by one or more specific or unspecified users. The network 2 includes a wired and / or wireless LAN (Local Area Network) and / or a WAN (Wide Area Network) such as the Internet.

The user authentication device 4 is a portable device with a built-in computer that can be connected to the network 2. For example, a smartphone, a tablet terminal, or the like can be used as the user authentication device 4.

The user authentication device 4 is carried by each user, and one user is associated with one user authentication device 4 in the authentication server.

Note that a plurality of terminal devices 1 having the same functions may be connected to the network 2. Further, the authentication server 3 may determine whether or not to log in a specific service specified by the user among a plurality of specific services.

In the system shown in FIG. 1, when the terminal device 1 accepts a predetermined user operation, the terminal device 1 transmits the fixed user authentication data (such as the user ID of the specific service) specific to the specific service via the network 2. Without sending a service login request for the specific service to the authentication server 3.

Upon receiving the service login request, the authentication server 3 executes device authentication of the terminal device 1 that is the transmission source of the service login request. When the device authentication of the terminal device 1 is successful, the authentication server 3 corresponds to the specific service. A service code is generated and transmitted via the network 2 to the terminal device 1 that is the transmission source of the service login request. That is, the authentication server 3 has not specified the user at this point. The generated service code is held in association with the service login request and the terminal device 1.

When the terminal device 1 receives the service code, the terminal device 1 outputs the received service code in a predetermined form (a form corresponding to the service code input form in the user authentication device 4). For example, when the service code is input by the user in the user authentication device 4, the terminal device 1 displays or prints the received service code as text. For example, when the service code is input by reading a visible code such as a 2D code in the user authentication device 4, the terminal device 1 encodes the received service code into a visible code and displays the visible code. Or print. Further, for example, when the service code is input by wired communication or short-range wireless communication in the user authentication device 4, the terminal device 1 outputs the received service code as data by the wired communication or short-range wireless communication. To do.

When the user authentication device 4 receives the input of the service code output from the terminal device 1 in a predetermined form, the user authentication device 4 authenticates the input service code without transmitting fixed user authentication data via the network 2. Send to server 3.

Upon receiving the service code, the authentication server 3 executes device authentication of the user authentication device 4 that is the transmission source of the service code, and if the device authentication of the user authentication device 4 is successful, the authentication server 3 associates with the user authentication device 4 Log-in of the specified service specified by the received service code (that is, the specified service specified by the service login request corresponding to the service code) is permitted. That is, the authentication server 3 has specified the user at this time.

In this embodiment, one-time authentication is repeatedly executed as mutual device authentication between the authentication server 3 and the terminal device 1, and mutual authentication is performed between the authentication server 3 and the user authentication device 4. One-time authentication is repeatedly executed as device authentication. Note that mutual device authentication may be realized by another authentication process.

Specifically, each of the terminal device 1 and the authentication server 3 generates its own seed, encrypts the generated seed, transmits and receives each other, generates the generated seed, and receives and decrypts the communication partner seed. A communication partner that has generated its own one-time authenticator (such as a one-time ID), sends and receives the generated one-time authenticator to each other, and based on the generated seed and the seed of the received and decrypted communication partner. The one-time authenticator is authenticated, and each time the authentication is successful, the next authentication seed is generated and the own seed is updated. Authentication for this one-time authenticator is called one-time authentication.

The terminal device 1 transmits the seed generated by itself and the one-time authenticator generated by itself to the authentication server 3 through the network 2 together with the service login request. The authentication server 3 encrypts the service code described above, and transmits the self-generated seed and the self-generated one-time authenticator together with the encrypted service code via the network 2 at the source of the service login request. It transmits to a certain terminal device 1. When the terminal device 1 receives the encrypted service code, the terminal device 1 decrypts the received encrypted service code. When the authentication server 3 succeeds in authenticating the received one-time identifier of the terminal device 1, the authentication server 3 considers that the device authentication of the terminal device 1 is successful.

Further, the authentication server 3 and the user authentication device 4 perform the same one-time authentication independently of the one-time authentication of the authentication server 3 and the terminal device 1 and perform mutual device authentication.

Specifically, each of the user authentication device 4 and the authentication server 3 generates its own seed, encrypts the generated self seed, transmits and receives each other, generates the generated self seed, and receives and decrypts the communication partner. Generate a one-time authenticator from the seed, send and receive the generated one-time authenticator to each other, and authenticate the received one-time authenticator based on the generated self seed and the received and decrypted communication partner seed Each time the authentication is successful, the next authentication seed is generated and the own seed is updated.

The user authentication device 4 encrypts the service code described above, and transmits the seed generated by itself and the one-time authenticator generated by itself to the authentication server 3 together with the encrypted service code. When the authentication server 3 receives the encrypted service code, the authentication server 3 decrypts the received encrypted service code. Then, if the authentication server 3 succeeds in authenticating the received one-time identifier of the user authentication device 4, the authentication server 3 regards that the device authentication of the user authentication device 4 is successful.

In this embodiment, in the one-time authentication between the terminal device 1 and the authentication server 3, the terminal device 1 encrypts the generated seed with the common encryption key, transmits the encrypted seed, and the authentication server 3 decrypts the received encrypted seed with the common encryption key. Further, the authentication server 3 encrypts the service code with the common encryption key.

Furthermore, in this embodiment, each time the authentication for the one-time authenticator succeeds, the terminal device 1 and the authentication server 3 respectively generate at least the generated seed and the received and decrypted seed of the communication partner (here, The current common encryption key, the generated self seed, and the received and decrypted communication partner seed). That is, the terminal device 1 and the authentication server 3 each update their own common encryption key, and key distribution of the updated common encryption key is not performed.

In this embodiment, in the one-time authentication between the user authentication device 4 and the authentication server 3, the user authentication device 4 encrypts the generated seed with a common encryption key, and encrypts the seed. The authentication server 3 decrypts the received encrypted seed with the common encryption key. The common encryption key in the one-time authentication between the user authentication device 4 and the authentication server 3 is generated and updated separately from the common encryption key in the one-time authentication between the terminal device 1 and the authentication server 3. To go. The authentication server 3 decrypts the received encrypted service code with the common encryption key.

Furthermore, in this embodiment, each time the user authentication device 4 and the authentication server 3 succeed in authenticating the one-time authenticator, at least the generated self seed and the received and decrypted communication partner seed (current Common encryption key, generated self seed, and received and decrypted communication partner seed). That is, the terminal device 1 and the authentication server 3 each update their own common encryption key, and key distribution of the updated common encryption key is not performed.

Hereinafter, the configuration and operation of each device in the above system will be described.

(1) Terminal device 1

FIG. 2 is a block diagram showing a configuration of the terminal device 1 in FIG. As shown in FIG. 2, the terminal device 1 includes a computer having a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, and the like.

The CPU 11 is a processor that executes a program and executes processing described in the program. The ROM 12 is a nonvolatile memory that stores programs and data in advance. The RAM 13 is a volatile memory that temporarily stores the program and data when the program is executed.

The interface 14 is an interface circuit to which the storage device 15 can be connected. The storage device 15 is connected to the interface 14 and has a recording medium that stores an operating system (not shown), an authentication program 31, an application program 32, and the like. Device. As the storage device 15, a nonvolatile storage device such as a hard disk drive or SSD (Solid State Disk) is used.

The interface 16 is an interface circuit to which the communication device 17 can be connected. The communication device 17 is a device that can be connected to the network 2 such as a network interface or a modem.

The interface 18 is a peripheral device interface such as IEEE1394 or USB (Universal Serial Bus).

The interface 20 is an interface circuit to which the input device 21 can be connected. The input device 21 is a device that receives a user operation such as a keyboard and a mouse and outputs a signal corresponding to the user operation.

The image processing circuit 22 is a circuit that outputs an image signal corresponding to the data when the image data is written. A display device 23 that displays an image based on the image signal can be connected to the image processing circuit 22.

The CPU 11, ROM 12, RAM 13, interfaces 14, 16, 18, 20 and image processing circuit 22 are connected to each other via a bus or a controller chip so that data communication can be performed.

FIG. 3 is a block diagram showing a processing unit realized in the terminal device 1 shown in FIG. As shown in FIG. 3, in the terminal device 1, a communication processing unit 41, an authentication processing unit 42, and a service code output unit 43 are realized.

The communication processing unit 41 uses the communication device 17 to perform data communication with the authentication server 3 and the like via the network 2 using a predetermined communication protocol.

The authentication processing unit 42 is realized by the CPU 11 executing the authentication program 31, and uses the communication device 17 and the communication processing unit 41 to (a) transmit the above-described service login request, and (b) the authentication server 3. Is a processing unit that executes client-side processing and the like in mutual device authentication based on one-time authentication with the client.

The service code output unit 43 is a processing unit that is realized by the authentication program 31 being executed by the CPU 11 and outputs the above-described service code.

The application 44 is realized by the CPU 11 executing the application program 32. After the service login is permitted by the authentication server 3, the application 44 transmits a transmission request for data of a specific service, receives the data, and receives the data. A processing unit that performs data processing and the like.

(2) Authentication server 3

FIG. 4 is a block diagram showing a configuration of the authentication server 3 in FIG.

In FIG. 4, a CPU 51 is a processor that executes a program and executes processing described in the program. The ROM 52 is a nonvolatile memory that stores programs and data in advance. The RAM 53 is a memory that temporarily stores the program and data when the program is executed.

The interface 54 is an interface circuit to which the storage device 55 can be connected. The storage device 55 is connected to the interface 54 and stores an operating system (not shown), an authentication program 61, data used for authentication, and the like. A device having a medium. As the storage device 55, a nonvolatile storage device such as a hard disk drive or an SSD is used.

The storage device 55 stores a seed table 71a, an authenticator table 72a, and a terminal attribute table 73a as data used for one-time authentication between the terminal device 1 and the authentication server 3, and user authentication is performed. As data used for one-time authentication between the device 4 and the authentication server 3, a seed table 71b, an authenticator table 72b, and a device attribute table 73b are stored.

The seed table 71a has a next authentication seed and a next authentication common encryption key updated at the last authentication in the one-time authentication between the terminal device 1 and the authentication server 3. The seed table 71b has a next authentication seed and a next authentication common encryption key updated at the last authentication in the one-time authentication between the user authentication device 4 and the authentication server 3.

The authenticator table 72 a has a client-side one-time authenticator for next authentication updated at the last authentication in the one-time authentication between the terminal device 1 and the authentication server 3. The authenticator table 72b includes a client-side one-time authenticator for next authentication updated at the last authentication in the one-time authentication between the user authentication device 4 and the authentication server 3.

The terminal attribute table 73a is a table having a device ID of each terminal device 1 and attribute information (such as owner information) associated with the device ID. The device ID of each terminal device 1 in the terminal attribute table 73a is associated with the one-time identifier of the terminal device 1 in the identifier table 72a. In the terminal attribute table 73a, the one-time identifier of each terminal device 1 may be used instead of the device ID of each terminal device 1.

The device attribute table 73b is a table having a device ID of each user authentication device 4 and attribute information (user ID, owner information, etc.) associated with the device ID. The device ID of each user authentication device 4 in the device attribute table 73b is associated with the one-time identifier of the user authentication device 4 in the identifier table 72b. In the device attribute table 73b, the one-time identifier of each user authentication device 4 may be used instead of the device ID of each user authentication device 4.

The user attribute table 74 includes the user ID of each user and attribute information associated with the device ID (name, user ID used in the specific service, billing information when the specific service is a paid service, etc.). It is a table. Each user ID in the user attribute table 74 is associated with the same user ID in the device attribute table 73b.

The interface 56 is an interface circuit to which the communication device 57 can be connected. The communication device 57 is a device connectable to the network 3 such as a network interface card or a modem.

The CPU 51, the ROM 52, the RAM 53, and the

interfaces

54 and 56 are connected to each other by a bus or a controller chip so that data communication can be performed.

FIG. 5 is a block diagram showing a processing unit realized in the authentication server 3 shown in FIG. In the authentication server 3 shown in FIG. 5, a communication processing unit 81, a server-side authentication processing unit 82, a service code management unit 83, and a service providing unit 84 are realized.

The communication processing unit 81 uses the communication device 57 to perform data communication with the terminal device 1 and the user authentication device 4 via the network 2 using a predetermined communication protocol.

The server-side authentication processing unit 82 is realized by the CPU 51 executing the authentication program 61. Using the communication processing unit 81, server-side processing in mutual device authentication by one-time authentication with each terminal device 1, And server-side processing in mutual device authentication based on one-time authentication with each user authentication device 4.

The server side authentication processing unit 82 permits the service login when the service code is appropriately transmitted from the user authentication device 4 in response to the service login request, and otherwise, the service login. To refuse.

The service code management unit 83 generates a service code, sets a service code expiration date, associates a service login request (that is, the terminal device 1 that transmitted the service login request) with the generated service code, and the like. It is.

For example, the service code management unit 83 validates the service code before the expiration date of the service code, invalidates the service code after the expiration date of the service code, and the server-side authentication processing unit 82 If the code is invalid, the service login is rejected even if the received service code is appropriate.

The service providing unit 84 uses the communication device 57 and the communication processing unit 81 after the service login is permitted by the server-side authentication processing unit 82, and the terminal device 1 that is permitted to log in by the server-side authentication processing unit 82. The service data is transmitted to the terminal device 1 as a response to the service data request received from.

(3) User authentication device 4

FIG. 6 is a block diagram showing the configuration of the user authentication device 4 in FIG. As shown in FIG. 6, the user authentication device 4 includes a computer having a CPU 111, a ROM 112, a RAM 113, and the like.

The CPU 111 is a processor that executes a program and executes processing described in the program. The ROM 112 is a non-volatile memory that stores programs and data in advance. The RAM 113 is a volatile memory that temporarily stores the program and data when the program is executed.

The interface 114 is an interface circuit to which the storage device 115 can be connected. The storage device 115 is connected to the interface 114 and has a recording medium that stores an operating system (not shown), an authentication program 131, and the like. As the storage device 115, a nonvolatile storage device such as a flash memory is used.

Further, the interface 116 is an interface circuit to which the communication device 117 can be connected. The communication device 117 is a device that can be connected to the network 2 such as a network interface, or a baseband unit of a mobile phone that can be connected to the network 2 via a mobile phone network. The interface 118 is a peripheral device interface such as a USB.

The interface 120 is an interface circuit to which the input device 121 can be connected. The input device 121 is a device that receives a user operation such as a hard key or a touch panel and outputs a signal corresponding to the user operation.

The image processing circuit 122 is a circuit that outputs an image signal corresponding to the data to the display device 123 when the image data is written. The display device 123 is a liquid crystal display or the like, and displays an image based on the image signal.

The CPU 111, the ROM 112, the RAM 113, the

interfaces

114, 116, 118, 120, and the image processing circuit 122 are connected to each other by a bus or a controller chip so that data communication is possible.

FIG. 7 is a block diagram showing a processing unit realized in the user authentication device 4 shown in FIG. As shown in FIG. 7, in this user authentication device 4, a communication processing unit 141 and an authentication processing unit 142 are realized.

The communication processing unit 141 uses the communication device 117 to perform data communication with the authentication server 3 and the like via the network 2 using a predetermined communication protocol.

The authentication processing unit 142 is realized by executing the authentication program 131 by the CPU 111, and using the communication device 117 and the communication processing unit 141, (a) receiving the service code input and transmitting the service code, (B) A processing unit that executes processing on the client side in mutual device authentication based on one-time authentication with the authentication server 3.

(4) Processing at service login

FIG. 8 is a sequence diagram for explaining processing at the time of service login in the system shown in FIG.

The user operates the terminal device 1 to select a specific service, and transmits a service login request for the selected specific service to the authentication server 3.

At this time, in the terminal apparatus 1, when the user operation is detected by the input device 21, the authentication processing unit 42 encrypts the next seed R1 (n) of the terminal apparatus 1 with the encryption key K1 (n-1), and performs communication. Using the device 17 and the communication processing unit 41, a service login request, a one-time authenticator C1 (n-1) of the terminal device 1 for device authentication, and an encrypted seed K1 (n-1) of the terminal device 1 ) * R1 (n) are collectively transmitted as one message (step S1).

In the authentication server 3, the server-side authentication processing unit 82 uses the communication device 57 and the communication processing unit 81 to make a service login request, a one-time authenticator C1 (n−1), and an encrypted seed K1 (n− 1) When * R1 (n) is received, the encrypted seed K1 (n-1) * R1 (n) is decrypted, and the received seed R1 (n) of the terminal device 1 decrypted and the authentication held Based on the seed Q1 (n-1) of the server 3, it is determined whether or not the one-time authenticator C1 (n-1) is valid. That is, the one-time authenticator C1 (n-1) is calculated from the seed R1 (n) and the seed Q1 (n-1), and the calculated one-time authenticator C1 (n-1) and the received one-time authenticator It is determined whether or not the child C1 (n-1) matches.

If the server-side authentication processing unit 82 determines that the one-time authenticator C1 (n-1) is valid, it determines that the device authentication of the terminal device 1 as the transmission source has succeeded (step S2).

When it is determined that the device authentication of the terminal device 1 as the transmission source has been successful, the service code management unit 83 generates a service code (step S3). For example, a random number is used as the service code.

In addition, when the device authentication of the transmission source terminal device 1 fails, the service code is not generated and the service login request is rejected.

If the device authentication of the terminal device 1 is successful, the server-side authentication processing unit 82 encrypts the next seed Q1 (n) and service code of the authentication server 3 with the encryption key K1 (n−1), and the communication device 57 and Using the communication processing unit 81, the encrypted service code, the one-time authenticator S 1 (n−1) of the authentication server 3 for device authentication, and the seed K 1 (n−) of the encrypted authentication server 3 1) * Q1 (n) are collectively transmitted as one message to the terminal device 1 (step S4).

In the terminal device 1, the authentication processing unit 42 uses the communication device 17 and the communication processing unit 41 to encrypt the encrypted service code, the one-time authenticator S1 (n−1), and the encrypted seed K1. When (n-1) * Q1 (n) is received, the encrypted service code and the encrypted seed K1 (n-1) * Q1 (n) are decrypted and held in the seed of the terminal device 1 Based on R1 (n−1) and the received and decrypted authentication server 3 seed Q1 (n), it is determined whether or not the one-time authenticator S1 (n−1) is valid. That is, the one-time authenticator S1 (n-1) is calculated from the seed R1 (n-1) and the seed Q1 (n), and the calculated one-time authenticator S1 (n-1) and the received one-time authenticator It is determined whether or not the child S1 (n-1) matches.

If the authentication processing unit 42 determines that the one-time authenticator S1 (n-1) is valid, it determines that the device authentication of the authentication server 3 as the transmission source has succeeded (step S5).

If the authentication server 3 succeeds in device authentication, the service code output unit 43 outputs the service code in a predetermined form (step S6). The output service code is input to the user authentication device 4.

Here, the service code output unit 43 uses the image processing circuit 22 to display the service code as text on the display device 23. Then, the user operates the input device 121 to input the service code as the displayed text into the user authentication device 4.

In the user authentication device 4, the authentication processing unit 142 is activated in accordance with a user operation (step S7). A user ID and a password may be requested to activate the authentication processing unit 142. In this case, if a regular user ID and password registered in advance are input to the user authentication device 4, the authentication processing unit 142 is activated, but when a user ID and password other than the regular user ID and password are input. The authentication processing unit 142 is not activated. Note that the user ID and password input to the user authentication device 4 are not transmitted to the outside. Further, biometric authentication using biometric information such as a fingerprint may be performed instead of authentication using a user ID and password.

Thereafter, when the authentication processing unit 142 acquires the input service code (step S8), the service code and the next seed R2 (n) of the user authentication device 4 are encrypted with the encryption key K2 (n−1), Using the communication device 117 and the communication processing unit 141, a user authentication request, an encrypted service code, a one-time authenticator C2 (n-1) of the user authentication device 4 for device authentication, and an encrypted The seeds K2 (n−1) * R2 (n) of the user authentication device 4 are collectively transmitted to the authentication server 3 as one message (step S9).

In the authentication server 3, the server-side authentication processing unit 82 uses the communication device 57 and the communication processing unit 81 to use the user authentication request, the encrypted service code, the one-time authenticator C 2 (n−1), and the encryption When the encrypted seed K2 (n-1) * R2 (n) is received, the encrypted service code and the encrypted seed K2 (n-1) * R2 (n) are decrypted, received and decrypted Whether or not the one-time authenticator C2 (n-1) is valid based on the seed R2 (n) of the user authentication device 4 and the seed Q2 (n-1) of the held authentication server 3 judge. That is, the one-time authenticator C2 (n-1) is calculated from the seed R2 (n) and the seed Q2 (n-1), and the calculated one-time authenticator C2 (n-1) and the received one-time authenticator It is determined whether or not the child C2 (n-1) matches.

When the server-side authentication processing unit 82 determines that the one-time authenticator C2 (n−1) is valid, it determines that the device authentication of the user authentication device 4 that is the transmission source has succeeded (step S10). A user authentication response is transmitted to the user authentication device 4 (step S11). At this time, the server-side authentication processing unit 82 determines that the user authentication of the user associated with the user authentication device 4 that has succeeded in device authentication has succeeded.

Note that if the device authentication of the user authentication device 4 of the transmission source fails, the service login request is rejected.

If the server-side authentication processing unit 82 determines that the user authentication of the user has been successful, the server-side authentication processing unit 82 identifies the user as the user who transmitted the service login request, and permits login to the specific service specified by the service login request. Then, using the communication device 57 and the communication processing unit 81, a service login permission notification is transmitted to the terminal device 1 in which the service code is generated (step S12). Thereby, the user who enjoys the specific service is specified on the specific service side. Therefore, it is possible to transmit data for the user with a specific service or charge the user for a service usage fee. The service login permission notification may not be transmitted to the terminal device 1. In this case, the terminal device 1 may transmit a service data request after a predetermined time has elapsed from the output of the service code (step S6).

In the terminal device 1, when the authentication processing unit 42 receives the service login permission notification using the communication device 17 and the communication processing unit 41, the authentication processing unit 42 notifies the application 44 that login is permitted.

Thereafter, the application 44 of the terminal device 1 uses the communication device 17 and the communication processing unit 41 to transmit a service data request for a specific service to the service providing unit 84 (in this case, the authentication server 3) (step S13). .

In the authentication server 3, when the service providing unit 84 receives the service data request using the communication device 57 and the communication processing unit 81, the service providing unit 84 transmits the data specified by the service data request to the application 44 of the terminal device 1 ( Step S14).

In this way, the user of the terminal device 1 can enjoy the specific service using the terminal device 1 after receiving the user authentication using the user authentication device 4.

(5) Details of one-time authentication between the terminal device 1 and the authentication server 3

FIG. 9 is a sequence diagram illustrating details of one-time authentication between the terminal device 1 and the authentication server 3 in the embodiment of the present invention.

In the terminal device 1 and the authentication server 3, the seed R 1 (n−1) of the terminal device 1, the seed Q 1 (n−1) of the authentication server 3, and the common encryption key K 1 (n−1) are stored in the

storage devices

15 and 55. Etc., each of which is held in a nonvolatile storage device. The initial seed value R1 (0) of the terminal device 1, the initial seed value Q1 (0) of the authentication server 3, and the initial value K1 (0) of the common encryption key are set as appropriate. In the authentication server 3, a one-time identifier C1 (n-1) on the client side is calculated and held in advance.

The seed R1 (n-1) is a client-side seed for the one-time authentication of this time (n-1). The seed Q1 (n-1) is a server-side seed for the current one-time authentication (n-1). The common encryption key K1 (n-1) is used when the client side seed R1 (n) for next authentication is transmitted to the authentication server 3 during the one-time authentication of this time (n-1). This is a common encryption key for encryption.

First, the authentication processing unit 42 generates a random number R, and sets the random number R in the client side seed R1 (n) for the next authentication (step S21).

Then, the authentication processing unit 42 generates a client-side one-time authenticator C1 (n-1) for the current one-time authentication (step S22).

The one-time authenticator C1 (n-1) is calculated with a one-way function. This one-way function is a function that takes two arguments and has different function values depending on the order of the arguments. In this embodiment, the one-way function is a hash function hc.

The one-time authenticator C1 (n-1) is calculated according to the following equation, for example.

C1 (n-1) = hc (R1 (n-1), Q1 (n-1)) (1)

Here, R1 (n-1) is used as the first argument of the hash function hc, and Q1 (n-1) is used as the second argument.

Further, the authentication processing unit 42 encrypts R1 (n) with the common encryption key K1 (n-1) according to a predetermined encryption method. Note that R1 (n) after encryption with the common encryption key K1 (n-1) is expressed as K1 (n-1) * R1 (n).

Then, the authentication processing unit 42 transmits the one-time authenticators C1 (n-1) and K1 (n-1) * R1 (n) to the authentication server 3 (steps S23 and S1). At this time, the communication processing unit 41 transmits the one-time authenticators C1 (n−1) and K1 (n−1) * R1 (n) as one message.

In the authentication server 3, the server-side authentication processing unit 82 uses the communication processing unit 81 to receive the message, and from the message, the one-time authenticators C1 (n-1) and K1 (n-1) * R1 (N) is extracted, and the received one-time authenticator C1 (n−1) holds the client-side one-time authenticator (that is, held seeds R1 (n−1), Q1 (n− 1) to (the value obtained by the above equation (1)) is determined (steps S24 and S2).

When it is determined that the received one-time authenticator C1 (n-1) is an invalid one-time authenticator, the server-side authentication processing unit 82 determines that the authentication has failed and ends the process.

When the received one-time authenticator C1 (n-1) matches the client-side one-time authenticator stored in the authenticator table 72a, the server-side authentication processing unit 82 determines that the authentication is successful, A random number Q is generated, and the random number Q is set in the server side seed Q1 (n) for the next authentication (step S25).

The server-side authentication processing unit 82 decrypts K1 (n-1) * R1 (n) into R1 (n) using the common encryption key K1 (n-1) held in the seed table 71a. Then, the server-side authentication processing unit 82 generates a server-side one-time authenticator S1 (n-1) for the current (n-1) one-time authentication (step S26).

The one-time authenticator S1 (n-1) is calculated with a one-way function. This one-way function is a function that takes two arguments and has different function values depending on the order of the arguments. In this embodiment, the one-way function is a hash function hs.

The one-time authenticator S1 (n-1) is calculated according to the following formula.

S1 (n-1) = hs (R1 (n), Q1 (n-1)) (2)

Here, R1 (n) is used as the first argument of the hash function hs, and Q1 (n-1) is used as the second argument. The hash function hs may be the same function as the hash function hc or a different function.

Further, the server side authentication processing unit 82 encrypts Q1 (n) with the common encryption key K1 (n-1) according to a predetermined encryption method. Note that Q1 (n) after encryption with the common encryption key K1 (n-1) is expressed as K1 (n-1) * Q1 (n).

Then, the server side authentication processing unit 82 uses the communication processing unit 81 to transmit the one-time authenticators S1 (n-1) and K1 (n-1) * Q1 (n) to the terminal device 1 (Step S1). S27, S4). At this time, the communication processing unit 81 transmits the one-time authenticators S1 (n-1) and K1 (n-1) * Q1 (n) as one message.

In the terminal device 1, the authentication processing unit 42 uses the communication processing unit 41 to receive the message and extract the one-time authenticators S1 (n-1) and K1 (n-1) * Q1 (n) To do.

Then, the authentication processing unit 42 calculates the value of the valid one-time authenticator S1 (n-1) based on R1 (n) and Q1 (n-1) according to the above equation (2) and receives it. It is determined whether or not the one-time authenticator S1 (n-1) matches the calculated value (step S28).

At this time, if the received one-time authenticator S1 (n-1) does not match the calculated value, the authentication processing unit 43 determines that the authentication has failed and ends the process.

If the received one-time authenticator S1 (n-1) matches the calculated value, the authentication processing unit 42 determines that the authentication is successful, and first holds K1 (n-1) * Q1 (n). The common encryption key K1 (n-1) is decrypted to Q1 (n), and this value is set as the server-side seed for the next authentication.

Then, the authentication processing unit 42 calculates a common encryption key K1 (n) for next authentication according to the following equation, and updates the common encryption key (step S29).

K1 (n) = hk (K1 (n-1), R1 (n), Q1 (n)) (3)

Here, hk is a one-way function and a hash function.

In this way, after successful one-time authentication, the authentication processing unit 42 uses the stored seeds R1 (n−1), Q1 (n−1) and the common encryption key K1 (n−1) as R1. Update with (n) and Q1 (n) and K1 (n).

On the other hand, also in the authentication server 3, after transmitting the one-time authenticator S1 (n-1), the server-side authentication processing unit 82 calculates the next authentication common encryption key K1 (n) according to the above-described equation (3). Then, the common encryption key is updated (step S30).

Further, the server-side authentication processing unit 82 calculates a client-side one-time authenticator C1 (n) to be used at the next one-time authentication from R1 (n) and Q1 (n) according to the above equation (1). . And the server side authentication process part 82 updates the data about the terminal device 1 in the seed table 71a with R1 (n), Q1 (n), and K1 (n), and the authenticator table with C1 (n). The one-time authenticator for the terminal device 1 in 72a is updated. Thus, these values are held until the next session (that is, the next one-time authentication).

In this way, one-time authentication between the terminal device 1 and the authentication server 3 is executed.

(6) Details of one-time authentication between the user authentication device 4 and the authentication server 3

FIG. 10 is a sequence diagram illustrating details of the one-time authentication between the user authentication device 4 and the authentication server 3 in the embodiment of the present invention. Note that the processing shown in FIG. 9 and the processing shown in FIG. 10 are performed independently.

In the user authentication device 4 and the authentication server 3, the seed R2 (n-1) of the user authentication device 4, the seed Q2 (n-1) of the authentication server 3, and the common encryption key K2 (n-1) are stored in the storage device 115. , 55 and so on, respectively. Note that the initial value R2 (0) of the seed of the user authentication device 4, the initial value Q2 (0) of the seed of the authentication server 3, and the initial value K2 (0) of the common encryption key are set as appropriate. In the authentication server 3, a one-time identifier C2 (n-1) on the client side is calculated and held in advance.

The seed R2 (n-1) is a client-side seed for the one-time authentication of this time (n-1). The seed Q2 (n-1) is a server-side seed for the one-time authentication of this time (n-1). The common encryption key K2 (n-1) is used when the client side seed R2 (n) for next authentication is transmitted to the authentication server 3 during the one-time authentication of this time (n-1). This is a common encryption key for encryption.

First, the authentication processing unit 142 generates a random number R and sets the random number R in the client side seed R2 (n) for next authentication (step S41).

Then, the authentication processing unit 142 generates a client-side one-time authenticator C2 (n-1) for the current one-time authentication (step S42).

The one-time authenticator C2 (n-1) is calculated with a one-way function. This one-way function is a function that takes two arguments and has different function values depending on the order of the arguments. In this embodiment, the one-way function is a hash function hc.

The one-time authenticator C2 (n-1) is calculated according to the following equation, for example.

C2 (n-1) = hc (R2 (n-1), Q2 (n-1)) (4)

Here, R2 (n-1) is used as the first argument of the hash function hc, and Q2 (n-1) is used as the second argument. Note that the hash function hc for generating the one-time authenticator C2 (n-1) may be the same as or different from the hash function hc for generating the one-time authenticator C1 (n-1). .

Further, the authentication processing unit 42 encrypts R2 (n) with the common encryption key K2 (n-1) according to a predetermined encryption method. Note that R2 (n) after encryption with the common encryption key K2 (n-1) is expressed as K2 (n-1) * R1 (n).

Then, the authentication processing unit 42 transmits the one-time authenticators C2 (n−1) and K2 (n−1) * R2 (n) to the authentication server 3 (Steps S43 and S9). At this time, the communication processing unit 41 transmits the one-time authenticators C2 (n−1) and K2 (n−1) * R2 (n) as one message.

In the authentication server 3, the server-side authentication processing unit 82 uses the communication processing unit 81 to receive the message, and from the message, the one-time authenticators C2 (n-1) and K2 (n-1) * R2 (N) is extracted, and the received one-time authenticator C2 (n-1) holds the client-side one-time authenticator (that is, held seeds R2 (n-1), Q2 (n- 1) to (the value obtained by the above equation (4)) is determined (step S44).

When it is determined that the received one-time authenticator C2 (n-1) is an invalid one-time authenticator, the server-side authentication processing unit 82 determines that the authentication has failed and ends the process.

When the received one-time authenticator C2 (n-1) matches the client-side one-time authenticator stored in the authenticator table 72b, the server-side authentication processing unit 82 determines that the authentication is successful, A random number Q is generated, and the random number Q is set in the server side seed Q2 (n) for the next authentication (step S45).

The server-side authentication processing unit 82 decrypts K2 (n−1) * R2 (n) into R2 (n) using the common encryption key K2 (n−1) held in the seed table 71b. Then, the server-side authentication processing unit 82 generates the server-side one-time authenticator S2 (n-1) for the current (n-1) one-time authentication (step S46).

The one-time authenticator S2 (n-1) is calculated with a one-way function. This one-way function is a function that takes two arguments and has different function values depending on the order of the arguments. In this embodiment, the one-way function is a hash function hs.

The one-time authenticator S2 (n-1) is calculated according to the following formula.

S2 (n-1) = hs (R2 (n), Q2 (n-1)) (5)

Here, R2 (n) is used for the first argument of the hash function hs, and Q2 (n-1) is used for the second argument. The hash function hs may be the same function as the hash function hc or a different function. Further, the hash function hs for generating the one-time authenticator S2 (n-1) may be the same as or different from the hash function hs for generating the one-time authenticator S1 (n-1). .

Further, the server side authentication processing unit 82 encrypts Q2 (n) with the common encryption key K2 (n-1) according to a predetermined encryption method. Note that Q2 (n) after encryption with the common encryption key K2 (n-1) is expressed as K2 (n-1) * Q2 (n).

Server-side authentication processing unit 82 then uses communication processing unit 81 to transmit one-time authenticators S2 (n−1) and K2 (n−1) * Q2 (n) to terminal device 1 (step S1). S47, S11). At this time, the communication processing unit 81 transmits the one-time authenticators S2 (n-1) and K2 (n-1) * Q2 (n) as one message.

In the user authentication device 4, the authentication processing unit 142 uses the communication processing unit 141 to receive the message, and sends one-time authenticators S2 (n−1) and K2 (n−1) * Q2 (n). Extract.

Then, the authentication processing unit 142 calculates the value of the valid one-time authenticator S2 (n−1) according to the above equation (5) based on R2 (n) and Q2 (n−1) and receives it. It is determined whether or not the one-time authenticator S2 (n-1) matches the calculated value (step S48).

At this time, if the received one-time authenticator S2 (n-1) does not match the calculated value, the authentication processing unit 143 determines that the authentication has failed and ends the process.

If the received one-time authenticator S2 (n−1) matches the calculated value, the authentication processing unit 142 determines that the authentication is successful, and first holds K2 (n−1) * Q2 (n). The common encryption key K2 (n-1) is decrypted to Q2 (n), and this value is set as the server-side seed for the next authentication.

Then, the authentication processing unit 142 calculates the next authentication common encryption key K2 (n) according to the following equation, and updates the common encryption key (step S49).

K2 (n) = hk (K2 (n−1), R2 (n), Q2 (n)) (6)

Here, hk is a one-way function and a hash function. Note that the hash function hk for generating K2 (n) may be the same as or different from the hash function hk for generating K1 (n).

After successful one-time authentication in this way, the authentication processing unit 142 uses the stored seeds R2 (n−1), Q2 (n−1) and the common encryption key K2 (n−1) as R2 Update with (n) and Q2 (n) and K2 (n).

On the other hand, also in the authentication server 3, after transmitting the one-time authenticator S2 (n-1), the server-side authentication processing unit 82 calculates the next authentication common encryption key K2 (n) according to the above-described equation (6). Then, the common encryption key is updated (step S50).

Further, the server-side authentication processing unit 82 calculates a client-side one-time authenticator C2 (n) to be used at the next one-time authentication from R2 (n) and Q2 (n) according to the above equation (4). . Then, the server-side authentication processing unit 82 updates data on the user authentication device 4 in the seed table 71b with R2 (n), Q2 (n), and K2 (n), and with C2 (n) The one-time authenticator for the user authentication device 4 in the table 72b is updated. Thus, these values are held until the next session (that is, the next one-time authentication).

In this way, one-time authentication between the user authentication device 4 and the authentication server 3 is executed.

As described above, according to the above embodiment, (a) the terminal device 1 transmits a service login request for a specific service to the authentication server 3 without transmitting fixed user authentication data, and (b) authentication. Upon receiving the service login request, the server 3 executes device authentication of the terminal device 1 that is the transmission source of the service login request, and generates a service code corresponding to the specific service when the device authentication of the terminal device 1 is successful. (C) When the terminal device 1 receives the service code, the terminal device 1 outputs the received service code in a predetermined form. (D) The user authentication device 4 When the input of the service code output by the terminal device 1 is received in a predetermined form, the input service is not transmitted without transmitting the fixed user authentication data. (E) Upon receiving the service code, the authentication server 3 executes device authentication of the user authentication device 4 that is the source of the service code and succeeds in device authentication of the user authentication device 4 In such a case, the user associated with the user authentication device 4 is permitted to log in the specific service specified by the received service code.

This allows a user to be identified and authorized to log in to a regular user without transmitting / receiving user authentication data required for user authentication for service login via a communication path such as the Internet.

For example, when the terminal device 1 on the client side is a terminal device that can be used by a plurality of users (for example, a terminal device in which a multiuser operating system is operating), even if the terminal device 1 is successfully authenticated, the terminal device 1 Although it is difficult to specify the user who is operating at the present time, according to the system of the above embodiment, the user of the terminal device 1 is specified.

It should be noted that various changes and modifications to the above-described embodiments will be apparent to those skilled in the art. Such changes and modifications may be made without departing from the spirit and scope of the subject matter and without diminishing its intended advantages. That is, such changes and modifications are intended to be included within the scope of the claims.

For example, in the above-described embodiment, after the service login is permitted, for the communication between the service providing unit 84 and the terminal device 1, the one-time authentication of the phase 2 described in Japanese Patent Application Laid-Open No. 2012-34292 (that is, the above-mentioned One-time authentication, which is a different series from the one-time authentication described above, derived from the one-time authentication may be repeatedly performed.

Further, in the above embodiment, the service providing unit 84 may be provided in a server different from the authentication server 3, and service data may be provided from the server to the terminal device 1 after service login permission.

Further, in the above embodiment, the

authentication programs

31, 61, 131 may be recorded on a portable computer-readable recording medium (such as a CD-ROM). In that case, the

authentication programs

31, 61, 131 may be read from the recording medium and installed in the terminal device 1, the authentication server 3, or the user authentication device 4 described above. In the above embodiment, the

authentication programs

31, 61, 131 may be downloaded from a server and installed in the terminal device 1, the authentication server 3, or the user authentication device 4 described above.

In the above-described embodiment, one user is associated with one user authentication device 4 in the authentication server 3, but a plurality of users are associated with one user authentication device 4. May be. In that case, the user ID indicating the current user of the user authentication device 4 may be encrypted together with the service code and transmitted to the authentication server 3, and the user ID of the user authentication device 4 may be identified by decoding the user ID. Alternatively, a plurality of one-time authenticators are set independently for a plurality of users of the user authentication device 4, and the current time of the user authentication device 4 is determined by one-time authentication using the one-time authenticator selected by the user authentication device 4. A user may be specified.

In the above embodiment, device authentication is mutually performed between the terminal device 1 and the authentication server 3 by one-time authentication. Instead, the device is mutually or by SSL (Secure Sockets Layer) or the terminal device. 1 and the authentication of only one of the authentication servers 3 may be performed.

The present invention is applicable to user authentication in network services, for example.

Claims

An authentication server that determines whether a user can log in to a specific service;
A terminal device operated by the user and receiving data of the specific service;
A user authentication device associated with the user by the authentication server;
(A) The terminal device transmits a service login request for the specific service to the authentication server without transmitting fixed user authentication data,
(B) Upon receiving the service login request, the authentication server generates a service code corresponding to the specific service, and transmits the service code to the terminal device that is the transmission source of the service login request.
(C) Upon receipt of the service code, the terminal device outputs the received service code in a predetermined form,
(D) When the user authentication device receives the input of the service code output by the terminal device in a predetermined form, the user authentication device transmits the input service code without transmitting fixed user authentication data. To the server,
(E) Upon receiving the service code, the authentication server executes device authentication of the user authentication device that is a transmission source of the service code, and when the device authentication of the user authentication device is successful, the user authentication device Permitting the user associated with the login of the specific service specified by the received service code;
A personal authentication system.
When the authentication server receives the service login request, the authentication server executes device authentication of the terminal device that is the transmission source of the service login request, and when the device authentication of the terminal device is successful, the service corresponding to the specific service The personal authentication system according to claim 1, wherein a code is generated and transmitted to the terminal device that is a transmission source of the service login request.
The terminal device and the authentication server each generate a seed, encrypt the generated seed, transmit and receive each other, generate a one-time authenticator from the generated seed and the received and decrypted seed, and generate The one-time authenticator is mutually transmitted and received, and the received one-time authenticator is authenticated based on the generated seed and the received and decoded seed. Generate seed and update the seed,
The terminal device sends the seed generated by itself and the one-time authenticator generated by itself to the authentication server together with the service login request,
The authentication server encrypts the service code, transmits the seed generated by itself and the one-time authenticator generated by itself to the terminal device together with the encrypted service code,
When the terminal device receives the encrypted service code, the terminal device decrypts the received encrypted service code,
When the authentication server succeeds in authenticating the received one-time identifier of the terminal device, the authentication server considers that the device authentication of the terminal device is successful;
The personal authentication system according to claim 2.
The user authentication device and the authentication server each generate a seed, encrypt the generated seed, transmit and receive each other, generate a one-time authenticator from the generated seed and the received and decrypted seed, The generated one-time authenticator is mutually transmitted and received, and the received one-time authenticator is authenticated based on the generated seed and the received and decrypted seed. Generate seeds for the above and update the seeds.
The user authentication device encrypts the service code, transmits the self-generated seed and the self-generated one-time authenticator together with the encrypted service code to the authentication server,
The authentication server (a) receives the encrypted service code, decrypts the received encrypted service code, and (b) authenticates the received one-time identifier of the user authentication device. If successful, the device authentication of the user authentication device is considered successful;
The personal authentication system according to any one of claims 1 to 3, wherein:
The terminal device encrypts the generated seed with a common encryption key, transmits the encrypted seed,
The authentication server (a) decrypts the received encrypted seed with the common encryption key, (b) encrypts the service code with the common encryption key,
Each of the terminal device and the authentication server each updates the common encryption key based on at least the generated seed and the received and decrypted seed each time authentication for the one-time authenticator is successful.
The personal authentication system according to claim 3.
The user authentication device encrypts the generated seed with a common encryption key, transmits the encrypted seed,
The authentication server (a) decrypts the received encrypted seed with the common encryption key, and (b) decrypts the received encrypted service code with the common encryption key,
The user authentication device and the authentication server each update the common encryption key based on at least the generated seed and the received and decrypted seed each time authentication for the one-time authenticator is successful.
The personal authentication system according to claim 4.
In an authentication server that determines whether a user can log in to a specific service,
A communication device;
An authentication processing unit;
A service code generator,
The service code generation unit uses the communication device to request a service login for the specific service without receiving fixed user authentication data from a terminal device operated by the user and receiving the data of the specific service. Is received by the authentication server, a service code corresponding to the specific service is generated,
The authentication processing unit uses the communication device to transmit the generated service code to the terminal device that is a transmission source of the service login request,
The authentication processing unit outputs (a) the terminal device without receiving fixed user authentication data from the user authentication device associated with the user by the authentication server using the communication device. And (b) performing device authentication of the user authentication device that is the transmission source of the received service code, and when the device authentication of the user authentication device is successful, the user authentication device Allowing the associated user to log in to the specific service specified by the received service code;
An authentication server characterized by
In an authentication program executed in an authentication server that determines whether or not a user can log in to a specific service,
A computer in the authentication server and a server-side authentication processing unit;
Function as a service code generator,
The service code generation unit uses the communication device of the authentication server to respond to the specific service without receiving fixed user authentication data from a terminal device operated by the user and receiving the data of the specific service. When a service login request is received by the authentication server, if the terminal device is successfully authenticated, a service code corresponding to the specific service is generated,
The server-side authentication processing unit uses the communication device of the authentication server to transmit the generated service code to the terminal device that is a transmission source of the service login request,
The server-side authentication processing unit (a) uses the communication device of the authentication server, without receiving fixed user authentication data from the user authentication device associated with the user by the authentication server, When receiving the service code output by the terminal device, (b) performing device authentication of the user authentication device that is the transmission source of the received service code, and succeeding in device authentication of the user authentication device, Allowing the user associated with the user authentication device to log in the specific service specified by the received service code;
A computer-readable authentication program.
In an authentication program that is operated by a user and is executed in a terminal device that receives data of a specific service that is determined by the authentication server as to whether or not the user can log in,
A computer in the terminal device;
An authentication processing unit;
Function as a service code output unit,
The authentication processing unit
(A) Sending a service login request for the specific service to the authentication server without sending fixed user authentication data;
(B) receiving a service code corresponding to the specific service transmitted in response to the service login request from the authentication server;
When the service code is received, the service code output unit outputs the received service code in a predetermined form that can be input to a user authentication device. The user authentication device is output by the authentication server. When receiving the input of the service code that is associated with the user and output by the terminal device, the input service code is transmitted to the authentication server without transmitting fixed user authentication data. ,
An authentication program characterized by
In an authentication program executed in a user authentication device associated with the user by an authentication server that determines whether or not to log in a specific service for the user,
A computer in the user authentication device;
Function as an authentication processing unit,
The authentication processing unit
(A) receiving in a predetermined form an input of a service code received from the authentication server and output in a predetermined form by a terminal device operated by the user and receiving data of the specific service;
(B) Upon receiving the input of the service code output by the terminal device, the input service code is transmitted to the authentication server without transmitting fixed user authentication data, and the service code is transmitted. When the device authentication of the original user authentication device is executed and the device authentication of the user authentication device is successful, the identification specified by the received service code for the user associated with the user authentication device Allow service login,
An authentication program characterized by