JP7276737B2 - Identity verification system and identity verification method - Google Patents

Description

The present invention relates generally to identity authentication.

Personal authentication technology using a one-time password (hereinafter referred to as OTP) is known. "OTP" is a character string (generally a random number) that can be used only once. A "character string" is composed of multiple (or single) characters, and each character may be either alphabetic, numeric, or other code. Also, typically, an OTP is a character string whose upper limit of the number of times it can be used is 1, but as used herein, "OTP" is an extended character string whose upper limit of the number of times it can be used is 2 or more. It may be an extended OTP with an upper limit on the usable period instead of or in addition to the number of times it can be used.

For example, the technology disclosed in Patent Document 1 is known as a person authentication technology using OTP.

Japanese Patent Application Laid-Open No. 2011-215940

A WEB function is used to provide services via the Internet. Generally, the WEB function is to send a request specifying a URL (Uniform Resource Locator) from the WEB browser of the user terminal to the server system, and the server system displays an HTML (Hypertext Markup Language) file according to the URL on the WEB browser of the user terminal. It is a function that allows

User convenience will be improved if the OTP required for personal authentication can be provided using the WEB function. However, there is no method for safely providing the OTP to the user using the WEB function. This is because both the user and the communication path cannot be correctly confirmed.

Therefore, two-step authentication is generally adopted as a personal authentication method using OTP. In two-factor authentication, the OTP can be conveyed to the user by email, SMS (Short Message Service), dongle (hardware token), telephone voice, or application (for example, as an application separate from the browser or service application). OTP issuing application) is used.

However, two-factor authentication does not prevent phishing scams. That is, if a malicious third party acquires the authentication information (for example, ID and password) entered by the user through a fake WEB screen and also acquires the OTP, the malicious third party can impersonate the user.

A server system communicating with a user terminal having a WEB browser generates a token and sends the generated token stored by the user terminal via HTTP. A server system associates a user with the generated token and associates an issued OTP with the generated user-associated token. The server system transmits a link notification addressed to the user describing an OTP link, which is a link having a character string based on the generated token. When the token on which the character string of the OTP link specified in the issued link notification is based matches the stored token, the server system transmits an HTTP request following the OTP link from the user terminal. Receive and send an OTP HTTP response to the user terminal. It is a requirement for successful user authentication that the OTP entered by the user matches the OTP associated with the token with which the user is associated.

According to the present invention, OTP can be safely provided by the WEB function.

It is a figure which shows the system configuration|structure which concerns on one Embodiment of this invention. It is part of the authentication process performed in one embodiment of the present invention. It is the remainder of the authentication process performed in one embodiment of the present invention.

