JP2000049766A - Key managing server system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a safe and simple management method of an open key certificate and a secret key by automating a system with a key management server which manages a key management table and an application management table. SOLUTION: When a connection request (1) to an application server 6 from a client terminal 4 is given, a key management server 1 obtains an open key certificate for application (4 and 5) from an application CA8, by using a key management table 2 (2) or an application management table 3 (3). An open key certificate for application and a secret key, which are required for certification at the time of connection with the application server 6, are transmitted to the client terminal 4 (6). The client terminal 4 is certified (7) at connection by using the open key certificate for application and the secret key, which are received from the key management server 1. If certification is successful, communication with the application server 6 can be conducted.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention manages public key certificates and private keys in a system that handles a plurality of public key certificates and private keys and uses them for each authentication required when connecting to each application server. About.

[0002]

2. Description of the Related Art Conventionally, as a method relating to user key management, for example, there is a "portable information storage medium and an authentication method and an authentication system using the same" described in JP-A-09-223210.

[0003] In this method, a user first enters C
A issues an application for key issuance, and the CA receives the application for issuance, generates the public key and private key of the application user, writes the public key certificate and private key of the application user on the IC card, and sends the application user off-line. Send the IC card. The public key certificate includes the public key of the requesting user and the signature of the CA that certifies the authenticity of the public key.

A user creates a signature using the secret key of the received IC card and uses it for authentication, and owns and manages the IC card.

When one user has a plurality of public key certificates and private keys and uses them for each authentication with each application server, if a special system is not prepared, a public key certificate is issued from key generation. It is necessary for the user to perform all of the application and its management by himself.

[0006]

According to the method disclosed in Japanese Patent Application Laid-Open No. 09-223210, although a user can safely manage a private key, one user can use a plurality of public key certificates and private keys. If so, it does not mention how to use it properly. Also, when the user requests the CA to issue a public key certificate, the user must perform the processing by himself. Further, the public key and the private key are set to be generated by the CA, but there is no mention of a case where a CA not performing such key generation is requested to issue a public key certificate.

In a method in which a user manages a plurality of public key certificates and private keys by himself / herself, a public key certificate and a private key required for authentication at the time of application connection are properly used, and a public key certificate whose expiration date has expired is used. When the secret key is managed on the magnetic disk or the like of the client terminal, there is a problem in that the secret key must be encrypted with the password of the user in order to prevent plagiarism.

[0008] An object of the present invention is to make a user aware of whether to use a public key certificate and a private key of a user required for authentication when connecting to an application server, and to update a public key certificate, generate a key, and publish it. The key management server automates the procedure for issuing a key certificate, reducing the burden on the user and managing only the public key certificate and private key pair for the key management server system. An object of the present invention is to provide a secure and easy method of managing a public key certificate and a private key by storing the certificate in a removable medium.

[0009]

In order to achieve the above object, according to the present invention, a pair of a public key certificate and a private key for each application created for each user and an application used for authentication at the time of connection are provided. A key management table to be managed, an algorithm for generating a key used for authentication at the time of connection for each application, and an application C for issuing an application public key certificate used for authentication
A, an application management table for storing information of an accessible user list file storing accessible user names, and a key management table and an application management table for managing the key management table and the application management table. If the user has access to the application server and the public key certificate and private key for the application required for authentication do not exist in the user's key management table, or if they do, the expiration date of the public key certificate If the key has expired, the application CA generates a key if the CA does not generate a key, and then issues an application for issuing a public key certificate on behalf of the user. User key management of the received application public key certificate Registered Buru, characterized in that it comprises what will become the key management server sends these public key certificate and private key to a client terminal used by a user.

Furthermore, in the present invention, the key management server and the user authenticate each other using the public key certificate and the private key for the key management server system issued by the key management server system CA trusted by the key management server system. Then, the user obtains a public key certificate and a private key for the user's key management server system distributed from the administrator of the key management server system,
The key management server system CA owns and manages a removable medium that stores the public key certificate of the CA itself, sets the removable medium in the media reader only when connection with the application server is necessary, receives authentication from the key management server, and It is characterized by receiving a public key certificate and a private key for an application necessary for connection to a server.

[0011]

DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below in detail with reference to the drawings.

FIG. 1 is a block diagram showing a configuration of a key management server system according to an embodiment of the present invention.

Reference numeral 1 denotes a key management server that manages a key of a user, and manages a key management table 2, an application management table 3, and a plurality of client terminals 4.

