JP2015138978A - Authentication system, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an authentication system which has high safety and can be easier to use.SOLUTION: An authentication system includes a plurality of user terminals and an authentication server. A user terminal includes: a first registration unit which generates a public key not including personal information and a secret key corresponding to the public key and transmits registration information including the public key to the authentication server; and a first authentication unit which authenticates, by using the secret key, the user terminal's possession of the secret key corresponding to the public key or generates data required for the authentication to transmit the data. The authentication server includes: a second registration unit for storing received registration information, for each user terminal; and a second authentication unit which authenticates, by using a public key included in the registration information, the user terminal's possession of a secret key corresponding to the public key or generates data required for the authentication to transmit the data.

Description

  The present invention relates to an authentication system and program for executing user authentication online.

  Conventionally, several access control methods for resources on a network in the Internet or an intranet have been proposed. Well-known is basic authentication using an ID and a password (see Non-Patent Document 1). In addition to this, there is a method of performing access control using the IP address of the access source. There is another authentication method using a personal certificate. A well-known authentication method using a personal certificate is a personal electronic certificate service provided by VeriSign (registered trademark) (see Non-Patent Document 2). As an authentication method using a personal certificate, Apache's FakeBasic authentication is known (see Non-Patent Document 3).

“HTTP Authentication: Basic and Digest Access Authentication”, [online], [Search January 10, 2013], Internet <URL: http://tools.ietf.org/html/rfc2617> “Verisign Personal Digital Certificate Class2 Standard-Authenticating Individuals in the Organization”, [online], [Search January 10, 2013], Internet <URL: https://www.verisign.co.jp/personal /class2/index.html> “Fake Basic Authentication”, [online], [searched on January 10, 2013], Internet <URL: http://httpd.apache.org/docs/2.2/mod/mod_ssl.html>

  In the authentication method using ID and password, the server normally manages the value converted from the password by the hash function. If this value is leaked, the password is obtained by attacking this value. Since it can be obtained illegally, there is a problem from the viewpoint of security. In the method of performing access control using the IP address of the access source, there are cases where unauthorized tampering is performed on the IP address of the access source, and there is a problem from the viewpoint of security as in the authentication method using the ID and password.

  Also, the authentication method using a personal certificate has a problem that the identification procedure is complicated and the introduction cost is high.

  Therefore, an object of the present invention is to provide an authentication system that is highly safe and can be used more easily.

  The authentication system of the present invention includes a plurality of user terminals and an authentication server. The user terminal includes a first registration unit and a first authentication unit, and the authentication server includes a second registration unit and a second authentication unit.

  The first registration unit generates a public key not including personal information and a secret key corresponding to the public key, and transmits registration information including the public key to the authentication server. The first authentication unit uses the secret key to authenticate that the terminal has a secret key corresponding to the public key, or generates and transmits data necessary for authentication. The second registration unit stores the received registration information for each user terminal. The second authenticating unit authenticates that the user terminal possesses the private key corresponding to the public key using the public key included in the registration information, or generates and transmits data necessary for the authentication.

  The authentication system of the present invention has high safety and can be used more easily.