In the following description, an "interface device" may be one or more interface devices. The one or more interface devices may be at least one of the following:
- One or more I/O (Input/Output) interface devices. An I/O (Input/Output) interface device is an interface device for at least one of an I/O device and a remote display computer. The I/O interface device to the display computer may be a communications interface device. The at least one I/O device may be any of a user interface device, eg, an input device such as a keyboard and pointing device, and an output device such as a display device.
- One or more communication interface devices. The one or more communication interface devices may be one or more of the same type of communication interface device (e.g., one or more NICs (Network Interface Cards)) or two or more different types of communication interface devices (e.g., NIC and It may be an HBA (Host Bus Adapter).

Also, in the following description, "memory" may be one or more memory devices, typically a main memory device. At least one memory device in the memory may be a volatile memory device or a non-volatile memory device.

Also, in the following description, a "persistent storage device" is one or more persistent storage devices. A permanent storage device is typically a non-volatile storage device (for example, an auxiliary storage device), and specifically, for example, an HDD (Hard Disk Drive) or SSD (Solid State Drive).

Also, in the following description, "storage" may be at least memory of memory and persistent storage.

Also, in the following description, a "processor" is one or more processor devices. The at least one processor device is typically a microprocessor device such as a CPU (Central Processing Unit), but may be another type of processor device such as a GPU (Graphics Processing Unit). At least one processor device may be single-core or multi-core. At least one processor device may be a processor core. At least one processor device may be a broadly defined processor device such as a hardware circuit (for example, FPGA (Field-Programmable Gate Array) or ASIC (Application Specific Integrated Circuit)) that performs part or all of processing.

In addition, in the following description, the function may be described using the expression “yyy part”, but the function may be realized by executing one or more computer programs by a processor, or may be realized by executing one or more computer programs. It may be realized by the above hardware circuits (for example, FPGA or ASIC), or may be realized by a combination thereof. When a function is realized by executing a program by a processor, the defined processing is performed while appropriately using a storage device and/or an interface device, etc., so the function may be at least part of the processor. good. A process described with a function as the subject may be a process performed by a processor or a device having the processor. Programs may be installed from program sources. The program source may be, for example, a program distribution computer or a computer-readable storage medium (eg, non-transitory storage medium). The description of each function is an example, and multiple functions may be combined into one function, or one function may be divided into multiple functions.

An embodiment of the present invention will be described in detail below with reference to the drawings. In the following embodiments, login authentication is adopted as an example of personal authentication, login information such as an ID and password is adopted as authentication information for personal authentication, and a WEB page for inputting authentication information for personal authentication A login page is adopted in which an ID and password are entered.

FIG. 1 is a diagram showing a system configuration according to one embodiment of the present invention.

Communication is performed between the user terminal 150 and the server system 100 via a communication network such as the Internet.

A user terminal 150 is an information processing terminal such as a personal computer or a smart phone. The user terminal 150 has an IF device (interface device) 160, a storage device 180, and a processor 190 connected thereto. The user terminal 150 also has a UI (User Interface) device 170 connected to the IF device 160 .

The IF device 160 communicates with the later-described IF device 110 of the server system 100 and the UI device 170 .

The UI device 170 is at least one of an input device such as a keyboard or mouse and a display device such as a liquid crystal display. The UI device 170 may be a device such as a touch panel in which an input device and a display device are integrated.

The storage device 180 stores the key U. Key U is one or more user keys. User keys are used to encrypt and decrypt information. Hereinafter, the n-th user key is expressed as "K _Un " (n is a natural number). A different user key may be used for each object of multiple encrypted communication (for example, an argument as an example of information), or a common user key may be used regardless of the object of multiple encrypted communication.

A processor 190 functions as a web browser 191 , a token management section 192 and an encryption section 193 . These functions 191 to 193 are realized by the processor 190 executing at least part of one or more computer programs including or excluding the OS (Operating System) of the user terminal 150 . For example, at least one of the token management unit 192 and the encryption unit 193 may be a function prepared in advance in the user terminal 150 (for example, a plug-in of the WEB browser 191), or a JAVA Embedded functions (functions obtained from web pages) such as scripts (“JAVA” is a registered trademark) may be used. A description of these functions 191-193 is provided in the description of the authentication process represented by FIGS.

The server system 100 may be a physical system composed of one or more physical computers having computational resources such as an IF device 110, a storage device 120, and a processor 130 connected thereto. It may be a logical system based on a system (for example, a system as a cloud computing service).

IF device 110 communicates with IF device 160 of user terminal 150 .

A storage device 120 stores a key S and a management DB (database) 121 .

The key S is one or more server keys respectively corresponding to one or more user keys. Server keys are used to encrypt and decrypt information. A different server key may be used for each object of multiple encrypted communication (for example, an argument as an example of information), or a common server key may be used regardless of the object of multiple encrypted communication. In this embodiment, it is assumed that the user key and the server key have a one-to-one correspondence. Hereinafter, the n-th server key corresponding to the n-th user key K _Un is denoted as "K _Sn ". Which user key and which server key are used in which multiplex encrypted communication may be determined in advance, or the user key and server key used may be arbitrary regardless of which multiplexed encrypted communication. .

The management DB 121 is an example of management information and includes information for each user. For example, for each user, the user's information includes authentication information, such as the user's ID and password. Also, for each user, the token and OTP are added to the user's information as appropriate. Note that the user's authentication information may include other types of information such as user's biometric information instead of or in addition to at least one of the ID and password.

Processor 130 functions as token manager 131 , WEB-IF section 132 , encryption section 133 , OTP manager 134 and authentication section 135 . These functions 131 to 135 are implemented by the processor 130 executing at least part of one or more computer programs including or excluding the OS of the server system 100 . Also, the description of these functions 131 to 135 will be made in the description of the authentication process represented by FIGS. 2 and 3. FIG.

2 and 3 illustrate the authentication process performed in one embodiment of the invention.

At S<b>201 , the WEB browser 191 of the user terminal 150 transmits an HTTP request to the server system 100 . The "HTTP request" referred to here is a request specifying the URL of the login page, but instead of such a request, an HTTP request specifying the URL of a web page other than the login page may be employed. . If the server system 100 identifies in response to this HTTP request that the user's login authentication has not been completed, the HTTP response of the login page may be provided to the user terminal 150 .

S202: The server system 100 receives the HTTP request sent in S201 (or the HTTP request sent by redirection). In response to the HTTP request, the token management unit 131 of the server system 100 generates a token (hereinafter referred to as token A) and temporarily stores it in the storage device 120, for example. Token A is, for example, a character string as a random number. The WEB-IF unit 132 of the server system 100 provides the user terminal 150 with the HTTP response of the login page associated with (for example, embedded in) the token A.

S203: The WEB browser 191 of the user terminal 150 displays the login page from the server system 100, and the token management section 192 of the user terminal 150 saves the token A associated with the login page. Token A may be stored in storage device 180 (ie, local storage), but may alternatively or additionally be in session storage.

S204: The WEB browser 191 of the user terminal 150 accepts the input of the ID and PW (password) for the login page.

S205: For example, when the login button on the login page is pressed in S204, the WEB browser 191 of the user terminal 150 encrypts an argument (hereinafter, argument P) that is information including the entered ID and password. 193, and the encryption unit 193 encrypts the argument P using the first user key _KU1 and the stored token A (encryption password). Argument P may include information other than ID and password (for example, timestamp). An argument encrypted using the first user key K _U1 is denoted as “argument E _U1 ”.

S206: The WEB browser 191 of the user terminal 150 transmits an HTTP request (for example, a personal authentication request) associated with the argument _EU1 .

S207: The server system 100 (for example, the WEB-IF unit 132) receives the HTTP request associated with the argument E _U1 , and the encryption unit 133 of the server system 100 encrypts the temporarily stored token A (encryption password). and the first server key _KS1 to encrypt the argument _EU1 . An argument encrypted using the first user key K _U1 and the first server key K _S1 , that is, an argument multi-encrypted is denoted as "argument E _U1S1 ". The server system 100 (for example, the WEB-IF unit 132) transmits the argument _EU1S1 to the user terminal 150.

S208: The argument _EU1S1 is received by the user terminal 150 (for example, the WEB browser 191), and the encryption unit 193 of the user terminal 150 converts the argument _EU1S1 into the stored token A (decryption password) and the first user Decrypt using the key _KU1 . As a result, the argument E _S1 in which the argument P is encrypted with the first server key K _S1 is obtained. The user terminal 150 (for example, the WEB browser 191) transmits the argument _ES1 to the server system 100. FIG.

S209: The server system 100 (for example, the WEB-IF unit 132) receives the argument E _S1 , and the encryption unit 133 of the server system 100 converts the temporarily stored token A (decryption password) and the first server key K Decode the argument E _S1 using _S1 . As a result, the argument P is obtained, and therefore the ID and password can be obtained from the argument P.

Multiple encryption communication (communication between the WEB browser 191 of the user terminal 150 and the WEB-IF unit 132 of the server system 100) in S206 to S209 is performed using HTTP. That is, the argument E _U1 , the argument E _U1S1 and the argument E _S1 are transmitted and received by HTTP. Also, in this embodiment, Vernam cipher is used for encryption using a key and an encryption password, and for decryption using a key and a decryption password. Techniques other than the Vernam cipher may be employed for encryption and decryption.

S210: The authentication unit 135 of the server system 100 determines whether information including an ID and password matching the ID and password obtained from the argument P exists in the management DB 121 . If the result of this determination is false (S210: NO), the authentication unit 135 performs error processing (for example, sending a message to the user terminal 150 indicating that the ID or password should be entered again). If the result of this determination is true (S210: YES), the process proceeds to S211 in FIG.

S211: The token management unit 192 of the server system 100 includes the temporarily stored token A in the user information (information in the management DB 121) corresponding to the ID and password of S210: YES. That is, the token management unit 192 associates the token A with the user. The WEB-IF unit 132 of the server system 100 provides the user terminal 150 with an OTP input page, which is a WEB page for OTP input with which the token A is associated (eg embedded). The OTP input page may be provided as an HTTP response to the HTTP request sent at S206.

S<b>212 : The WEB browser 191 of the user terminal 150 displays the OTP input page from the server system 100 . At this stage, the token management unit 192 of the user terminal 150 may determine whether or not a token matching the stored token A is associated with the OTP input page. If the result of this determination is false, the user terminal 150 (for example, the WEB browser 191) may perform error processing (for example, display a warning message indicating that the page is invalid).

S213: In parallel with S211, the OTP management unit 134 of the server system 100 transmits a URL notification to the user whose ID and password have been authenticated in S210. "URL notification" means a notification (eg, e-mail, or SMS message). In this embodiment, the OTP-URL contains a string as an argument that can be decrypted using the first user key K _U1 and the token A (ie argument E _U1 ). Argument _EU1 is an argument associated with the request sent to server system 100 at S206.

S214: User terminal 150 (e.g., mail application or SMS application (not shown)) displays the URL notification from server system 100 and accepts a user operation to specify the URL described in the notification.

S215: The encryption unit 193 of the user terminal 150 decrypts the character string in the specified URL (the character string as the argument _EU1 ) using the first user key _KU1 and the saved token A. .

S216: The token management unit 192 of the user terminal 150 determines whether or not the token obtained by the decryption in S215 matches the token A stored above. If the result of this determination is false, the user terminal 150 (for example, the WEB browser 191) may perform error processing (for example, displaying a message to start over from entering the ID and password). If the result of this determination is true (S216: YES), the process proceeds to S217.

S217: The WEB browser 191 of the user terminal 150 transmits an HTTP request specifying an OTP-URL (a request for an OTP display page, which is a WEB page displaying the OTP).

S218: The server system 100 (for example, the WEB-IF unit 132) receives the request specifying the OTP-URL, the OTP management unit 134 of the server system 100 issues the OTP, and the OTP is sent to the ID and password in S210. Associate with information (information in the management DB 121) corresponding to the authenticated user. That is, the OTP management unit 134 associates the issued OTP with the token associated with the user. Note that the OTP may be issued at an arbitrary timing after S210: YES, instead of when an HTTP request specifying an OTP-URL is received. Also, the OTP may be issued by a system external to the server system 100 .

S219: The following multiple encryption communication is performed. The target of this multiple cryptographic communication is OTP. Note that the OTP may be transmitted to the user terminal 150 without multiple encryption.
(X1) The encryption unit 133 of the server system 100 encrypts the issued OTP using the token A (encryption password) and the second server key _KS2 . This encrypted OTP is denoted as "OTP-E _S2 ". Also, for example, if there is only one server key in the key S, the first server key _KS1 and the second server key _KS2 may be the same key. The server system 100 (for example, the WEB-IF unit 132) transmits the OTP-E _S2 to the user terminal 150.
(X2) The user terminal 150 (for example, the WEB browser 191) receives the OTP-E _S2 , and the encryption unit 193 of the user terminal 150 encrypts the stored token A (encryption password) and the second server key. Encrypt OTP-E _S2 with a second user key K _U2 corresponding to K _S2 . The OTP encrypted using the second server key K _S2 and the second user key K _U2 , that is, the multiple encrypted OTP is denoted as "OTP-E _S2U2 ". User terminal 150 (for example, WEB browser 191) transmits OTP-E _S2U2 to server system 100. FIG.
(X3) Server system 100 (for example, WEB-IF unit 132) receives OTP-E _S2U2 , and encryption unit 133 of server system 100 encrypts OTP-E _S2U2 with token A (decryption password) and second is decrypted using the server key _KS2 of . As a result, an OTP-E _U2 in which the OTP is encrypted with the second user key K _U2 is obtained. The server system 100 (for example, the WEB-IF unit 132) transmits the OTP- _EU2 to the user terminal 150.
(X4) User terminal 150 (for example, WEB browser 191) receives OTP-E _U2 , and encryption unit 193 of user terminal 150 encrypts token A (decryption password) stored above and second user key K Decode OTP-E _U2 using _U2 . The OTP is thus obtained.

Multiple encryption communication (communication between the WEB browser 191 of the user terminal 150 and the WEB-IF section 132 of the server system 100) relating to (X1) to (X4) is performed using HTTP. That is, transmission and reception of OTP-E _S2 , OTP-E _S2U2 and OTP-E _U2 are performed by HTTP.

S220: The WEB browser 191 of the user terminal 150 displays the OTP from the server system 100 (for example, the OTP decrypted by (X4)).

S221: The WEB browser 191 of the user terminal 150 accepts OTP input for the OTP input page.

S222: For example, when the login button on the OTP input page is pressed in S221, the WEB browser 191 of the user terminal 150 transmits an HTTP request. The request specifies (token/ID) _U3 . “(Token/ID) _U3 ” is token A and ID (user ID entered for login) encrypted using OTP (encryption password) and third user key K _U3 . be. In this embodiment, token A and ID are targets of multiple cryptographic communication. Specifically, the following are performed. The third user key _KU3 may be the same user key as the first user key _KU1 or the second user key _KU2 , or may be a different user key.
(Y1) The server system 100 (for example, the WEB-IF unit 132) receives (token/ID) _U3 , and the encryption unit 133 of the server system 100 converts (token/ID) _U3 to the issued OTP ( decryption password) and the third server key K _S3 (server key corresponding to the third user key K _U3 ). A token/ID encrypted using the third user key K _U3 and the third server key K _S3 , that is, a multiple-encrypted token/ID is denoted as "(token/ID) _U3S3 ". The server system 100 (for example, the WEB-IF unit 132 ) transmits (token/ID) _U3S3 to the user terminal 150 .
(Y2) The user terminal 150 (for example, the WEB browser 191) receives (token/ID) _U3S3 , and the encryption unit 193 of the user terminal 150 converts the saved OTP (decryption password) and the third user key Decrypt U3S3 using K _U3 and (Token/ID) _U3S3 . As a result, (token/ID) _S3 in which the token/ID is encrypted with the third server key K _S3 is obtained. User terminal 150 (for example, WEB browser 191 ) transmits (token/ID) _S<b>3 to server system 100 .
(Y3) The server system 100 (for example, the WEB-IF unit 132) receives the (token/ID) _S3 , and the encryption unit 133 of the server system 100 encrypts the issued OTP (decryption password) and the third Decrypt (token/ID) _S3 using server key K _S3 . This acquires the token/ID.

Multiple encryption communication (communication between the WEB browser 191 of the user terminal 150 and the WEB-IF unit 132 of the server system 100) relating to (Y1) to (Y3) is performed using HTTP. That is, transmission and reception of (token/ID) _U3 , (token/ID) _U3S3 and (token/ID) _S3 are performed by HTTP.

S223: The authentication unit 135 of the server system 100 refers to the management DB 121 and determines whether the token/ID matches the token A and the ID of the user (the user whose ID and password were authenticated in S210). If the result of this determination is false (S223: NO), the authentication unit 135 performs error processing (for example, sending a message to the user terminal 150 indicating that the ID or password should be entered again). If the result of this determination is true (S223: YES), the process proceeds to S224.

S224: The authentication unit 135 of the server system 100 permits the user's login (successful authentication).

Considering this embodiment, for example, the following problems can be expected to be avoided.

First, there is a case where the login page is a fake page and a third party tries to impersonate the user by using the ID and password entered on the fake page. However, a token mismatch is detected at S216 when the OTP-URL in the URL notification is specified by a third party. This is because Token A (the correct token) does not exist in the third party's user terminal. Therefore, S216: NO (error), and the process does not proceed. As a result, the problem in this case can be avoided.

Second, there may be cases where the URL notification is a bogus notification. However, a token mismatch is detected at S216 when the OTP-URL in the URL notification is specified by the user. This is because the character string of the OTP-URL is not based on the token A. Therefore, S216: NO (error), and the process does not proceed.

Third, there is a possibility that the URL notification is stolen by a third party. However, the problem in this case can be avoided by one of the following methods (3-1) and (3-2).
(3-1) Token mismatch is detected in S216 when the OTP-URL in the URL notification is specified by a third party. This is because the same token A as the token A on which the character string of the OTP-URL is based is not saved in the third party's user terminal. Therefore, S216: NO (error), and the process does not proceed.
(3-2) The OTP to be transmitted in S219 is the object of multiple encrypted communication using the token A as the encryption password. Token A is not stored on the third party's user terminal. Therefore, decryption of the multiple-encrypted OTP fails.

Fourth, the OTP input page may be a fake page, and a third party may use the OTP entered on the fake page to impersonate the user. However, the problem in this case can be avoided by one of the following methods (4-1) and (4-2).
(4-1) The entered OTP is not associated with a third party in the server system 100; Therefore, S223: NO (error), that is, personal authentication fails.
(4-2) The input OTP is the target of multiple encrypted communication in the server system 100 using the token A as the decryption password. However, token A is not stored in the third party's user terminal. Therefore, the decryption fails at the server system 100 .

The above description can be summarized, for example, as follows. The following summary may include supplements and variations of the above description.

The personal authentication system includes a token management unit 131, a WEB-IF unit 132, and an OTP management unit 134 provided in the server system 100. FIG. The personal authentication system also includes a token management unit 192 provided in the user terminal 150 having the WEB browser 191 . The token management unit 131 of the server system 100 generates a token A. The WEB-IF unit 132 of the server system 100 transmits the generated token A to the user terminal 150 by HTTP. Token management unit 192 of user terminal 150 stores token A from server system 100 . The OTP management unit 134 of the server system 100 associates the issued OTP required for user authentication with the token A generated in the server system 100 and associated with the user. The OTP management unit 134 of the server system 100 transmits a user-addressed link notification (for example, the URL notification described above) describing an OTP link that is a link having a character string based on the token A. When the OTP link described in the issued link notification is specified, the token management unit 192 of the user terminal 150 stores the token on which the character string of the specified OTP link is based and the saved OTP link. It is determined whether or not the token A matches. When the determination result is affirmative, the user terminal 150 (WEB browser 191) transmits an HTTP request following the OTP link. When the server system 100 receives an HTTP request following the OTP link, the WEB-IF unit 132 of the server system 100 transmits an HTTP response of OTP to the user terminal 150, and the WEB browser 191 of the user terminal 150 displays the OTP. do. A requirement for successful user authentication is that the OTP entered by the user matches the OTP associated with the token with which the user is associated.

As a result, the OTP can be safely provided by the WEB function, and even if the OTP is notified by the WEB function, both the user and the communication path can be correctly confirmed. Specifically, the token generated in the server system 100 is transmitted to the user terminal 150 via HTTP and stored in the user terminal 150, and in the subsequent communication, if a token mismatch is detected, the process proceeds. do not have.

In the above, "character string based on token A" means a character string including token A and a character string as information encrypted using token A as an encryption password (this character string is token A may or may not contain ).

Further, "whether or not the token on which the character string of the specified OTP link is based matches the stored token A" may be, for example, any of the following.
- Whether or not the token obtained from the character string possessed by the specified OTP link matches the stored token A.
• Whether or not the character string possessed by the specified OTP link can be successfully decrypted using the stored token A as the decryption password (for example, decryption according to the Vernam cipher).

Token A may be generated and transmitted in a state in which the user is unspecified, or in a state in which the user is specified (for example, the user of the user terminal connected to the company network is specified). state). In addition, the “specified user” may be a user whose authentication information such as ID and password has not been authenticated but is specified as belonging to a specific range, or a user whose authentication information such as ID and password has not been authenticated. It may be a user whose authentication information has been authenticated.