Reference numeral 2 denotes a key management table that stores, for each user managed by the key management server 1, an application and correspondence information between a public key certificate and a private key for the application used for authentication when the application is connected, Details are shown in FIG.

Reference numeral 3 denotes an algorithm for generating a key used for authentication at the time of connection with each application, and an application CA for issuing a public key certificate for the application.
8 and an application management table for storing information of an accessible user list file storing names of users who can access the application. The details are shown in FIG.

Reference numeral 4 denotes a client terminal, 5 denotes a removable medium readable from the client terminal 4, and 6 denotes various application servers.

[0017] 7 is trusted by the key management server system,
The key management server system CA issues a key management server system public key certificate used for encrypting communication between a user registered in the key management server system and the key management server 1.

Reference numeral 8 denotes an application CA for each application that issues an application public key certificate used by each application server 6 for authentication at the time of connection.
And the CA designated by each application server 6.

FIG. 2 shows the client terminal 4, the key management server 1, the application server 6, and the application CA8 that issues an application public key certificate used for authentication by the application server 6 in the key management server system. FIG. 3 is a block diagram illustrating an outline of data exchange between them. The general operation of the key management server system will now be described based on FIG.

When a user requests connection with the application server 6, the client terminal 4 first connects to the key management server 1, and a public key certificate and a secret for an application required for authentication at the time of connection with the application server 6. The key is obtained from the key management server 1, and the key is used to connect to the application server 6 for authentication and communication.

Upon receiving a connection request from the client terminal 4, the application server 6 authenticates the user using a public key certificate and a private key for the application of the user using the client terminal 4. The communication with the client terminal 4 is started.

This will be described more specifically.

Upon receiving a connection request () from the client terminal 4 to the application server 6, the key management server 1 uses the key management table 2 () or the application management table 3 () to send a request from the application CA 8. Obtain an application public key certificate
(,). Then, a public key certificate and a private key for an application necessary for authentication at the time of connection with the application server 6 are transmitted to the client terminal 4 to the client terminal 4 (). The client terminal 4 uses the public key certificate and private key for the application received from the key management server 1 to be authenticated when connecting to the application server 6 (). If the authentication is successful, the client terminal 4 can communicate with the application server. it can().

Next, a more detailed operation of the key management server 1 will be described.

The key management server 1 receives a connection request from the client terminal 4 used by the user to the application server 6, and manages a public key certificate and a private key for an application necessary for authentication at the time of connection of the application. Check if it exists in Table 2. If they exist, they are extracted from the key management table 2 and transmitted to the client terminal 4. If it does not exist, an application CA8 for sending an application public key certificate issuance request is obtained from the application management table 3. If the application CA8 does not generate a key, a key is generated from a key generation algorithm, and the application CA8 is sent to the application CA8. A request for issuing a public key certificate is sent, the application private key and the application public key certificate received from the application CA8 are registered in the user key management table 2, and the private key and public key certificate are transmitted to the client terminal 4. Send.

The communication between the key management server 1 and the client terminal 4 is performed by a key management server system public key certificate issued from the key management server system CA7 to the key management server 1 and the user, and a pair thereof. Using the secret key for the key management server system.

Next, the configuration of the key management table 2 is shown in FIG. One table is created for each user, and a public key certificate and a private key for an application required for authentication at the time of connection are taken out according to the application server 6 to which the user requests connection. I have. The key management table 2 is encrypted with the public key for the key management server system of the key management server 1.

Next, the configuration of the application management table 3 is shown in FIG. An application CA8 for issuing an application public key certificate required for authentication at the time of connection for each application server 6, a key generation algorithm required when the application CA8 does not generate a key, and an accessible user name are stored. It consists of an accessible user list file.

The user distributes the public key certificate for the key management server system issued from the key management server system CA7 and the secret key for the key management server system to be paired therewith, which are distributed by the administrator of the key management server system. As long as there is only the removable medium 5 in which the public key certificate of the key management server system CA7 itself is stored, it is possible to perform the acquisition of the application public key certificate, the generation of the key, and the proper use of the key for each application.

FIG. 5 shows contents stored in the removable medium 5 which is distributed by the user from the administrator of the key management server system and is possessed and managed. It comprises a public key certificate and a private key for the user's key management server system, and a public key certificate of the key management server system CA7 itself. The user can be authenticated by the key management server 1 only by having the information registered in the key management server system and having the information stored in the removable medium 5 connected to the application server 6 to which he has access authority. Communication can be performed without being aware of whether to use the public key certificate and the private key for the application in authentication at the time.