1 is a block diagram illustrating an overview of an authentication system according to a first embodiment. FIG. 2 is a block diagram illustrating a configuration of a user terminal and an authentication server according to the first embodiment. 6 is a flowchart illustrating operations of the user terminal and the authentication server according to the first embodiment. The block diagram which shows the detailed structure of the user terminal of Example 1, and an authentication server. 5 is a flowchart illustrating details of operations of the user terminal and the authentication server according to the first embodiment. FIG. 3 is a block diagram illustrating an overview of an authentication system according to a second embodiment. The block diagram which shows the structure of the user terminal of Example 2, and an authentication server. The block diagram which shows the detailed structure of the user terminal of Example 2, and an authentication server. 9 is a flowchart illustrating details of operations of a user terminal and an authentication server according to the second embodiment. FIG. 9 is a block diagram illustrating an outline of an authentication system according to a third embodiment. The block diagram which shows the structure of the user terminal of Example 3, and an authentication server. The block diagram which shows the detailed structure of the user terminal of Example 3, and an authentication server. 10 is a flowchart illustrating details of operations of a user terminal and an authentication server according to the third embodiment. FIG. 9 is a block diagram illustrating an outline of an authentication system according to a fourth embodiment. The block diagram which shows the structure of the user terminal of Example 4, and an authentication server. 10 is a flowchart illustrating operations of a user terminal and an authentication server according to the fourth embodiment. FIG. 10 is a block diagram illustrating an outline of an authentication system according to a fifth embodiment. The block diagram which shows the structure of the user terminal of Example 5, and an authentication server. 10 is a flowchart illustrating operations of a user terminal and an authentication server according to a fifth embodiment.

  Hereinafter, embodiments of the present invention will be described in detail. In addition, the same number is attached | subjected to the structure part which has the same function, and duplication description is abbreviate | omitted.

  Hereinafter, an outline of the authentication system according to the first embodiment will be described with reference to FIGS. 1, 2, and 3. FIG. 1 is a block diagram illustrating an outline of an authentication system 1 according to the present embodiment. FIG. 2 is a block diagram illustrating configurations of the user terminal 11-k and the authentication server 12 according to the present embodiment. FIG. 3 is a flowchart showing the operation of the user terminal 11-k and the authentication server 12 of this embodiment.

  As shown in FIG. 1, the authentication system 1 of the present embodiment includes a plurality of user terminals 11-1, 11-2,..., 11 -k,. However, n is an integer of 2 or more. k is an integer of 1 to n. Note that n user terminals 11-1, 11-2,..., 11-k,..., 11-n and the authentication server 12 are connected to each other via the NW 9 so as to communicate with each other. Since the n user terminals 11-1, 11-2,..., 11-k,..., 11-n all have the same function, the user terminal 11-k will be described below as a representative of these. As illustrated in FIG. 2, the user terminal 11-k includes a first registration unit 111 and a first authentication unit 112, and the authentication server 12 includes a second registration unit 121 and a second authentication unit 122. As shown in FIG. 3, first, the first registration unit 111 of the user terminal 11-k generates a public key that does not include personal information and a secret key that corresponds to the public key, and stores registration information that includes the public key. It transmits to the authentication server (S111). Next, the second registration unit 121 of the authentication server 12 stores the received registration information for each user terminal (S121). The above is the user registration operation. Next, the first authentication unit 112 of the user terminal 11-k uses the secret key to authenticate that the own terminal possesses the secret key corresponding to the public key, or generates data necessary for the authentication. Transmit (S112). Next, the second authentication unit 122 of the authentication server 12 authenticates that the user terminal possesses the private key corresponding to the public key using the public key included in the registration information, or data necessary for the authentication. Generate and transmit (S122). The above is the user authentication operation.

  Hereinafter, the details of the authentication system 1 according to the present embodiment will be described with reference to FIGS. 4 and 5. FIG. 4 is a block diagram illustrating a detailed configuration of the user terminal 11-k and the authentication server 12 according to the present embodiment. FIG. 5 is a flowchart illustrating details of operations of the user terminal 11-k and the authentication server 12 according to the present embodiment.

  As shown in FIG. 4, the first registration unit 111 includes an identifier acquisition unit 1111, a key generation unit 1112, a secret key storage unit 1113, and a registration information transmission unit 1114. The first authentication unit 112 includes an identifier transmission unit 1121, a ciphertext reception unit 1122, and a ciphertext decryption unit 1123. The second registration unit 121 includes a registration information reception unit 1211 and a registration information storage unit 1212. The second authentication unit 122 includes an identifier reception unit 1221, a public key acquisition unit 1222, a session key generation unit 1223, a ciphertext generation unit 1224, and a ciphertext transmission unit 1225.