The WEB-IF unit 132 of the server system 100 has a first WEB page (for example, a login page) that is a WEB page for accepting input of information for personal authentication, and a second WEB page that is a WEB page for accepting input of OTP. (eg OTP entry page). At least one web page of the first web page and the second web page has the token A generated. In this way, since the token A is transmitted together with the WEB page (for example, embedded in the WEB page), communication only for transmitting the token A is unnecessary. In the embodiment, the first transmission of token A is transmission of a login page in which token A is embedded, but instead of that, transmission of an OTP input page in which token A is embedded after S210: YES may be transmitted. .

A server system 100 has an encryption unit 133 and a server key. A user terminal 150 has an encryption unit 193 and a user key. Information transmitted from the server system 100 to the user terminal 150 (typically information associated with an HTTP response from the server system 100 to the user terminal 150) and information transmitted from the user terminal 150 to the server system 100 (typically Specifically, at least one of (information associated with an HTTP request from the user terminal 150 to the server system 100) is subject to multiple encryption. Therefore, man-in-the-middle attacks can be prevented. For example:

<Multiple Encrypted Communication of Information Transmitted from Server System 100 to User Terminal 150>

The encryption unit 133 of the server system 100 encrypts target information, which is information transmitted to the user terminal 150 via HTTP, using the server key and the server-side encryption password that is the generated token A. . The WEB-IF unit 132 of the server system 100 transmits the first encrypted information, which is the encrypted target information, to the user terminal 150 by HTTP. The encryption unit 193 of the user terminal 150 encrypts the first encrypted information from the server system 100 using the user key and the user side encryption password which is the stored token A. The WEB browser 191 of the user terminal 150 transmits the second encrypted information, which is the encrypted first encrypted information, to the server system 100 by HTTP. The encryption unit 133 of the server system 100 decrypts the second encrypted information from the user terminal 150 using the server key and the same password as the server-side encryption password. The WEB-IF unit 132 of the server system 100 transmits the first encrypted information, which is the decrypted second encrypted information, to the user terminal 150 by HTTP. The encryption unit 193 of the user terminal 150 decrypts the first encrypted information from the server system 100 using the user key and the same password as the user-side encryption password to obtain the target information. In this manner, man-in-the-middle attacks can be prevented for information transmitted from server system 100 to user terminal 150 . The "target information" referred to in this paragraph is, for example, OTP. As a result, OTP confidential communication is realized.

<Multiple Encrypted Communication of Information Transmitted from User Terminal 150 to Server System 100>

The encryption unit 193 of the user terminal 150 encrypts the target information, which is the information transmitted to the server system 100 by HTTP, with the user key, the user-side encryption password (saved token A and the OTP from the server system 100). and at least one of The WEB browser 191 of the user terminal 150 transmits the first encrypted information, which is the encrypted target information, to the server system 100 by HTTP. The encryption unit 133 of the server system 100 converts the first encrypted information from the user terminal 150 into a server key and a password for server-side encryption (at least one of the generated token A and the issued OTP). ) and The WEB-IF unit 132 of the server system 100 transmits the second encrypted information, which is the encrypted first encrypted information, to the user terminal 150 by HTTP. The encryption unit 193 of the user terminal 150 decrypts the second encrypted information from the server system 100 using the user key and the same password as the user side encryption password. The WEB browser 191 of the user terminal 150 transmits the first encrypted information, which is the decrypted second encrypted information, to the server system 100 by HTTP. The encryption unit 133 of the server system 100 obtains the target information by decrypting the first encrypted information from the user terminal 150 using the server key and the same password as the server-side encryption password. In this manner, man-in-the-middle attacks can be prevented for information transmitted from user terminal 150 to server system 100 . The “target information” referred to in this paragraph is, for example, information input by the user to the WEB page displayed by the WEB browser 191 of the user terminal 150 . This realizes confidential communication of information (for example, authentication information or OTP) input by the user.