FIG. 6 is a flowchart showing a processing procedure when the client terminal 4 issues a connection request to the application server 6. In FIG. 6, first, the user issues a connection request to the application server 6 to the key management server 1 (step 601), and the client terminal 4 sends the public key certificate and private key for the user's key management server system from the removable medium 5. And the public key certificate of the key management server system CA7 itself (step 60).
2) The transmission data 1 to the key management server 1 is created (step 603), and the transmission data 1 is signed with the user's private key for the key management server system (step 604).
This transmission data 1 has the contents shown in FIG.

Next, the created transmission data 1 is transmitted to the key management server 1 (step 605).
Is received (step 606). The client terminal decrypts the transmission data 2 transmitted from the key management server 1 with the user's private key for the key management server system (step 607). Next, the signature of the public key certificate for the key management server system of the key management server 1 included in the received transmission data 2 is confirmed using the public key of the key management server system CA7 itself (step 6).
08), the signature of the transmission data 2 transmitted from the key management server 1 with respect to the item numbers 1 to 4 in FIG. 9 (item number 5 in FIG. 9) is confirmed using the public key of the key management server 1 (step). 609), a public key certificate and a private key for the application required for authentication at the time of connection with the application server 6 are obtained (step 610). The client terminal 4 is authenticated in accordance with the protocol of each application server 6 using the received public key certificate and private key for the application (step 611).

FIG. 7 is a flowchart showing a processing procedure when a connection request from the client terminal 4 of the key management server 1 to the application server 6 occurs. 7, first, transmission data 1 of a connection request to the application server 6 transmitted from the client terminal 4 is received (step 701), and the key management server 1 caches the data or, if necessary, from the key management server system CA7. The signature of the user's public key certificate for the key management server system (item number 2 in FIG. 8) in the transmission data 1 is confirmed with the obtained public key certificate of the key management server system CA7 (step 702).

Next, the signature (item number 3 in FIG. 8) of the transmission data 1 received from the client terminal 4 is confirmed using the user's public key for key management server system (item number 2 in FIG. 8) (step 703). ), The user searches the key management table 2 for an application public key certificate and private key required for authentication when connecting to the application server 6 (step 704). The access right to the application server 6, which determines whether or not the user name is present in the accessible user list file, the presence or absence of the key, and the expiration date of the application public key certificate if the key exists, are checked. (Step 705) If there is no key pair or the validity period has expired, the application management table 3 is used, and if the application CA8 does not generate a key, key generation is performed (Step 706), and the application CA8 is made public for the application. A key certificate is obtained (Step 707).

If the user does not have the right to access the application server 6, an error signal is transmitted to the client terminal 4 (step 711).
The client terminal 4 receives this signal and ends with an error. Next, transmission data 2 to the client terminal 4 is created (step 708), and the transmission data 2 is signed with the key management server system private key of the key management server 1 (step 709). This transmission data 2 has the contents shown in FIG. Then, the transmission data 2 is encrypted with the user's key management server system public key (item number 2 in FIG. 8) in the transmission data 1 received from the client terminal 4 and transmitted to the client terminal 4 (step 710).

In operating this key management server system, first, the key management server system CA7 is connected to the existing CA.
Select from or open for this system. Then, for each application server 6, a key generation algorithm used for authentication at the time of connection and an application CA8 for issuing an application public key certificate used for authentication.
Then, an application management table 3 for storing information of an accessible user list file storing accessible user names is created.

Then, the user requests the key management server system administrator to register with the key management server 1. By this registration, the user's key management table 2 is stored in the key management server 1.
Is created. Then, it determines which application can be used by the user, and changes the accessible user list file storing the accessible user names referred to from the application management table.

Then, the administrator of the key management server system generates a public key and a secret key for the key management server system used by the user in the key management server system, and sends the public key and the secret key from the key management server system CA7 to the key management server system. A public key certificate is issued, and the public key certificate and private key for the key management server system and the public key certificate of the key management server system CA7 are stored in the removable medium 5 and distributed to the user. Only when the user connects to the application server 6 via the key management server 1, the user sets the removable medium 5 in the media reader and sets the public key certificate and private key for the application necessary for authentication at the time of connection with the application server. To receive.

Here, the public key certificate and the private key for the application of the user managed by the key management server 1 are encrypted with the public key for the key management server system of the key management server 1. It is desirable to be placed in an environment where unauthorized access is not made.