As shown in FIG. 5, first, the identifier acquisition unit 1111 of the first registration unit 111 acquires an identifier ID _k that is information for identifying the terminal itself (S1111). As the identifier, for example, a character string uniquely set by the user can be used. Further, the user's mail address can be used as an identifier. An identifier may be assigned from the system. Other than this, for example, the public key itself can be used as an identifier as in Example 3 described later. Next, the key generation unit 1112 generates a public key PK _k not including personal information and a secret key SK _k corresponding to the public key PK _k (S1112). Next, the secret key storage unit 1113 stores the secret key SK _k (S1113). Next, the registration information transmission unit 1114 transmits the set of the identifier ID _k and the public key PK _{k to} the authentication server 12 as registration information (S1114).

  Next, the registration information receiving unit 1211 of the second registration unit 121 receives the registration information (S1211). The registration information storage unit 1212 stores the received registration information (S1212). The above is the details of the user registration operation.

Next, the identifier transmission unit 1121 of the first authentication unit 112 transmits the identifier ID _k to the authentication server 12 at the start of authentication (S1121).

Next, the identifier receiving unit 1221 of the second authentication unit 122 receives the identifier ID _k (S1221). Next, the public key acquisition unit 1222 acquires the public key PK _k corresponding to the received identifier ID _k from the registration information storage unit 1212 (S1222). Next, the session key generation unit 1223 generates a session key K (S1223). Next, the ciphertext generation unit 1224 encrypts the session key K using the public key PK _k corresponding to the received identifier ID _k , and generates a ciphertext C = EncPK (K) (S1224). Next, the ciphertext transmission unit 1225 transmits the ciphertext C = EncPK (K) to the user terminal 11-k (S1225).

Next, the ciphertext receiving unit 1122 of the first authentication unit 112 receives the ciphertext from the authentication server 12 (S1122). Next, the ciphertext decryption unit 1123 decrypts the ciphertext C using the secret key SK _k to obtain the session key K (S1123). If communication is possible using the session key K, authentication is considered successful. Thereafter, the user terminal 11-k and the authentication server 12 can communicate safely using the session key K. The above is the details of the user authentication operation.

  In the authentication system 1 according to the present embodiment, the first registration unit 111 transmits registration information including a public key at the time of user registration, and the identifier transmission unit 1122 transmits an identifier at the time of user authentication. Therefore, only a public key, an identifier, or the like that has no safety problem even if it is leaked is transmitted to the authentication server 12. On the other hand, the secret key to be concealed is safely concealed in the secret key storage unit 1113 of the user terminal 11-k. Therefore, even if communication is intercepted or registration information managed by the authentication server 12 is leaked, no security problem occurs. Further, since the session key K is encrypted and transmitted to the user terminal 11-k, it is possible to prevent eavesdropping by a third party during communication. In these respects, the present authentication system is superior to Basic authentication using an ID and a password. In addition, since the public key and identifier used in the authentication system 1 of the present embodiment do not include personal information, complicated procedures such as prior identity verification procedures are not required. Therefore, the user can easily use this authentication system. In addition, in the conventional access control method using a personal certificate, it is necessary to correctly manage the certificate revocation list when the terminal access is not permitted. Since the server 12 only needs to change the association information between the resource and the public key, management is not time-consuming and immediate. In these respects, the present authentication system is superior to an authentication method using a personal certificate.

  Many of today's online services that require authentication are sufficient without having to prove their real name or affiliation. In such a service, the function necessary for the authentication is only “confirm that the user has the secret information corresponding to the ID given at the first registration”. The point is that the authentication system 1 of the present embodiment has successfully removed the extra cost and complexity required for proof of real name and affiliation by making good use of this condition.

  Hereinafter, an outline of the authentication system according to the second embodiment, which is an authentication method different from the first embodiment, will be described with reference to FIGS. 6 and 7. FIG. 6 is a block diagram showing an outline of the authentication system 2 of the present embodiment. FIG. 7 is a block diagram showing the configuration of the user terminal 21-k and the authentication server 22 of this embodiment.

  As shown in FIG. 6, the authentication system 2 of the present embodiment includes a plurality of user terminals 21-1, 21-2,..., 21-k,. The n user terminals 21-1, 21-2,..., 21-k,..., 21-n and the authentication server 22 are connected to each other via the NW 9 so as to communicate with each other. Since the n user terminals 21-1, 21-2,..., 21-k,..., 21-n all have the same function, the user terminal 21-k will be described below as a representative of these. As illustrated in FIG. 7, the user terminal 21-k includes a first registration unit 111 and a first authentication unit 212, and the authentication server 22 includes a second registration unit 121 and a second authentication unit 222. About the 1st registration part 111 and the 2nd registration part 121, since it is the same as that of Example 1, it abbreviate | omits description about the detail of user registration operation | movement.

  The details of the authentication system 2 of the present embodiment will be described below with reference to FIGS. FIG. 8 is a block diagram illustrating a detailed configuration of the user terminal 21-k and the authentication server 22 according to the present embodiment. FIG. 9 is a flowchart showing details of the operations of the user terminal 21-k and the authentication server 22 of the present embodiment.

  As shown in FIG. 8, the first authentication unit 212 includes an identifier transmission unit 1121, a random number reception unit 2122, a signature generation unit 2123, and a signature transmission unit 2124. The second authentication unit 222 includes an identifier reception unit 1221, a public key acquisition unit 1222, a random number generation unit 2223, a random number transmission unit 2224, a signature reception unit 2225, and a signature verification unit 2226.