In communication between the WEB browser 191 of the user terminal 150 and the WEB-IF unit 132 of the server system 100, the communication protocol is changed from the first HTTP (for example, HTTP or HTTPS) to the second HTTP (referred to as "HTTPM" for convenience). may be changed). For example, this protocol transition may be performed by the WEB-IF unit 132 . Communication according to HTTP is multiple encryption communication. The targets of the multiplex encrypted communication are information sent from the WEB browser 191 of the user terminal 150 to the WEB-IF unit 132 of the server system 100 (for example, arguments of HTTP requests), and information sent from the WEB-IF unit 132 of the server system 100 to the user. It is at least part of the information (for example, the argument of the HTTP response) sent to the WEB browser 191 of the terminal 150 . The multiple encryption is encryption using the server key and the server-side encryption password by the encryption unit 133 of the server system 100, and the user key by the encryption unit 193 of the user terminal 150 and the user-side encryption password. and encryption using Both the server-side encryption password and the user-side encryption password are sent and received between the server system 100 and the user terminal 150 in multiple encryption communication using token A and token A as the encryption password. information (that is, information shared between the user terminal 150 and the server system 100). Multiple encryption communication can be maintained through such protocol conversion.

Although one embodiment of the present invention has been described above, these are examples for explaining the present invention, and are not intended to limit the scope of the present invention to these embodiments. The present invention can also be implemented in various other forms.