[0040]

As described above, according to the present invention,
The user only needs to manage the public key certificate and the private key for the set of key management server systems on a secure removable medium. Then, there is no need to be aware of whether to use the public key certificate and the private key for the application, which are required for the authentication at the time of connection for each of the plurality of application servers, and the key management is released. In addition, the key management server automatically generates the key and obtains the application public key certificate, so that the burden on the user is reduced. Further, since information on each application is collectively managed in an application management table managed by the key management server, it is possible to easily cope with a change.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a schematic configuration of an embodiment of a key management server system according to the present invention.

FIG. 2 is a block diagram showing an outline of data exchange between a client terminal, a key management server, an application server and an application CA in the key management server system.

FIG. 3 is a key management table showing correspondence between applications managed by a key management server for each user, and public key certificates and private keys for the applications.

FIG. 4 is a diagram showing an application management table indicating an accessible user list file storing an application CA, a key generation algorithm when key generation is necessary, and an accessible user name;

FIG. 5 is a diagram showing contents stored in a removable medium possessed and managed by each user.

FIG. 6 is a flowchart showing an outline of a processing procedure when making a connection request of a client terminal to an application server.

FIG. 7 is a flowchart showing an outline of a processing procedure when a connection request from the client terminal of the key management server to the application server occurs.

FIG. 8 is a diagram showing a format of transmission data 1 transmitted from the client terminal to the key management server in data exchange between the client terminal and the key management server.

FIG. 9 is a diagram showing a format of transmission data 2 transmitted from the key management server to the client terminal in data exchange between the client terminal and the key management server.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 ... Key management server, 2 ... Key management table, 3 ... Application management table, 4 ... Client terminal,
5: removable media, 6: application server, 7: key management server system C
A, 8: An application CA that issues an application public key certificate used by each application server for authentication at the time of connection.

 ──────────────────────────────────────────────────続 き Continuing from the front page (72) Inventor Kunio Nashimoto 6-81 Onoecho, Naka-ku, Yokohama-shi, Kanagawa Prefecture In-house Hitachi Software Engineering Co., Ltd. (72) Inventor Takeo Itai 6-81 Onoecho, Naka-ku, Yokohama-shi, Kanagawa Address Hitachi Software Engineering Co., Ltd. In-house (72) Inventor Hitoshi Kumagai 6-81 Onoecho, Naka-ku, Yokohama-shi, Kanagawa Prefecture Hitachi Software Engineering Co., Ltd. In-house F-term (reference) 5K013 BA02 EA06 GA08

Claims (5)

[Claims] 1. A pair of a public key certificate and a secret key (these are called a public key certificate and a private key for an application) created for each user and used for authentication of each application and its connection are managed. Stores a key management table, a key generation algorithm used for authentication at the time of connection for each application, a CA for issuing an application public key certificate used for authentication (this is called an application CA), and an accessible user name. A key management server system comprising: an application management table for storing information of an accessible user list file. 2. Both the key management server and the user can use a public key certificate (which is called a key management server system CA) issued by a certain CA trusted by the key management server system (this is called a key management server system CA). A key management server system comprising a communication protocol for encrypting and authenticating each other's communication using a public key certificate for a key management server system). 3. A public key certificate and a private key for an application necessary for authentication when connecting to an application server when a connection request to a certain application server is made from a client terminal used by a certain user. Has not yet been registered in the key management table for the user, and if the user has access to the application server, the key management server obtains the key generation algorithm from the application management table,
Automatically generate a public key / private key pair, obtain the application CA from the application management table, request the CA to issue a public key certificate, and create a new application in the user key management table. A key management server system for registering a key pair. 4. When a connection request to a certain application server is made from a client terminal used by a certain user, the user first connects to a key management server, and the key management server discloses the user to a key management server system. Authentication is performed using a key certificate and a pair of secret keys (this is called a secret key for a key management server system). If the authentication is successful,
The public key certificate and private key for the application required for authentication when connecting to the application server from the client terminal are retrieved from the user's key management table, and the expiration date of the public key certificate is checked. Then, the public key certificate is transferred to the application CA as in claim 3.
And a public key certificate and a private key for an application are encrypted with a user's public key for the key management server system and transmitted. 5. Each user stores a public key certificate and a private key for his / her own key management server system distributed by an administrator of the key management server system, and a public key certificate of the key management server system CA itself. A key management server system that owns and manages the removable media and receives authentication from the key management server by using the media.