As shown in FIG. 9, in the user authentication operation, first, the identifier transmission unit 1121 of the first authentication unit 212 transmits the identifier ID _k to the authentication server at the start of authentication (S1121).

Next, the identifier receiving unit 1221 of the second authentication unit 222 receives the identifier ID _k (S1221). Next, the public key acquisition unit 1222 acquires the public key PK _k corresponding to the received identifier ID _k from the registration information storage unit 1212 (S1222). Next, the random number generation unit 2223 generates a random number r (S2223). Next, the random number transmission unit 2224 transmits the random number r to the user terminal 21-k (S2224).

Next, the random number reception unit 2122 of the first authentication unit 212 receives the random number r from the authentication server 22 (S2122). Next, the signature generation unit 2123 generates a signature σ = sig (SK _k , r) of the random number r using the secret key SK _k (S2123). Next, the signature transmission unit 2124 transmits the signature σ = sig (SK _k , r) to the authentication server 22 (S2124).

Next, the signature receiving unit 2225 of the second authentication unit 222 receives the signature σ from the user terminal 21-k (S2225). Next, the signature verification unit 2226 verifies the signature σ using the public key PK _k corresponding to the received identifier ID _k (S2226).

  As described above, according to the authentication system 2 of the present embodiment, it is possible to realize a simpler authentication with higher security as in the first embodiment by using the signature by the secret key.

  The outline of the authentication system according to the third embodiment will be described below with reference to FIGS. 10 and 11 as an authentication method using a certificate issued by a certificate authority instead of the identification information described above. FIG. 10 is a block diagram showing an outline of the authentication system 3 of the present embodiment. FIG. 11 is a block diagram illustrating the configuration of the user terminal 31-k and the authentication server 32 according to the present embodiment.

  As shown in FIG. 10, the authentication system 3 of the present embodiment includes a plurality of user terminals 31-1, 31-2, ..., 31-k, ..., 31-n, an authentication server 32, and an authentication station 33. Including. Note that the n user terminals 31-1, 31-2,..., 31-k,..., 31-n, the authentication server 32, and the authentication station 33 are connected to each other via the NW 9 so as to communicate with each other. Since the n user terminals 31-1, 31-2, ..., 31-k, ..., 31-n all have the same function, the user terminal 31-k will be described below as a representative of these. As illustrated in FIG. 11, the user terminal 31-k includes a first registration unit 311 and a first authentication unit 312, and the authentication server 32 includes a second registration unit 321 and a second authentication unit 322.

  Hereinafter, the details of the authentication system 3 according to the present embodiment will be described with reference to FIGS. 12 and 13. FIG. 12 is a block diagram illustrating a detailed configuration of the user terminal 31-k and the authentication server 32 according to the present embodiment. FIG. 13 is a flowchart illustrating details of operations of the user terminal 31-k and the authentication server 32 according to the present embodiment.

  As illustrated in FIG. 12, the first registration unit 311 includes a key generation unit 1112, a secret key storage unit 1113, a registration information transmission unit 3114, a certificate reception unit 3115, and a certificate storage unit 3116. The first authentication unit 312 includes a certificate transmission unit 3121, a ciphertext reception unit 1122, and a ciphertext decryption unit 1123. The second registration unit 321 includes a registration information reception unit 3211, a certificate signature request generation unit 3212, a certificate signature request transmission unit 3213, a certificate reception unit 3214, and a public key-certificate storage unit 3215. The second authentication unit 322 includes a certificate reception unit 3221, a public key acquisition unit 3222, a session key generation unit 1223, a ciphertext generation unit 1224, and a ciphertext transmission unit 1225. Note that the first authentication unit 312 and the second authentication unit 322 differ only in that a certificate is used instead of the identifier in the first embodiment, and thus the description of the user authentication operation is omitted as appropriate.