For example, the personal authentication system in the above description may be a system external to a service system that provides services other than personal authentication and perform personal authentication on behalf of the service system. It may also be a service system that provides a service to a user who has completed the above.

Also, in the above description, the information provided by HTTP when the URL in the URL notification is specified is OTP, but other types of information may be employed instead of or in addition to OTP. For example, "personal authentication" may be performed without OTP (for example, only with authentication information such as an ID and password), and in communication after successful personal authentication, token issuance, token transmission to the user terminal, Transmission of the URL notification to the user terminal, provision of information to the user terminal by HTTP when the URL in the URL notification is specified, and the like may be performed. Further, in the communication in the service system, the above-described HTTP communication may be always performed from a predetermined stage.

100... Server system, 150... User terminal

Claims (9)

a token management unit, a WEB-IF (interface) unit, and an OTP (one-time password) management unit provided in the server system;
a token management unit provided in a user terminal having a WEB browser,
The token management unit of the server system generates a token,
the WEB-IF unit of the server system transmits the generated token to the user terminal via HTTP;
the token manager of the user terminal stores the token from the server system;
The OTP management unit of the server system associates the issued OTP required for user authentication with the generated token associated with the user,
The OTP management unit of the server system transmits a link notification addressed to the user describing an OTP link that is a link having a character string based on the token,
When the OTP link described in the issued link notification is specified,
determining whether the token management unit of the user terminal matches the token on which the character string of the specified OTP link is based and the stored token;
If the result of the determination is affirmative, the user terminal transmits an HTTP request according to the OTP link;
When the server system receives an HTTP request following the OTP link, the WEB-IF unit of the server system transmits an HTTP response of the OTP to the user terminal, and the WEB browser of the user terminal responds to the OTP to display
a requirement for successful authentication of the user is that the OTP entered by the user matches the OTP associated with the token with which the user is associated;
identity verification system. The WEB-IF unit of the server system provides a first WEB page that is a WEB page for accepting input of information for personal authentication and a second WEB page that is a WEB page for accepting input of OTP. has become
at least one web page of the first web page and the second web page has the generated token;
The person authentication system according to claim 1. the server system having an encryption unit and a server key;
The user terminal has an encryption unit and a user key,
The encryption unit of the server system encrypts target information, which is information transmitted to the user terminal via HTTP, using the server key and the server-side encryption password that is the generated token. , the WEB-IF unit of the server system transmits the first encrypted information, which is the encrypted target information, to the user terminal by HTTP;
The encryption unit of the user terminal encrypts the first encrypted information from the server system using the user key and the user-side encryption password that is the stored token, and the WEB browser of the user terminal transmits the second encrypted information, which is the encrypted first encrypted information, to the server system via HTTP;
The encryption unit of the server system decrypts the second encrypted information from the user terminal using the server key and the same password as the server-side encryption password, and decrypts the second encrypted information from the server system. the WEB-IF unit transmits the first encrypted information, which is the decrypted second encrypted information, to the user terminal via HTTP;
The encryption unit of the user terminal decrypts the first encrypted information from the server system using the user key and the same password as the user-side encryption password, so that the target get information,
The personal authentication system according to claim 1 or 2. the target information is the OTP;
The personal authentication system according to claim 3. the server system having an encryption unit and a server key;
The user terminal has an encryption unit and a user key,
The encryption unit of the user terminal encrypts target information, which is information transmitted to the server system by HTTP, with at least one of the user key, the stored token, and OTP from the server system. and the user side encryption password, and the WEB browser of the user terminal transmits the first encrypted information, which is the encrypted target information, to the server system by HTTP,
wherein the encryption unit of the server system converts the first encrypted information from the user terminal into at least one of the server key, the generated token, and the issued OTP. and a password for side encryption, and the WEB-IF unit of the server system transmits the second encrypted information, which is the encrypted first encrypted information, to the user terminal via HTTP. death,
The encryption unit of the user terminal decrypts the second encrypted information from the server system using the user key and the same password as the user-side encryption password, and decrypts the second encrypted information from the user terminal. the web browser transmits the first encrypted information, which is the decrypted second encrypted information, to the server system via HTTP;
The encryption unit of the server system decrypts the first encrypted information from the user terminal using the server key and the same password as the server-side encryption password, thereby enabling the target get information,
The personal authentication system according to claim 1 or 2. The target information is information input by a user to a WEB page displayed by the WEB browser of the user terminal.
The personal authentication system according to claim 5. the server system having an encryption unit and a server key;
The user terminal has an encryption unit and a user key,
a protocol for communication between the WEB browser of the user terminal and the WEB-IF unit of the server system transitions from the first HTTP to the second HTTP;
The communication according to the second HTTP is multiple encryption communication,
The targets of the multiple encrypted communication are information transmitted from the WEB browser of the user terminal to the WEB-IF section of the server system, and information transmitted from the WEB-IF section of the server system to the WEB browser of the user terminal. is at least part of the transmitted information;
The multiple encryption includes encryption using the server key and server-side encryption password by the encryption unit of the server system, and encryption of the user key and user-side encryption by the encryption unit of the user terminal. and encryption using an encryption password;
Both the server-side encryption password and the user-side encryption password are transmitted and received between the server system and the user terminal in multiple encryption communication using the token and the token as an encryption password. is at least one of the information provided and
The personal authentication system according to any one of claims 1 to 6. A personal authentication method performed by a server system communicating with a user terminal having a web browser,
generate a token,
transmitting the generated token stored by the user terminal to the user terminal via HTTP;
associate a user with the generated token;
associate an issued OTP with the generated token with which the user is associated;
Sending a link notification addressed to the user in which an OTP link, which is a link having a character string based on the generated token, is described;
When the user terminal determines that the token on which the character string of the specified OTP link on the issued link notification is based matches the stored token, the OTP link receive an HTTP request according to and send an HTTP response of said OTP to said user terminal;
a requirement for successful authentication of the user is that the OTP entered by the user matches the OTP associated with the token with which the user is associated;
Identity verification method. A computer program for causing a user terminal having a WEB browser and communicating with the server system according to claim 1 to execute the operation of the token management unit according to claim 1.

Images