Since steps S1112 and S1113 are the same as those in the first embodiment, the description thereof is omitted. Next, the registration information transmission unit 3114 of the first registration unit 311 transmits only the public key PK _k as registration information to the authentication server 32 (S3114). Next, the registration information receiving unit 3211 of the second registration unit 321 receives the public key PK _k as registration information (S3211). Next, the certificate signature request generation unit 3212 generates a certificate signature request CSR as a substitute for personal information that should include the received public key PK _k in the certificate signature request CSR (S3212). Next, the certificate signature request transmission unit 3213 transmits the certificate signature request CSR to the certificate authority 33 (S3213).

Next, the certificate authority 33 receives the certificate signature request CSR (S331). Next, the certificate authority 33 generates a certificate cert _k corresponding to the public key PK _k and transmits it to the authentication server 32 (S332).

Next, the certificate receiving unit 3214 of the second registration unit 321 receives the certificate cert _k corresponding to the public key PK _k from the certificate authority 33 (S3214). Public Key - certificate storage unit 3215 stores a set of certificate cert _k corresponding to the public key PK _k and the public key PK _k received (S3215). The above is the details of the user registration operation.

The certificate receiving unit 3115 of the first registration unit 311 receives the certificate cert _k corresponding to the public key PK _k from the certificate authority 33 (S3115). Next, the certificate storage unit 3116 stores the certificate cert _k (S3116).

In the user authentication operation, as shown in FIG. 13, the certificate transmission unit 3121 of the first authentication unit 312 transmits the certificate cert _k to the authentication server 32 at the start of authentication (S3121).

Next, the certificate reception unit 3221 of the second authentication unit 322 receives the certificate cert _k transmitted from the user terminal 31-k (S3221). Next, the public key acquisition unit 3222 acquires the public key PK _k corresponding to the certificate cert _k transmitted from the user terminal 31-k from the certificate-public key storage unit 3215 (S3222). As described above, this embodiment is different only in that a certificate is used instead of the identifier in the first embodiment. Accordingly, the operation after step S1223 is the same as that of the first embodiment, and thus the description thereof is omitted.

  Note that the authentication system 3 of this embodiment can be implemented by authentication of a Web browser and a Web server. In the case of authentication using a conventional ID password, the user can manually enter an ID and password in the input field of the browser and perform authentication using a protocol such as Basic authentication. On the other hand, in the case of this authentication system, it is not realistic to manually input a public key encryption private key in the input field of the browser. Therefore, this authentication system can be realized by using FakeBasic authentication (Non-patent Document 3), which is a protocol for authenticating a personal certificate. In this case, the authentication server side 32 can perform authentication using a personal certificate by enabling Apache's FakeBasic authentication. The authentication is set to use LDAP. LDAP is a protocol for accessing a directory database in a TCP / IP network such as the Internet or an intranet. In this authentication system, LDAP can be used in the authentication server 32 to register a list of registered user public keys in a database.

  In the authentication system 3 of the present embodiment, the certificate signature request generation unit 3212 is configured to generate a certificate signature request CSR using a public key as a substitute for personal information to be included in the certificate signature request CSR. Even when implemented using a protocol for authenticating a personal certificate such as Fake Basic authentication, there is no complication specific to an authentication method using a personal certificate.

  14, 15, and 16, in addition to the configuration of the first embodiment, the authentication server has a function of transmitting an authentication result notification to another server (service providing server that provides various services). The authentication system 4 according to the fourth embodiment will be described. FIG. 14 is a block diagram showing an outline of the authentication system 4 of the present embodiment. FIG. 15 is a block diagram illustrating configurations of the user terminal 11-k and the authentication server 42 according to the present embodiment. FIG. 16 is a flowchart illustrating operations of the user terminal 11-k and the authentication server 42 according to the present embodiment.

  As shown in FIG. 14, the authentication system 4 according to the present embodiment includes a plurality of user terminals 11-1, 11-2,..., 11 -k, 11 -n, an authentication server 42 and a service providing server 43. Including. User terminals 11-1, 11-2, ..., 11-k, ..., 11-n are the same as those in the first embodiment. Note that the n user terminals 11-1, 11-2, ..., 11-k, ..., 11-n, the authentication server 42, and the service providing server 43 are connected to each other via the NW 9 so as to communicate with each other. . The service providing server 43 transmits an authentication query (authentication request) to the authentication server 42 in response to access from the user terminals 11-1, 11-2,..., 11-k,. This is an operation aimed at causing the authentication server 42 to take over the user authentication operation. For example, the service providing server 43 is a PayTV site, an e-book sales site, a game server, and the like, and performs an authentication operation on a large-scale server such as facebook (registered trademark) and iTunes Store (registered trademark) corresponding to the authentication server 42. There is an example to have you act.

  As illustrated in FIG. 15, the authentication server 42 further includes an authentication result notification unit 423 in addition to the second registration unit 121 and the second authentication unit 122 that are the same as those in the first embodiment. As illustrated in FIG. 16, when receiving the authentication query Q, the authentication result notifying unit 423 receives an authentication result notification (if it is T or F, T) that is a result of authentication with the user terminal 11-k that has performed access. Authentication success, authentication failure if F) is transmitted to the service providing server 43 (S423). The service providing server 43 determines whether the user can access the resource based on the received authentication result notification.

  As described above, according to the authentication system 4 of the present embodiment, the authentication server 42 can authenticate the user terminal 11-k that is the access source instead of the service providing server 43. Therefore, in addition to the effects of the first embodiment. It can be applied to various systems more flexibly.

  Hereinafter, with reference to FIG. 17, FIG. 18, FIG. 19, in addition to the configuration of the first embodiment, the authentication system 5 of the fifth embodiment to which the authentication server has added a function of transmitting an authorization token to the user terminal upon successful authentication. explain. FIG. 17 is a block diagram showing an outline of the authentication system 5 of the present embodiment. FIG. 18 is a block diagram illustrating configurations of the user terminal 51-k and the authentication server 52 according to the present embodiment. FIG. 19 is a flowchart illustrating operations of the user terminal 51-k and the authentication server 52 according to the present embodiment.

  As shown in FIG. 17, the authentication system 5 of this embodiment includes a plurality of user terminals 51-1, 51-2,..., 51-k, 51 -n, an authentication server 52, and a service providing server 53. Including. The n user terminals 51-1, 51-2, ..., 51-k, ..., 51-n, the authentication server 52, and the service providing server 53 are communicably connected to each other via the NW9. Since the n user terminals 51-1, 51-2, ..., 51-k, ..., 51-n all have the same function, the user terminal 51-k will be described below as a representative of these. In this embodiment, for example, the authentication server 52 can be a system server in an entrance / exit management system such as a company, and the service providing server 53 can be a server device in an in-house LAN or a university campus LAN. In this case, authentication is performed when a student or employee enters a laboratory or company, and an authorization token is issued when the authentication is successful. An example of using this authorization token in an in-house LAN or a campus LAN can be assumed. In this case, the permission token can be used, for example, for permission to use the printer, permission for access to the network drive, or the like.

  As illustrated in FIG. 18, the user terminal 51-k further includes a permission token receiving unit 513 in addition to the same first registration unit 111 and first authentication unit 112 as those in the first embodiment. The authentication server 52 further includes a permission token transmission unit 523 in addition to the second registration unit 121 and the second authentication unit 122 that are the same as those in the first embodiment. As illustrated in FIG. 19, the authorization token transmission unit 523 of the authentication server 52 generates an authorization token every time the second authentication unit 122 succeeds in authentication, and transmits the authorization token to the user terminal 51-k that is the authentication partner. (S523). The permission token receiving unit 513 of the user terminal 51-k receives the permission token (S513).

  Thus, according to the authentication system 5 of the present embodiment, since the authentication server 52 issues the authorization token used by the service providing server 53 and the like, in addition to the effects of the first embodiment, more flexibly, It can be applied to various systems.

  The various processes described above are not only executed in time series according to the description, but may also be executed in parallel or individually as required by the processing capability of the apparatus that executes the processes. Needless to say, other modifications are possible without departing from the spirit of the present invention.

  Further, when the above-described configuration is realized by a computer, processing contents of functions that each device should have are described by a program. The processing functions are realized on the computer by executing the program on the computer.

  The program describing the processing contents can be recorded on a computer-readable recording medium. As the computer-readable recording medium, for example, any recording medium such as a magnetic recording device, an optical disk, a magneto-optical recording medium, and a semiconductor memory may be used.

  The program is distributed by selling, transferring, or lending a portable recording medium such as a DVD or CD-ROM in which the program is recorded. Furthermore, the program may be distributed by storing the program in a storage device of the server computer and transferring the program from the server computer to another computer via a network.

  A computer that executes such a program first stores, for example, a program recorded on a portable recording medium or a program transferred from a server computer in its own storage device. When executing the process, the computer reads a program stored in its own recording medium and executes a process according to the read program. As another execution form of the program, the computer may directly read the program from a portable recording medium and execute processing according to the program, and the program is transferred from the server computer to the computer. Each time, the processing according to the received program may be executed sequentially. Also, the program is not transferred from the server computer to the computer, and the above-described processing is executed by a so-called ASP (Application Service Provider) type service that realizes the processing function only by the execution instruction and result acquisition. It is good. Note that the program in this embodiment includes information that is used for processing by an electronic computer and that conforms to the program (data that is not a direct command to the computer but has a property that defines the processing of the computer).

  In this embodiment, the present apparatus is configured by executing a predetermined program on a computer. However, at least a part of these processing contents may be realized by hardware.

Claims (8)

An authentication system including a plurality of user terminals and an authentication server,
The user terminal is
A first registration unit that generates a public key not including personal information and a secret key corresponding to the public key, and transmits registration information including the public key to the authentication server;
A first authentication unit that authenticates that the terminal owns the secret key corresponding to the public key by using the secret key, or generates and transmits data necessary for the authentication;
The authentication server is
A second registration unit for storing the received registration information for each user terminal;
Second authentication for authenticating that the user terminal possesses the secret key corresponding to the public key using the public key included in the registration information, or generating and transmitting data necessary for the authentication Authentication system including a department. The authentication system according to claim 1,
The first registration unit includes:
An identifier acquisition unit that acquires an identifier that is information for identifying the terminal;
A key generation unit that generates a public key not including personal information, and a secret key corresponding to the public key;
A secret key storage unit for storing the secret key;
A registration information transmission unit that transmits the set of the identifier and the public key as the registration information to the authentication server;
The first authentication unit includes:
An identifier transmitter for transmitting the identifier to the authentication server at the start of authentication;
A ciphertext receiving unit that receives ciphertext from the authentication server;
A ciphertext decryption unit that obtains a session key by decrypting the ciphertext using the secret key;
The second registration unit
A registration information receiving unit for receiving the registration information;
A registration information storage unit for storing the received registration information;
The second authentication unit includes:
An identifier receiving unit for receiving the identifier;
A public key acquisition unit for acquiring the public key corresponding to the received identifier from the registration information storage unit;
A session key generation unit for generating the session key;
Using a public key corresponding to the received identifier, a ciphertext generator that encrypts the session key and generates the ciphertext;
An authentication system including a ciphertext transmission unit that transmits the ciphertext to the user terminal. The authentication system according to claim 1,
The first registration unit includes:
An identifier acquisition unit that acquires an identifier that is information for identifying the terminal;
A key generation unit that generates a public key not including personal information, and a secret key corresponding to the public key;
A secret key storage unit for storing the secret key;
A registration information transmission unit that transmits the set of the identifier and the public key as the registration information to the authentication server;
The first authentication unit includes:
An identifier transmitter for transmitting the identifier to the authentication server at the start of authentication;
A random number receiver for receiving a random number from the authentication server;
A signature generation unit that generates a signature of the random number using the secret key;
A signature transmission unit that transmits the signature to the authentication server;
The second registration unit
A registration information receiving unit for receiving the registration information;
A registration information storage unit for storing the received registration information;
The second authentication unit includes:
An identifier receiving unit for receiving the identifier;
A public key acquisition unit that acquires the public key corresponding to the received identifier from the registration information storage unit;
A random number generator for generating the random number;
A random number transmitter for transmitting the random number to the user terminal;
A signature receiver for receiving the signature from the user terminal;
An authentication system including a signature verification unit that verifies the signature using the public key corresponding to the received identifier. The authentication system according to claim 1,
A certificate authority that issues a certificate in response to the certificate signing request;
The first registration unit includes:
A key generation unit that generates a public key not including personal information, and a secret key corresponding to the public key;
A secret key storage unit for storing the secret key;
A registration information transmission unit that transmits the public key as the registration information to the authentication server;
A certificate receiver that receives the certificate corresponding to the public key from the certificate authority;
A certificate storage unit for storing the certificate;
The first authentication unit includes:
A certificate transmission unit that transmits the certificate to the authentication server at the start of authentication;
A ciphertext receiving unit that receives ciphertext from the authentication server;
A ciphertext decryption unit that obtains a session key by decrypting the ciphertext using the secret key;
The second registration unit
A registration information receiving unit that receives the public key as the registration information;
A certificate signing request generating unit for generating the certificate signing request as a substitute for personal information to be included in the certificate signing request with the received public key;
A certificate signing request sending unit for sending the certificate signing request to the certificate authority;
A certificate receiver that receives the certificate corresponding to the public key from the certificate authority;
A public key-certificate storage unit for storing the received public key and a set of the certificate corresponding to the public key;
The second authentication unit includes:
A certificate receiver for receiving the certificate transmitted from the user terminal;
A public key acquisition unit that acquires the public key corresponding to the certificate transmitted from the user terminal from the certificate-public key storage unit;
A session key generation unit for generating the session key;
A ciphertext generating unit that generates the ciphertext by encrypting the session key using the public key corresponding to the certificate transmitted from the user terminal;
An authentication system including a ciphertext transmission unit that transmits the ciphertext. The authentication system according to any one of claims 1 to 4,
A service providing server that transmits an authentication query to the authentication server in response to access from the user terminal;
The authentication server is
An authentication system further comprising: an authentication result notification unit that transmits an authentication result notification, which is a result of authentication with the user terminal that has performed access when the authentication query is received, to the service providing server. The authentication system according to any one of claims 1 to 4,
The authentication server is
An authentication system further comprising an authorization token transmission unit that generates an authorization token each time the second authentication unit succeeds in authentication and transmits the authorization token to the user terminal that is an authentication partner.   The program for functioning a computer as a user terminal contained in the authentication system in any one of Claim 1 to 6.   A program for causing a computer to function as an authentication server included in the authentication system according to any one of claims 1 to 6.

Images