Device management apparatus, method and program for controlling device management apparatus

Abstract

To improve the convenience of managing a key pair having a specified purpose managed on a device. [Solution] A device management device that manages key pairs that are set in a managed network device via a network accepts a choice of whether to overwrite a key pair with the key pair instructed to be added when a key pair with the same purpose as that of a key pair instructed to be added to a network device is already set in the network device, and if the choice of overwriting with the key pair instructed to be added has been accepted, deletes the same purpose as the key pair instructed to be added from the uses of the key pairs set in the network device, and adds the key pair instructed to be added.

Description

[Technical field]

[0001] The present invention relates to a device management apparatus, a control method for the device management apparatus, and a program. [Background technology]

[0002] Conventional methods for managing key pairs of devices include, for example, a method in which the device itself generates a key pair and uses the key pair. Patent Document 1 discloses a technique in which, when the device is turned on, it is determined whether or not key pair data exists in the device, and if no key pair data exists, a key pair is automatically generated and stored. Patent Document 2 discloses a technique for managing key pairs of other devices, in which a key pair is requested from a certification authority, and the key pair received from the certification authority is stored and used. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2005-303676 A [Patent Document 2] JP 7208707 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, when the device itself generates a key pair as in Patent Document 1, the generated key pair is a self-signed certificate, and certificate verification fails. For example, when a key pair generated by the device itself is used as a certificate for an HTTPS server, the web browser displays a warning that the connection is not secure. In addition, when a key pair is requested from a certificate authority as in Patent Document 2, it is necessary to prepare a certificate authority that accepts requests for key pairs from devices, which places a burden on customers. In addition, when a key pair has uses such as TLS communication, signatures, IPSec, and IEEE802.1X authentication, it is necessary to specify these uses separately. When a use is specified for a key pair, there is a restriction that only one key pair for that use always exists, and keys cannot be added or deleted.

[0005] An object of the present invention is to improve the convenience of managing key pairs, each having a designated purpose, managed by a device. [Means for solving the problem]

[0006] In order to solve the above problems, the device management device of the present invention is a device management device that manages key pairs that are set in a managed network device via a network, and has a selection means that, when a key pair with the same purpose as that of a key pair instructed to be added to the network device is already set in the network device, accepts a selection of whether to overwrite it with the key pair instructed to be added, and an adding means that, when the selection of overwriting with the key pair instructed to be added has been accepted, deletes the same purpose as the key pair instructed to be added from the uses of the key pairs set in the network device, and adds the key pair instructed to be added. The adding means creates a list of key pairs to be registered by adding the key pair instructed to be added to a list of key pairs registered in the network device, creates key pair registration instruction data in which the same purpose as the key pair instructed to be added is deleted from the purposes of the key pairs set in the network device in the list of key pairs to be registered and the purposes of the default keys set in the network device, and sends the data to the network device, thereby adding the key pair. In addition, the device management device of the present invention is a device management device that manages key pairs set in a managed network device via a network, and has a deletion means that deletes a key pair that has been instructed to be deleted from the network device, and when the deletion means deletes a key pair for a specific purpose that must always be present in the network device, it adds the specific purpose to the purpose of the default key of the network device. Effect of the Invention

[0007] According to the present invention, it is possible to improve the convenience of managing key pairs, each of which is managed in a device and has a designated purpose. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an overall configuration of a network device management system. [Diagram 2] FIG. 2 is a diagram illustrating a hardware configuration of a device management server. [Diagram 3] FIG. 2 is a diagram illustrating a software configuration of a device management server and an agent. [Figure 4] FIG. 13 is a diagram illustrating an example of a key pair management screen provided by the device management server. [Diagram 5] FIG. 13 is a diagram illustrating an example of a key pair registration screen provided by the device management server. [Figure 6] FIG. 13 is a diagram illustrating an example of a setting screen for associating a key pair with a device. [Figure 7] FIG. 13 is a diagram illustrating an example of a screen for adding a key pair to a device. [Figure 8] 11 is a flowchart showing a process for adding a key pair to a device. [Figure 9] 11 is a flowchart showing a process for adding a key pair to a device. [Figure 10] 13 is a flowchart showing a process for creating a list of key pairs to be registered and a list of key pair differences. [Figure 11] FIG. 13 is a diagram showing an example of a setting screen for deleting a key pair from a device. [Figure 12] 11 is a flowchart illustrating a process for deleting a key pair from a device. [Figure 13] 11 is a flowchart illustrating a process for deleting a key pair from a device. [Figure 14] 13 is a flowchart showing a process of integrating a list of key pairs. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] (First embodiment) Fig. 1 is a diagram for explaining the overall configuration of a network device management system. A network device management system (hereinafter referred to as a device management system) provides services (functions) to network devices via a network. When there are a large number of devices to be managed, the device management system may be configured with a management device that performs overall management, and multiple agents that execute processing on devices according to instructions from the management device. The device management system of this embodiment has one device management application server and multiple agent application devices.

[0010] The device management server 101 is a device management apparatus having a device management application. The device management application provides a function for managing devices to be managed. The agent 106 and the agent 107 are agent devices having an agent application. That is, the device management system of this embodiment has one device management server 101 and the agent 106 and the agent 107 as multiple agent application devices. The device management system manages the device 102, the device 103, the device 110, and the device 111 as network devices. The agent and the network devices are linked according to the device addresses, etc. For example, the agent 106 is linked to the devices 102 and 103, and the agent 107 is linked to the devices 110 and 111. Note that, in this embodiment, an example will be described using two agents and four devices, but even if tens of thousands of devices are managed via a dozen or so agents, the configuration and operation are the same as those described in this embodiment.

[0011] The device management system may also include a directory server 105. The directory server 105 is an information processing device that manages user information such as user accounts. The device management server 101 and the directory server 105 are connected to each other via a network 104. The device management server 101 can also be set so that a user of the directory server 105 can log in as a user of the device management server 101.

[0012] The device management server 101, the directory server 105, the agent 106, the device 102, and the device 103 are interconnected by a network 104. The network 104 is, for example, a WAN. The agent 107, the device 110, and the device 111 are interconnected by a network 108. The network 108 is, for example, a LAN. The network 104 and the network 108 are connected by a router 109. The router 109 can be configured to permit communication between the device management server 101 and the agent 107 on the network 108, but block communication between the device management server 101 and the devices 110 and 111.

[0013] In this embodiment, the network 104 is a WAN and the network 108 is a LAN, but the network 104 and the network 108 may be configured to transmit and receive data, and the communication method is not important. For example, each network may be configured as a LAN, a WAN, a cellular network such as LTE or 5G, a wireless network, a telephone line, a dedicated digital line, or a combination of these.

[0014] In this embodiment, communication between the device management server 101 and the devices 102 and 103 is performed via the agent 106. Also, communication between the device management server 101 and the devices 110 and 111 is performed via the router 109 and the agent 107. Note that, although an example in which the device management server 101 and the agent 106 operate on different hosts will be described in this embodiment, it is also possible for the device management server 101 and the agent 106 to operate on the same host. When the device management server 101 and the agent 106 operate on the same host, it is possible for the devices 102 and 103 to communicate directly with the device management server 101.

[0015] The device management server 101 provides various services (functions) to the network devices to be managed. The device management server 101 of this embodiment uses an agent to provide services to the network devices. The services provided by the device management server 101 include, for example, a service for managing key pairs of network devices. The device management server 101 also has a built-in web service server related to the functions provided by the device itself. The device management server 101 may be realized by one or more information processing devices, a virtual machine (cloud service) using resources provided by a data center including the information processing devices, or a combination of these. The directory server 105 may also be realized by one or more information processing devices, a virtual machine (cloud service) using resources provided by a data center including the information processing devices, or a combination of these. The device management system may also be implemented as a Web-based application, and may also be used on a PC via a Web browser.

[0016] Agent 106 and agent 107 are agent devices that communicate with devices based on instructions from device management server 101. Agent 106 and agent 107 each have a built-in web service server related to functions provided by device management server 101. In addition, the agent is linked to a network device according to the address of the network device, etc. Agent 106 is linked to device 102 and device 103. Agent 107 is linked to device 110 and device 111.

[0017] The devices 102, 103, 110, and 111 are network devices that are managed by the device management server 101 and can communicate with the device management server 101. The network devices are, for example, multifunction printers (MFPs) that integrate multiple functions such as a print function, a read function, and a FAX function. The network devices may be image forming devices such as printers, scanners, and 3D printers, information processing devices such as PCs, image processing devices such as cameras, smart home appliances, and the like. The network devices are capable of performing encrypted communication with external devices such as the device management server 101, and have an HTTPS server function. A key pair of a public key and a private key for communication encryption is set in the network device of this embodiment. The key pair set in the device includes a default key that is managed so that it cannot be deleted from the device. In addition, it is possible to set a purpose for the key pair. It is also possible not to set a purpose for the key pair.

[0018] Here, a process flow for providing a service to a network device by the network device management system will be described using the agent 106 and the device 102 as an example. The device management server 101 instructs the agent 106 to operate the device 102. The agent 106 performs operations such as sending a request to the device 102 according to the instructions of the device management server 101, and sends the results to the device management server 101. Examples of operations by the agent 106 on the device 102 include obtaining information from the device 102, changing settings of the device 102, instructing the device 102 to install an application, and instructing the device 102 to change the settings of a key pair. In this way, communication is performed between the device management server 101 and the agent 106, and between the agent 106 and the device 102. Therefore, the device 102 and the device management server 101 do not directly communicate with each other.

[0019] 2 is a diagram illustrating the hardware configuration of the device management server 101. The host computers on which the agents 106, 107, and directory server 105 run also have the same hardware configuration as the device management server 101. The device management server 101 includes a CPU 201, a RAM 202, a ROM 203, a KBDC 204, a VC 205, a DC 206, and a NIC 208. These components are connected to a system bus 209.

[0020] The CPU 201 controls the entire device management server 101. The CPU 201 loads a program stored in a memory (ROM 203 or external storage device 207) into the RAM 202 as necessary, executes the program, and generally controls each unit connected to the system bus 209. The CPU 201 may also load software (programs) downloaded via a network into the RAM 202 as necessary, and execute the program, thereby generally controlling each unit connected to the system bus 209. The RAM 202 (Random Access Memory) is a memory from which data can be read / written, and functions as the main memory or work area of ​​the CPU 201. The ROM (Read Only Memory) 203 is a memory dedicated to reading data, and stores, for example, a basic control program of the device management server 101. The external storage device 207 is a memory such as a hard disk (HD) or a solid state drive (SSD). The external storage device 207 stores various applications including a boot program, an operating system (OS), an authentication server, an authentication client, and the like, database data, user files, and the like.

[0021] The KBDC 204 controls input to the device management server 101. The KBDC 204 sends input information from input devices such as a keyboard or pointing device (not shown), a virtual keyboard, voice, etc., to the CPU 201, and controls input to the device management server 101. The VC 205 is a video controller and controls display on a display device (not shown). The display device may be, for example, an LCD (Liquid Crystal Display) or a head-mounted display capable of displaying virtual reality (VR). The DC 206 is a disk controller and controls access to the external storage device 207. The NIC 208 is a communication controller, and the device management server 101 is connected to the network 104 via the NIC 208. The CPU 201 is connected to the network 104 via the NIC 208, and enables data communication with each device on the network.

[0022] Fig. 3 shows the software configuration of a device management server and an agent. Fig. 3(A) is a diagram for explaining the software configuration of the device management server 101. The device management server 101 realizes processing by the functional modules shown in Fig. 3(A) by calling an application program for device management from memory and executing it with the CPU 201. The functional modules shown in Fig. 3(A) are provided as, for example, a device management application.

[0023] The device management server 101 has an agent management section 301, a device management section 302, a task management section 303, an HTTP / HTTPS server 304, and a firmware management section 305. The agent management section 301 manages information related to the agent 106 and the agent 107. The device management section 302 manages information related to the device 102, the device 103, the device 110, and the device 111. The information related to the device includes information about which agent the device is linked to. The task management section 303 manages tasks. As part of task management, the task management section 303 manages the contents and results of operations on the device. Furthermore, the task management section 303 instructs the agent to operate the device by executing a task. The management information managed by the task management section 303 is stored in a database (not shown).

[0024] The device management server 101 has both HTTP and HTTPS functions. The HTTP / HTTPS server 304 is a web service server built into the device management server 101 that is related to services provided by the device management server 101. The HTTP / HTTPS server 304 receives requests from external devices such as agents and devices, and returns responses to the requests. The HTTP / HTTPS server 304 also provides a WEB UI that enables a user to operate the device management server 101. The key pair management unit 305 manages key pairs in the device and key pairs set in the device.

[0025] Fig. 3(B) is a diagram for explaining the software configuration of an agent. Here, agent 106 will be explained as an example, but other agents have a similar configuration. Agent 106 realizes processing by the functional modules shown in Fig. 3(B) by calling an application program for the device management agent from memory and executing it with CPU 201. The functional modules shown in Fig. 3(B) are functional modules related to services provided by device management server 101, and are provided as agent applications provided by device management server 101, for example.

[0026] The agent 106 has a task execution unit 310 and an HTTP / HTTPS server 311. The task execution unit 310 executes a task instructed by the device management server 101. The task execution unit 310 executes an operation on a device according to an instruction from the device management server 101, and then transmits the result to the device management server 101. The HTTP / HTTPS server 311 is a web service server built into the agent 106 that is related to services provided by the device management server 101. The HTTP / HTTPS server 311 receives requests from the device management server 101 and external devices such as devices. The device management server 101 and the agent 106 communicate with each other mainly using HTTPS via the HTTP / HTTPS server 304 of the device management server 101 and the HTTP / HTTPS server 311 of the agent 106.

[0027] FIG. 4 is a diagram showing an example of a key pair management screen provided by the device management server 101. The key pair management screen includes, for example, a table 401, a new registration button 402, a drop-down list 403, and an execute button 404. The table 401 is a table that displays a list of key pairs registered in the device management server 101. The table 401 includes, for example, items such as name, purpose, subject, number of linked devices, number of installed devices, and deletion. "Name" is the name given to the key pair by the user. "Purpose" is the purpose specified for the key pair. The uniqueness of each key pair is ensured by the combination of "name", "purpose", and the key pair itself.

[0028] Table 401 also includes the key pairs registered in each device obtained from device 102, device 103, device 110, and device 111. The "number of linked devices" in table 401 displays the number of devices that are linked to register the key pair. When it detects a user's click on the "number of linked devices" cell of a row in the table, the device management server 101 transitions to a screen (FIG. 6) for setting the link between the key pair and the device in the clicked row. The "number of installed devices" in table 401 is the number of devices in which the key pair is registered. When it detects a user's click on the "number of installed devices" cell of a row in the table, the device management server 101 displays a list of devices in which the key pair in the clicked row is registered (not shown).

[0029] "Delete" displays deletable key pairs in a recognizable manner. A deletable key pair is a key pair that is not registered in a device (i.e., the "number of installations" is 0). In the example shown in FIG. 4, an "X" mark is displayed as a delete button in the delete item for a deletable key pair. On the other hand, if the key pair is already registered in a device (i.e., the "number of installations" is 1 or more), the device management server 101 does not display the delete button "X". When the device management server 101 detects a user clicking on the "X" cell of a row in the table 401, the device management server 101 displays a dialog box to confirm the deletion of the key pair of the clicked row. Then, when the device management server 101 confirms the user's instruction to delete, it deletes the key pair from the device management server 101.

[0030] The new registration button 402 is a button for registering a key pair. When the click of the new registration button 402 is detected, the device management server 101 transitions to a screen (FIG. 5) for registering a key pair in the device management server 101, which will be described later. The drop-down list 403 is a drop-down list for selecting a process. The options 405 indicate the options of the drop-down list 403. The options of the drop-down list 403 include, for example, "obtain key pair from device," "add key pair to device," and "delete key pair from device." The user selects a desired process in the drop-down list 405 and presses the execute button 404. When the click of the execute button 404 is detected, the device management server 101 executes a process according to the process selected in the drop-down list 403. When the click of the execute button 404 is detected, the device management server 101 obtains information on the key pair registered in the device, saves the result in a database or file system in the device management server 101, and updates the display of the table 401. If "Add key pair to device" is selected, the device management server 101 opens a setting screen for adding a key pair to the device as shown in Fig. 7. If "Delete key pair from device" is selected, the device management server 101 opens a setting screen for deleting a key pair from the device as shown in Fig. 11.

[0031] Fig. 5 is a diagram showing an example of a key pair registration screen provided by the device management server 101. When the device management server 101 detects pressing of the New Registration button 402, it displays the key pair registration screen shown in Fig. 5. On the key pair registration screen, a key pair to be added to a device is registered in the device management server 101. Here, an example will be described in which a key pair is registered in the device 102. The key pair registration screen includes, for example, a Browse button 501, a file name 502, a name 503, a password 504, a purpose 505, an Add button 506, and a Cancel button 507.

[0032] Browse button 501 is a button for specifying a file in which key pair data stored in the host computer is stored. The key pair data is stored in a file in PKCS#12 format, for example. The format of the key pair data is not limited to PKCS#12 format. When Browse button 501 is clicked, a file selection dialog provided by the OS or web browser opens. In the displayed dialog, the user selects a file name corresponding to the key pair data. File name 502 is a file name including the key pair selected by clicking Browse button 501. In the example shown in FIG. 5, a key pair with file name 502 of "printer03.pfx" is specified as the key pair to be registered.

[0033] The name 503 is a text box for inputting the name of the key pair. The name of the key pair is used by the device management server 101 and the device 102 as information for the user to identify the key pair. The password 504 is a text box for inputting the password of the key pair in the PKCS#12 format indicated by the file name 502. The purpose 505 is a check box for specifying the purpose of the key pair to be added in the device 102. Here, multiple check boxes can be selected. For example, "TLS", "IEEE 802.1X", "IPSec", and "SIP" can be selected as the purpose 505 of the key pair in the device 102. Note that the purpose of the key pair is not limited to these. The key pair for "TLS (Transport Layer Security)" is a server key pair used when the device has an HTTPS server function. The HTTPS server function of the device uses TLS as a communication protocol, and uses a key pair for TLS in TLS communication. The key pair for "IEEE 802.1X" is a key pair used in the IEEE 802.1x authentication function. The key pair for "IPSec (Security Architecture for Internet Protocol)" is a key pair used in IPSec encrypted communication. The key pair for "SIP (Session Initiation Protocol)" is a key pair used in SIP encrypted communication. In the example shown in Fig. 5, the "TLS" checkbox is checked as usage 505.

[0034] The Add button 506 is a button for additionally registering a key pair specified by the user on the key pair registration screen in the device management server 101. The device management server 101 enables the Add button 506 when the file specification 502, the input of the name 503, and the input of the password 504 are valid. It is possible to register a key pair even if the purpose 505 is not specified. When detecting a click of the Add button 506 by the user, the device management server 101 checks the contents input on the key pair registration screen. Specifically, the device management server 101 checks whether the key pair file in the PKCD#12 format indicated by the file name 502 is a valid key pair and whether the password of the key pair file matches the password input in the password 504. If the check result is correct, the device management server 101 stores the key pair data of the file name 502 together with the name 503, the password 504, and the purpose 505 in a database or a file system in the device management server 101. Then, when the registration of the key pair is completed, the device management server 101 transitions to a key pair management screen shown in Fig. 4. On the other hand, if the confirmation result is incorrect, for example, if the key pair file is invalid or the password does not match, the device management server 101 displays an error dialog and does not register the key pair. When the device management server 101 detects that the user has clicked on the cancel button 507, it transitions to a key pair management screen shown in Fig. 4.

[0035] 6 is a diagram showing an example of a binding setting screen between a key pair and a device provided by the device management server 101. When the device management server 101 detects a click on a "binding" cell of a row in table 401 on the key pair management screen (FIG. 4), the device management server 101 displays the binding setting screen. The binding setting screen is a screen for setting and managing the binding between a key pair selected on the key pair management screen and a network device. The binding setting screen includes, for example, key pair information 601, a table 602, a save button 603, and a cancel button 604.

[0036] Key pair information 601 is an area that displays information about the key pair to be linked. For example, the name, purpose, and subject of the key pair are displayed in key pair information 601. Table 602 is a table for selecting a device to be linked to the key pair. For example, check boxes and device information are displayed in table 602. The device information includes, for example, the device name, product name, device IP address, and device installation location. The user specifies the device to be linked to the key pair by selecting a check box in table 602.

[0037] When detecting a user click on a Save button 603, the device management server 101 associates the device whose check box in table 602 is selected with the key pair to be associated, which is displayed in the key pair information 601, and stores the associated key pair in the database. When detecting a user click on a Cancel button 604, the device management server 101 transitions to a key pair management screen shown in FIG.

[0038] Data for the device management server 101 and the device 102 to exchange key pair information is made up of a group of files compressed and integrated using, for example, ZIP or TAR. The group of files is made up of a setting file (for example, an XML file or a JSON file) that describes the key pair information, and a directory that stores files in which each key pair data is converted into PKCS#12 format. An example of a key setting file for the device 102 is shown below. <?xml version=”1.0”?> <device_configuration xmlns=”http: / / www.my.company.com / ns / deviceConfiguration”> <configuration_settings> <password> X'78B0851086BA1A9A8741903A515A085D07D17A8A9152B44D44BB1D27C7DD0B877A'< / password> < / configuration_settings> <key_management_settings> <key> <device_default_key usage=”1” / > <device_keys> <device_key name=”printer03_TLS_key” usage=”1”> device_key_file_01.p12 < / device_key> <device_key name=”printer03_wifi_key” usage=”2”> device_key_file_02.p12 < / device_key> < / device_keys> < / key> < / key_management_settings> < / device_configuration>

[0039] The "password" in the "configuration_settings" of the configuration file stores the password information for the configuration file. Sensitive information in the configuration file is encrypted using information generated from this password. The password for the configuration file is the password for the PKCD#12 format file of the key pair included in the configuration data. The password information for the configuration file is, for example, a value calculated from the hash of the password, so that the password cannot be guessed from the configuration file.

[0040] The keys in the device 102 consist of one default key pair automatically generated by the device 102 and multiple key pairs registered by the user. The key_management_settings block includes the usage of the default key pair (usage of device_default_key) and information on multiple key pairs registered by the user (device_keys). The default key is a key pair that is stored in the device from the time of shipment from the factory and is managed so that it cannot be deleted. Therefore, the default key always exists in the device.

[0041] Each key pair registered by the user includes the name of the key pair (device_key name) set by the user and the usage of the key pair as attributes, and the file name of the key pair data as a value. For example, the usage is indicated by 4 bits, and each of the four digits is assigned to the presence or absence of a usage. Each digit indicates the following usage. 1st digit =0001=1= TLS Second digit =0010=2= IEEE 802.1X Third digit =0100=4= IPSec 4th digit =1000=8= SIP For example, "4" (0100 in binary) means "IPSec", and "10" (1010 in binary) means "IEEE802.1X" and "SIP". In addition, there are the following restrictions on key usage: 1. Multiple key pairs, including the default key pair, cannot be assigned the same purpose. 2. A key pair for TLS use must exist. Thus, a key pair for TLS use is a key pair for a given use that must always be present in a network device.

[0042] When the device management server 101 requests the device 102 to obtain information on a key pair registered in the device 102, the device 102 processes its own key pair information into data in the format shown above and returns the data to the device management server 101. When the device 102 receives data on the key pair information in the format shown above from the device management server 101, the device 102 verifies the content of the received data. If there is no problem with the result of the verification, the device 102 updates the registration information of the key pair in the device 102 with the content of the data received from the device 102. Although not described in detail in this embodiment, it goes without saying that authentication and authorization are required when the device management server 101 calls the device 102 to obtain or set key pair information.

[0043] 7 is a diagram showing an example of a setting screen for adding a key pair to a device. The setting screen for adding a key pair to a device is a screen provided by the device management server 101 for setting a process for adding a key pair registered in the device management server 101 to the device 102. When "Add key pair to device" is selected in the dropdown 403 on the key pair management screen (FIG. 4) and clicking of the execute button 404 is detected, the device management server 101 displays the setting screen for adding a key pair to a device.

[0044] The setting screen for adding a key pair to a device includes, for example, a check box 701, a table 702, an add button 703, and a cancel button 704. The check box 701 is used to set a process to be performed when a key pair with the same purpose as the key pair to be added already exists in the device. There is a restriction that the same purpose cannot be assigned to multiple key pairs, including a default key pair, for key purposes. Therefore, when adding a key pair with the same purpose, only one of the existing key pair and the key pair to be newly added can exist as the key pair with the same purpose. Therefore, the check box 701 is used to select whether or not to overwrite and register the existing key pair with the key pair instructed to be added when a key with the same purpose exists. By detecting whether or not the check box 701 is ON / OFF, the device management server 101 functions as a selection means for accepting a selection of whether or not to overwrite with the key pair to be added when a key pair with the same purpose as the key pair to be added to the device 102 has already been set.

[0045] If the check box 701 is selected, the device management server 101 overwrites and registers the key pair to be added this time. That is, the device management server 101 deletes the purpose of the key pair to be added from the key pair already existing in the device, and adds the key pair. If the check box 701 is not selected, the device management server 101 does not add a key pair if a key pair with the purpose of the key pair to be added already exists in the device.

[0046] Table 702 displays a list of key pairs associated with devices. The user selects a key pair to add from the list of key pairs associated with devices displayed in table 702. Table 702 displays check boxes for selecting a key, the key name, purpose, subject, and number of associated devices. The user checks the check box corresponding to the key to add. When detecting a click of the Add button 703 by the user, the device management server 101 starts a process of adding the selected key pair to each device associated with the key pair whose check box is selected in table 702. When detecting a click of the Cancel button 704 by the user, the device management server 101 closes the setting screen for adding the key pair to the device.

[0047] 8 and 9 are flowcharts showing the process of adding a key pair to a device. Here, an example will be described in which the device management server 101 adds a key pair to the device 102. The process of adding a key pair to a device by the device management server 101 is realized by the CPU 201 of the device management server 101 calling up and executing a device management application program from memory (ROM 203 or external storage device 207). Therefore, the CPU 201 of the device management server 101 functions as an adding unit that adds a key pair to a device.

[0048] In step S801, the device management server 101 acquires a list of key pairs instructed to be added to the target device. Specifically, the device management server 101 acquires and lists key pairs associated with the target device from among the key pairs specified to be added by the user. In this embodiment, the device management server 101 acquires a key pair associated with the device 102 from the key pairs selected on the screen for adding a key pair to the device (FIG. 7). In step S802, the device management server 101 checks whether a key pair with the same purpose exists among the key pairs to be added. In step S803, the device management server 101 determines whether a key pair with the same purpose exists as a result of the check in step S802. If a key pair with the same purpose exists as a result of the check, the device management server 101 ends this process without setting the key pair to the device. The device management server 101 may display an error message indicating that a key pair with the same purpose exists. If the check result indicates that a key pair for the same purpose does not exist, the device management server 101 performs the process of step S804.

[0049] In step S804, the device management server 101 acquires registration information of the device's key pair from the device to be added. The key pair information acquired from the device includes the use of the default key pair and a list of registered key pairs. In this embodiment, the device management server 101 acquires from the device 102 a list of key pairs already registered in the device 102 and the use of the default key.

[0050] In step S805, the device management server 101 creates a list of key pairs to be registered in the device, and a list of differences between the list of key pairs to be set in the device and the list of key pairs already registered in the device. The list of key pairs to be registered in the device is a list that combines the key pairs already registered in the device and the key pairs to be added in the current addition process. Specifically, the device management server 101 creates a list of key pairs to be registered in the device from the list of key pairs that are instructed to be added to the device obtained in step S801 and the list of key pairs already registered in the device obtained in step S804. Note that the list does not include default keys. Then, the device management server 101 creates a key pair difference list that is a difference between the list of key pairs to be set in the created device and the list of key pairs already registered in the device obtained in step S804. In other words, the list of key pair differences is a list of key pairs to be newly added to the device 102. The process in step S805 will be described in detail later with reference to FIG. 10.

[0051] In step S806, the device management server 101 determines whether the difference list created in step S805 is empty. If the difference list is empty, this means that there is no new key pair to add, and the device management server 101 ends this process without setting a key pair in the device. If there are differences, that is, if the difference list is not empty, the process of step S807 is performed.

[0052] In step S807, the device management server 101 determines whether or not an overwrite setting for the use of the key pair has been set, which overwrites the use of the existing key pair with the use of the key pair to be added when a key pair with the same use as the use of the key pair instructed to be added is set in the device. The device management server 101 determines whether or not an overwrite setting for the use of the key pair has been set based on the setting of a check box 701 on the setting screen for adding a key pair to a device (FIG. 7). If the check box 701 is not checked, it is determined that the overwrite setting has not been set, and the device management server 101 performs the process of step S811. On the other hand, if the check box 701 is checked, it is determined that the overwrite setting has been set, and the device management server 101 performs the process of step S808.

[0053] There is a restriction that the same use cannot be assigned to multiple key pairs, including a default key pair. Therefore, when the overwrite setting of the use of the key pair is set, if the use set for the key pair to be added is set for the key pair currently registered in the device 102, the device management server 101 needs to delete the use of the registered key pair. Therefore, by repeating the processes of steps S808 and S809, the same use as the use of the key pair to be added is deleted from the use of the key pair including the default key already set in the device 102. In step S808, the device management server 101 extracts a key pair (differential key pair) from the key pair difference list. The key pair in the key pair difference list is different from the key pair currently registered in the device 102 in terms of the key pair body or use, and a part of the use of the key pair currently registered in the device 102 is overwritten with the use of the key pair in the difference list.

[0054] In step S809, the device management server 101 deletes the same usage as the usage of the differential key pair extracted in step S808 from the usage of the existing key pairs. Specifically, the device management server 101 first deletes the same usage as the usage of the differential key pair from the usage of key pairs other than the differential key pair extracted in step S808 in the list of key pairs to be registered created in step S805. Furthermore, the device management server 101 deletes the same usage as the usage of the differential key pair from the usage of default keys. Here, the usage of the default key pair is the usage of the default key pair currently set in the device, obtained from the device 102 in step 804. By deleting the same usage as the usage of the differential key pair from the usage of existing key pairs, it is possible to delete the same usage as the usage of the key pair to be added.

[0055] In step S810, the device management server 101 determines whether extraction of all key pairs from the key pair difference list has been completed. If extraction of all key pairs from the key pair difference list has been completed, the process proceeds to step S811. On the other hand, if extraction of all key pairs from the key pair difference list has not been completed, the process returns to step S808.

[0056] Regarding the use of a key pair, there is a key pair for a specific purpose that must be present in the device. Specifically, in this embodiment, there is a constraint that a key pair for TLS purpose must be present. Therefore, in step S811, the device management server 101 determines whether or not a key pair for TLS purpose, which is a key pair for a specific purpose that must be present in the device, is present in the list of key pairs to be registered. If a key pair for TLS purpose is not present in the list of key pairs to be registered, the device management server 101 performs the process of step S813. On the other hand, if a key pair for TLS purpose is present in the list of key pairs to be registered, the device management server 101 performs the process of step S814.

[0057] In step S813, the device management server 101 adds TLS usage to the usage of the default key pair. By processing in step S813, it is possible to add TLS usage to the default key when the key pair to be registered does not have a key pair for TLS usage, thereby complying with the constraint that a key pair for TLS usage must exist. In step S814, the device management server 101 cancels (deletes) the setting of TLS usage from the usage of the default key pair.

[0058] In step S815, the device management server 101 checks whether a key pair with the same purpose exists among the key pair to be registered and the default key pair. If the check shows that the purposes overlap, the device management server 101 ends this process without setting the key pair in the device. On the other hand, if the check shows that the purposes do not overlap, the device management server 101 performs the process of step S817.

[0059] In step S817, the device management server 101 creates key pair registration instruction data to be sent to the device 102, based on the list of key pairs to be registered and the purpose of the default key pair. Finally, in step S818, the device management server 101 sends the key pair registration instruction data created in step S817 to the device 102. The device 102 that has received the key pair registration instruction data from the device management server 101 sets the key pair of the device 102 based on the received key pair registration instruction data. This realizes the addition of the key pair to the device 102 while complying with the constraints related to the key pair. This ends the key pair addition process. After the key pair addition process ends, the device management server 101 acquires key pair information from the device 102, and updates the list of key pairs (table 401) in the device management server 101, which is displayed on the key pair management screen (FIG. 4).

[0060] Here, detailed processing of step S805 will be described with reference to Fig. 10. Fig. 10 is a flowchart showing processing for creating a list of key pairs to be registered and a list of key pair differences. In this processing, a list of key pairs to be registered in the device 102 and a list of key pairs to be added (a list of key pair differences) are created from the list of key pairs instructed to be added and the list of key pairs registered in the device 102. The processing for creating the list of key pairs to be registered and the list of key pair differences by the device management server 101 is realized by the CPU 201 of the device management server 101 calling up from memory and executing a device management application program.

[0061] The device management server 101 obtains a list of key pairs that have been instructed to be added to the device in step S801, and a list of key pairs already registered in the device (a list of key pairs currently registered in the device 102) in step S804. In step S901, the device management server 101 copies the list of key pairs registered in the device to create a list of key pairs to be registered. In this process, the key pairs decided to be added in the processes of steps S903 to S908 are added to the list of key pairs to be registered created by copying in step S901, thereby completing the list of key pairs to be registered.

[0062] In step S902, the device management server 101 creates an empty list of key pairs for differences. In this process, the key pairs determined to be added in the processes of steps S903 to S908 are added to the empty key pair difference list created in step S902, thereby completing the list of key pair differences.

[0063] In step S903, the device management server 101 sequentially extracts key pairs from the list of key pairs instructed to be added obtained in S801. In step S904, the device management server 101 searches the list of key pairs to be registered for a key pair whose name and body match those of the key pair to be added extracted in S903. In step S905, the device management server 101 determines whether a key pair whose name and body match those of the key pair to be added has been found from the list of key pairs to be registered as a result of the search in step S904. If a key pair whose name and body match is found, the device management server 101 performs processing in step S906. On the other hand, if a key pair whose name and body match is not found, the device management server 101 performs processing in step S907.

[0064] In step S906, the device management server 101 adds the purpose of the key pair to be added to the purpose of the key pair to be registered that matches the name and body of the key pair to be added. Then, the device management server 101 adds the key pair to be registered, the purpose of which has been added, to the key pair difference list. For example, assume that the purpose of the key to be added retrieved in step S903 is "IPSec" and "SIP", and the purpose of the key pair found in the list of key pairs to be registered that matches the name and body is "IEEE 802.1X" and "SIP". "IPSec" is added to the purpose of the matching key pair in the list of key pairs to be registered, and the purpose of the updated key pair becomes "IEEE 802.1X", "IPSec", and "SIP". In other words, the purpose of the key pair to be registered is set to the union of the purposes of the two key pairs (the key to be added retrieved in step S903 and the key pair in the list of key pairs to be registered that matches the name and purpose of the key). In addition, if the purpose of the key pair to be added matches that of a key pair to be registered whose name and body match those of the key pair to be added, neither the purpose is added nor the key pair is added to the key pair difference list.

[0065] In step S907, the device management server 101 adds the key pair to be added retrieved in step S903 to both the list of key pairs to be registered and the difference list. This means that the key pair to be added retrieved in step S903 is not currently registered in the device 102 and is therefore to be additionally registered. In step S908, the device management server 101 checks whether it has processed all key pairs in the list of key pairs to be added retrieved in step S801, that is, whether it has extracted all key pairs in step S903. If the processing has been completed for the key pairs to be added for all devices 102, the device management server 101 performs the processing of step S909. On the other hand, if the processing has not been completed for the key pairs to be added for all devices 102, the device management server 101 returns to the processing of step S903.

[0066] In step S909, the device management server 101 completes the creation of the list of key pairs to be registered and the list of key pairs for differences, and returns the list of key pairs to be registered and the list of key pairs for differences to the caller of the process, thereby terminating this process. Note that if the key pair to be added already exists in the device and its purpose matches, the list of differences will be empty.

[0067] 8 to 10, for example, a key pair is added as follows. Note that in the following, a thumbprint (partially omitted to avoid lengthy display) is used as information for identifying the main body of the key pair, but this is not limited to this. For more precise identification, it is also possible to use a combination of all or part of the thumbprint, serial number, and subject as information for identifying the main body of the key pair.

[0068] (Example 1) Table 1 shows the key pairs of the device 102 before it is added. Two key pairs are set in the device 102 before it is added: a default key pair and a key pair named "printer03-wifi". The usage of the default key pair is set to TLS. The usage of printer03-wifi is set to IEEE802.1X. [Table 1] Table 2 shows the key pair that has been instructed to be added to the device 102. The key pair that has been instructed to be added has the name "printer03-tls" and TLS is set as its purpose. [Table 2]

[0069] A case where a command is issued to add a key pair shown in Table 2 to the device 102 to which the key pair shown in Table 1 is set will be described. First, a case where the check box 701 on the setting screen for adding a key pair to a device (FIG. 7) is set to OFF will be described. In a case where a command is issued to not add a key pair if a key with the same purpose exists in the device, the device management server 101 does not perform a process to add a key pair because a key pair with a purpose of TLS is set as the purpose of the default key pair. Next, a case where the check box 701 on the setting screen for adding a key pair to a device (FIG. 7) is set to ON will be described. In a case where a key pair with the same purpose exists in the device and the purpose of the key pair to be added is to be prioritized, the device management server 101 deletes TLS from the purpose of the default key pair in order to add the key pair with a purpose of TLS that is instructed to be added. Table 3 shows the settings of the key pair of the device 102 after the addition process when the check box 701 is set to ON. In Table 3, a key pair with the name "printer03-tls" and a purpose of TLS is added to the device 102, and TLS is deleted from the purpose of the default key pair. [Table 3]

[0070] (Example 2) Next, a case will be described where device 102 (Table 1) is instructed to add the key pairs in Table 4. Table 4 shows the key pairs that device 102 is instructed to add. The key pairs that have been instructed to add are two key pairs: a key pair with the name "printer04-sip" whose purpose is set to SIP, and a key pair with the name "printer04-ipsec-sip" whose purpose is set to IPSec and SIP. [Table 4] In the example of Table 4, since the use of the key to be added, "SIP", is duplicated, the device management server 101 does not execute the addition process due to the processes in steps S802 and S803.

[0071] (Example 3) Table 5 shows the key pairs of the device 102 before it is added. Two key pairs are set in the device 102 before it is added: a default key pair and a key pair named "printer03-wifi-sip". The usage of the default key pair is set to TLS. The usage of printer03-wifi-sip is set to IEEE802.1X and SIP. [Table 5] Table 6 shows the key pair that has been instructed to be added to the device 102. The key pair that has been instructed to be added has the name "printer03-ipsec-sip" and has IPSec and SIP set as its purpose. [Table 6]

[0072] A case where a command is given to add a key pair shown in Table 6 to the device 102 to which the key pair shown in Table 5 is set will be described. First, a case where the check box 701 on the setting screen for adding a key pair to a device (FIG. 7) is set to OFF will be described. In a case where a setting is made such that if a key pair with the same purpose exists in the device, the key pair is not added, the device management server 101 does not perform the process of adding the key pair because a key pair for the "SIP" purpose exists in both the device and the key pair to be added. Next, a case where the check box 701 on the setting screen for adding a key pair to a device (FIG. 7) is set to ON will be described. In a case where the purpose of the key pair to be added is given priority, the device management server 101 deletes the SIP purpose from the purpose of the key pair with the name "printer03-ipsec-sip" set in the device 102 because the key pair to be added has the purpose of "SIP". Table 7 shows the setting of the key pair of the device 102 after the addition process when the check box 701 is set to ON. In Table 7, a key pair with the name "printer03-ipsec-sip" and uses IPSec and SIP is added to the device 102, and SIP is removed (released) from the uses of the key pair with the name "printer03-ipsec-sip". [Table 7]

[0073] Next, a process in which the device management server 101 deletes a key pair from the device 102 will be described. Fig. 11 is a diagram showing an example of a setting screen for deleting a key pair from a device. The key pair deletion setting screen is a screen provided by the device management server 101 for making settings for a process for deleting a key pair from the device 102. When "Delete key pair from device" is selected in the drop-down 403 on the key pair management screen (Fig. 4) and clicking of the execute button 404 is detected, the device management server 101 displays the key pair deletion setting screen.

[0074] The key pair deletion setting screen includes a table 1001, a delete button 1002, and a cancel button 1003. The table 1001 is a table for selecting a key to be deleted, and displays a list of key pairs registered in a device. The table 1001 displays a check box for selecting a key, the name of the key, its purpose, the subject, and the number of registered devices. Since the key pairs displayed in the table 1001 are key pairs registered in a device, key pairs with one or more registered devices are displayed in the table 1001. The user selects a key pair to be deleted from the list of key pairs registered in the device displayed in the table 1001, and checks the corresponding check box. When detecting a click of the delete button 1002 by the user, the device management server 101 starts a process of deleting the selected key pair for each device in which the key pair with the check box selected in the table 1001 is registered. When detecting a click of the cancel button 1003 by the user, the device management server 101 closes the key pair deletion setting screen.

[0075] 12 and 13 are flowcharts showing the process of deleting a key pair from a device. Here, an example will be described in which the device management server 101 deletes a key pair from the device 102. The process of deleting a key pair by the device management server 101 is realized by the CPU 201 of the device management server 101 calling up and executing a device management application program from memory (ROM 203 or external storage device 207). Therefore, the CPU 201 of the device management server 101 functions as a deleting unit that deletes the key pair from the device.

[0076] In step S1101, the device management server 101 acquires a list of key pairs that are designated for deletion in table 1001 on the key pair deletion setting screen (FIG. 11) and are recorded as being registered in the device 102. In step S1102, the device management server 101 acquires key pair information from the device 102 (the purpose of the default key pair and a list of key pairs already registered in the device 102).

[0077] In step S1103, the device management server 101 sequentially extracts key pairs from the list of key pairs to be deleted acquired in step S1101. The device management server 101 performs a key pair deletion process for the extracted key pairs in steps S1104 to S1109. In step S1104, the device management server 101 searches the list of key pairs registered in the device 102 for a key pair whose name and body match as a registered key pair to be deleted. In S1105, the device management server 101 determines whether or not a key pair whose name and body match as a registered key pair to be deleted is found in the list of key pairs registered in the device 102 as a result of the search in S1104. If a key pair whose name and body match as a registered key pair to be deleted is not found, the device management server 101 performs the process of step S1110. On the other hand, if a key pair whose name and body match the key pair to be deleted is found, the device management server 101 performs the process of step S1106.

[0078] In step S1106, the device management server 101 compares the usage of the key pair to be deleted with the key pair found in the search (the registered key pair to be deleted). In step S1107, the device management server 101 determines whether the usage matches based on the comparison result of step S1106. If the usage matches, the device management server 101 performs processing of step S1108. On the other hand, if the usage does not match, the device management server 101 performs processing of step S1109.

[0079] In step S1108, the device management server 101 deletes the found key pair (registered key pair to be deleted) from the list of key pairs registered in the device 102. In step S1109, from the list of key pairs registered in the device 102, among the uses of the found key pair (registered key pair to be deleted), the same use as the use of the key pair to be deleted is deleted. In other words, from the uses of the key pair (registered key pair to be deleted) whose name and body match those of the key pair to be deleted in the list of registered key pairs, only the use of the key pair to be deleted is deleted, and the key pair body and uses that are not included in the uses of the key pair to be deleted are left. For example, if the use of the key pair to be deleted is "SIP" and the uses of the found key pair (registered key pair to be deleted) are "IEEE 802.1X" and "SIP", the use "SIP" is deleted, and the use of the registered key pair to be deleted becomes "IEEE 802.1X".

[0080] In step S1110, the device management server 101 determines whether the deletion process has been performed on all of the key pairs instructed to be deleted obtained in step S1101, i.e., whether all of the key pairs to be deleted in step S1103 have been extracted. If the deletion process has been performed on all of the key pairs instructed to be deleted, the process proceeds to step S1111. On the other hand, if the deletion process has not been performed on all of the key pairs instructed to be deleted, i.e., if there are key pairs remaining in the list of key pairs to be deleted that have not been extracted, the process returns to step S1103.

[0081] In step S1111, the device management server 101 checks whether there has been any change to the key pair to be registered in the device 102. If there has been no change, this means that the key pair specified for deletion has not been registered in the device 102, and the device management server 101 ends this process. On the other hand, if there has been a change, that is, if the key pair or purpose has been deleted from the list of key pairs registered in the device 102, the device management server 101 performs the process of step S1112.

[0082] Regarding the use of the key pair, there is a key pair for a specific purpose that must be present in the device. Specifically, in this embodiment, there is a constraint that a key pair for TLS purpose must be present. In step S1112, the device management server 101 checks whether a key pair for TLS purpose, which is a key pair for a specific purpose that must be present in the device, exists in the list of key pairs registered in the device 102. In step S1113, the device management server 101 determines whether or not a key pair for TLS purpose exists in the list of registered key pairs as a result of the check in step S1112. If a key pair for TLS purpose exists in the list of registered key pairs, the device management server 101 performs the process of step S1115. On the other hand, if a key pair for TLS purpose does not exist in the list of registered key pairs, the device management server 101 performs the process of step S1114.

[0083] In step S1114, the device management server 101 sets the use of the default key pair to TLS, and the process proceeds to step S1115. In step S1115, registration instruction data to be sent to the device 102 is created based on the list of registered key pairs and the use of the default key pair. Finally, in step S1116, the device management server 101 sends the registration instruction data created in step S1115 to the device 102. The device 102 that has received the registration instruction data from the device management server 101 sets the key pair of the device 102 based on the received registration instruction data. This realizes the deletion of the key pair from the device 102 while complying with the constraints related to the key pair. This ends the key pair deletion process. After the key pair deletion process ends, the device management server 101 acquires key pair information from the device 102, and updates the list of key pairs (table 401) in the device management server 101, which is displayed on the key pair management screen (FIG. 4).

[0084] (Example 4) Table 8 shows the key pairs of the device 102 before it is deleted. Three key pairs are set in the device 102 before it is deleted: a default key pair, a key pair named "printer03-wifi", and a key pair named "printer03-ipsec". The purpose of the default key pair is set to TLS. The purpose of printer03-wifi is set to IEEE802.1X. In addition, the key pair body of printer03-wifi is set to KEY_III. The purpose of printer03-ipsec is set to IPSec. [Table 8] It is assumed here that an instruction has been given to delete the key pairs in Table 9. Table 9 shows the key pairs that have been instructed to be deleted from the device 102. [Table 9] The key pair instructed to be deleted has the name "printer03-wifi", the purpose is IPSec, and the key pair body is KEY_III. The name and body of the key pair instructed to be deleted match those of the third key pair in Table 8. The purpose of the key pair instructed to be deleted also matches that of the third key pair in Table 8. When a deletion process is performed for the key pair instructed to be deleted, the key pairs of the device 102 are as shown in Table 9. Table 9 shows the key pairs of the device 102 after deletion. Table 9 is obtained by deleting the third key pair from Table 8. Note that in Example 4, the key pair for TLS purpose was not targeted for deletion, so the default key continues to be set for TLS purpose from before deletion. [Table 10]

[0085] (Example 5) Table 8 shows the key pairs of the device 102 before it is deleted. Three key pairs are set in the device 102 before it is deleted: a default key pair, a key pair named "printer03-wifi", and a key pair named "printer03-tls". Nothing is set as the purpose of the default key pair. The purpose of printer03-wifi is set to IEEE802.1X. The purpose of printer03-tls is set to TLS. The key pair body of printer03-tls is set to KEY_IV. [Table 11] Table 11 shows the key pairs instructed to be deleted by the device 102. The key pair instructed to be deleted has the name "printer03-tls," its purpose is TLS, and its key pair body is KEY_IV. The name and body of the key pair instructed to be deleted match those of the third key pair in Table 8. In addition, the purpose of the key pair instructed to be deleted also matches that of the third key pair in Table 8. [Table 12] When the deletion process of the key pair instructed to be deleted is executed, the key pair of the device 102 becomes as shown in Table 12. Table 12 shows the key pair of the device 102 after deletion. In Table 12, the third key in Table 10 has been deleted, and TLS has been added to the default key usage. In Example 5, since the deletion of the key pair for TLS usage has been instructed, TLS usage is set for the default key pair. [Table 13]

[0086] (Example 6) Table 13 shows the key pairs of the device 102 before it is deleted. Three key pairs are set in the device 102 before it is deleted: a default key pair, a key pair named "printer03-wifi", and a key pair named "printer03-tls". Nothing is set as the purpose of the default key pair. The purposes of printer03-wifi are set to IEEE802.1X and IPSec. The purposes of printer03-tls are set to TLS. In addition, the key pair body of printer03-tls is set to KEY_III. [Table 14] Table 14 shows a key pair instructed to be deleted by the device 102. The key pair instructed to be deleted has the name "printer03-wifi", the purpose is IEEE802.1X, and the key pair body is KEY_III. The name and body of the key pair instructed to be deleted match those of the second key pair in Table 13. The purposes of the second key pair in Table 13 are set to IEEE802.1X and IPSec, but the purpose instructed to be deleted is only IEEE802.1X. Therefore, the purpose of "IEEE802.1X" is deleted from the key pair, and the key pair printer03-wifi is left as an IPSec purpose. Note that a difference between the purpose of the key pair instructed to be deleted (the key pair in the device management server 101) that matches the name and body and the purpose of the key pair set in the device occurs when, for example, a user sets the purpose of the key pair using the panel of the device or a WEB UI. As a result of the user adding IPSec to the uses of printer-03-wifi using the panel of the device 102 or the like, a difference has arisen between the key pair in the device management server 101 (where only "IEEE802.1X" is set as the use) and the key pair in the device. [Table 15]

[0087] When the deletion process for the key pair instructed to be deleted is executed, the key pair of the device 102 becomes as shown in Table 15. Table 15 shows the key pair of the device 102 after deletion. In Table 15, the purpose IEEE802.1X has been deleted from the second key in Table 13. Note that in Example 15, the key pair for TLS purpose was not targeted for deletion, so the TLS purpose remains set in printer03-tls, as it was before deletion. [Table 16]

[0088] As described above, according to the present embodiment, when a key pair is added, a choice is made as to whether or not to overwrite if a key pair with the same purpose exists. If overwriting is selected, it is possible to add a key pair even if a key pair with the same purpose already exists. When adding a key pair to overwrite an existing key pair, the same purpose as the purpose of the key pair to be added is deleted from the existing key pair, so that a key pair with the same purpose is not set in the device. In addition, when deleting a key pair, if a key for a specific purpose (e.g., TLS purpose) that must always exist in the device is deleted, the specific purpose can be set to a default key to ensure that a key pair with the specific purpose always exists in the device.

[0089] Second embodiment When adding multiple key pairs to a device, multiple key pairs with the same name and key pair body may exist in the list of key pairs to be added. Also, multiple key pairs with the same name and key pair body may exist in the list of key pairs already registered in the device. Such multiple key pairs can be integrated into one key pair with a name and key pair body whose purpose is the union of the purposes of each key pair. In this embodiment, the integration of key pairs will be described.

[0090] Here, a specific situation where the key pair merging process is executed will be described. First, the use of the key pair list merging process in the key pair addition process will be described. When the device management server 101 acquires a list of key pairs to be added in the key addition process, it merges the list of key pairs to be added (step S801). Moreover, the device management server 101 executes the merging process instead of duplicating the list of key pairs of the device (step S901). Then, the device management server 101 handles the list of key pairs after the merge in step S901 as a list of key pairs to be registered. Next, the use of the key pair list merging process in the key pair deletion process will be described. The device management server 101 executes the merging process on the list of key pairs acquired from the device, and uses the list after the merge as a list of registered key pairs (step S1102).

[0091] 14 is a flowchart showing the process of integrating the lists of key pairs. The process of integrating the lists of key pairs by the device management server 101 is realized by the CPU 201 of the device management server 101 calling up a device management application program from memory (the ROM 203 or the external storage device 207) and executing it.

[0092] When starting the process of integrating the key pair lists, a list of key pairs to be integrated is input to the device management server 101. In step S1201, the device management server 101 creates an empty key pair list for storing the list of key pairs after integration. Next, in step S1202, the device management server 101 sequentially extracts key pairs from the input list of key pairs to be integrated. The device management server 101 performs the processes of steps S1203 to S1206 on the extracted key pairs.

[0093] In step S1203, the device management server 101 searches the list of integrated key pairs for a key pair having the same name and key pair body as the extracted key pair. In step S1204, the device management server 101 determines whether a key pair having the same name and key pair body has been found as a result of the search in step S1203. If a key pair having the same name and key pair body is not found as a result of the search, the device management server 101 performs processing in step S1205. On the other hand, if a key pair having the same name and key pair body is found as a result of the search, the device management server 101 performs processing in step S1206.

[0094] In step S1205, the device management server 101 adds the extracted key pair to the list of key pairs after integration. In step S1206, the device management server 101 adds the purpose of the extracted key pair to the purpose of the key pair in the list of key pairs after integration. If there is no purpose to add, that is, if the purpose of the extracted key pair is the same as the purpose of the key pair in the list of key pairs after integration, the device management server 101 does not add the purpose. In step S1107, the device management server 101 checks whether the processing for all key pairs in the list of key pairs to be integrated is completed. If the processing for all key pairs in the list of key pairs to be integrated is completed, that is, if all key pairs in the list of key pairs to be integrated are extracted in step S1202, the device management server 101 performs the processing of step S1208. On the other hand, if the processing for all key pairs in the list of key pairs to be integrated is not completed, the process returns to the processing of step S1202. In step S1208, the device management server 101 returns the list of key pairs after integration to the caller and ends the processing.

[0095] Table 16 shows the key pair lists to be merged. The key pair list that has been instructed to be merged contains two key pairs named "printer05-one" and one key pair named "printer05-two". The purpose of the first key pair for "printer05-one" is set to IEEE802.1X and IPSec. The purpose of the second key pair for "printer05-one" is set to IEEE802.1X and SIP. The purpose of the key pair for "printer05-two" is set to TLS. [Table 17] When the merge process is performed on the list in Table 16, it results in the list in Table 17. Table 17 shows the key pair list after the merge process. As a result of the merge process, the key pair named "printer05-one" has been merged. The printer05-one key pair has three set uses: IEEE802.1X, IPSec, and SIP. [Table 18]

[0096] As described above, according to this embodiment, the device management server 101 can perform an integration process on a list of key pairs to be added and a list of key pairs already registered in a device. By integrating the lists of key pairs, the number of processes to be performed in subsequent search processes and the like can be reduced.

[0097] The disclosure of this embodiment includes the following configuration of a device management apparatus. (Configuration 1) A device management apparatus for managing a key pair set in a network device to be managed via a network, comprising: a selection means for accepting a selection as to whether or not to overwrite a key pair instructed to be added to a network device with a key pair having the same purpose as that of the key pair instructed to be added to the network device when the key pair is already set in the network device; and an adding means for, when an option to overwrite with the key pair instructed to be added has been accepted, deleting the same use as the key pair instructed to be added from the uses of the key pairs set in the network device, and adding the key pair instructed to be added. (Configuration 2) the adding means acquires from the network device a use of a default key and a list of key pairs registered in the network device, creates a list of key pairs to be registered in the network device based on the acquired list of key pairs registered in the network device, and adds the key pair instructed to be added to the created list of key pairs to be registered; When a selection to overwrite with the key pair instructed to be added has been accepted, the adding means deletes the same purpose as the purpose of the key pair instructed to be added from the purpose of the key pair set in the network device in the list of key pairs to be registered and the purpose of the default key; The device management apparatus according to claim 1, characterized in that the adding means creates key pair registration instruction data based on the list of key pairs to be registered and the purpose of the default key, and adds the key pair by sending the registration instruction data to the network device. (Configuration 3) The device management apparatus according to configuration 2, wherein the adding means, after deleting the same purpose as the key pair instructed to be added, checks whether the list of key pairs to be registered includes a key pair with a specific purpose that must be present in the network device, and if there is no key pair with the specific purpose, adds the specific purpose to the purposes of a default key. (Configuration 4) The key pair is a public key and a private key pair for communication encryption, 4. The device management apparatus according to configuration 3, wherein the predetermined use of the key pair is use by the network device for TLS (Transport Layer Security). (Configuration 5) 5. The device management apparatus according to claim 1, wherein the network device is an image forming apparatus. (Configuration 6) the selection means displays, on a screen for setting addition of a key pair to the network device, whether or not to overwrite a key pair having the same purpose as that of the key pair instructed to be added, to allow the user to select, The device management apparatus according to any one of configurations 1 to 5, wherein the adding means does not add the key pair instructed to be added if a key pair with the same purpose exists among the key pairs instructed to be added. (Configuration 7) A device management apparatus for managing a key pair set in a network device to be managed via a network, comprising: a deletion means for deleting the key pair instructed to be deleted from the network device; A device management device characterized in that, when a key pair for a specific purpose that must be present in a network device is deleted, the deletion means adds the specific purpose to the purpose of the default key of the network device. (Configuration 8) The deletion means acquires from the network device a list of uses of the default key and key pairs registered in the network device, When the list of registered key pairs contains a key pair whose name and body match those of the key pair instructed to be deleted, the deletion means deletes the key pair from the list of registered key pairs if the usage of the key pair matches that of the key pair instructed to be deleted, and deletes only the usage of the key pair instructed to be deleted from the list of registered key pairs if the usage of the key pair does not match that of the key pair instructed to be deleted, When the list of registered key pairs does not include a key for the predetermined purpose, the deletion means adds the predetermined purpose to the purpose of a default key of the network device; The device management apparatus according to configuration 7, wherein the deletion means creates registration instruction data for a key pair based on the list of registered key pairs and the purpose of the default key, and deletes the key pair by sending the registration instruction data to the network device. (Configuration 9) The key pair is a public key and a private key pair for communication encryption, 9. The device management apparatus according to configuration 7 or 8, wherein the predetermined use of the key pair is use by the network device for TLS (Transport Layer Security).

[0098] (Other embodiments) The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions.

[0099] Although the preferred embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and various modifications and changes are possible within the scope of the gist of the present invention.

Claims

1. A device management apparatus for managing a key pair set in a network device to be managed via a network, comprising: a selection means for accepting a selection as to whether or not to overwrite a key pair instructed to be added to a network device with a key pair having the same purpose as that of the key pair instructed to be added to the network device when the key pair is already set in the network device; an adding means for, when a selection to overwrite with the key pair instructed to be added has been accepted, deleting a use that is the same as the key pair instructed to be added from the uses of the key pairs set in the network device, and adding the key pair instructed to be added, a network device management apparatus including a network device management unit that manages a network environment by storing a key pair in a network device and a network interface that manages a network device and a network interface that manages a network device and a network interface that manages a network device and a network interface that manages a network device and a network interface that manages a network device and a network interface that manages a network device and a network interface that manages a network device and a network interface that manages a network device and a network device,

2. the adding means acquires from the network device a use of a default key and a list of key pairs registered in the network device, creates a list of key pairs to be registered in the network device based on the acquired list of key pairs registered in the network device, and adds the key pair instructed to be added to the created list of key pairs to be registered; When a selection to overwrite with the key pair instructed to be added has been accepted, the adding means deletes the same purpose as the purpose of the key pair instructed to be added from the purpose of the key pair set in the network device in the list of key pairs to be registered and the purpose of the default key; The device management apparatus according to claim 1, characterized in that the adding means creates key pair registration instruction data based on the list of key pairs to be registered and the purpose of the default key, and adds the key pair by sending the registration instruction data to the network device.

3. 3. The device management apparatus according to claim 2, wherein the adding means, after deleting the same use as the key pair instructed to be added, checks whether the list of key pairs to be registered contains a key pair with a specific use that must be present in the network device, and if there is no key pair with the specific use, adds the specific use to the uses of a default key.

4. The key pair is a public key and a private key pair for communication encryption, 4. The device management apparatus according to claim 3, wherein the predetermined use of the key pair is use by the network device for TLS (Transport Layer Security).

5. 2. The device management apparatus according to claim 1, wherein the network device is an image forming apparatus.

6. the selection means displays, on a screen for setting addition of a key pair to the network device, whether or not to overwrite a key pair having the same purpose as that of the key pair instructed to be added, to allow the user to select, 2. The device management apparatus according to claim 1 , wherein the adding unit does not add the key pair instructed to be added if a key pair having the same purpose is present among the key pairs instructed to be added.

7. A device management apparatus for managing a key pair set in a network device to be managed via a network, comprising: a deletion means for deleting the key pair instructed to be deleted from the network device; A device management apparatus characterized in that, when a key pair for a specific purpose that must be present in a network device is deleted, the deletion means adds the specific purpose to the purpose of the default key of the network device.

8. The deletion means acquires from the network device a list of uses of the default key and key pairs registered in the network device, When the list of registered key pairs contains a key pair whose name and body match those of the key pair instructed to be deleted, the deletion means deletes the key pair from the list of registered key pairs if the usage of the key pair matches that of the key pair instructed to be deleted, and deletes only the usage of the key pair instructed to be deleted from the list of registered key pairs if the usage of the key pair does not match that of the key pair instructed to be deleted, When the list of registered key pairs does not include a key for the predetermined purpose, the deletion means adds the predetermined purpose to the purpose of a default key of the network device; The device management apparatus according to claim 7, characterized in that the deletion means creates key pair registration instruction data based on the list of registered key pairs and the use of the default key, and deletes the key pair by sending the registration instruction data to the network device.

9. The key pair is a public key and a private key pair for communication encryption, 9. The device management apparatus according to claim 7, wherein the predetermined use of the key pair is use by the network device for TLS (Transport Layer Security).

10. A method for controlling a device management apparatus for managing a key pair set in a network device to be managed via a network, comprising: receiving a selection as to whether or not to overwrite a key pair set in the network device with the key pair instructed to be added to the network device when the key pair has the same purpose as that of the key pair instructed to be added to the network device; and when a selection to overwrite the key pair instructed to be added has been accepted, deleting the same use as the key pair instructed to be added from the uses of the key pairs set in the network device, and adding the key pair instructed to be added; a network device management apparatus that manages a network connection between the network device and the network management system and a user of the network, the network device managing the network connection being connected to the network, and a network device that manages the network connection between the network device and the network, the network device managing the network connection being connected to the network, and the network device managing the network connection being connected to the network,

11. A method for controlling a device management apparatus for managing a key pair set in a network device to be managed via a network, comprising: deleting the designated key pair from the network device; 1. A method for controlling a device management apparatus, comprising the steps of: when a key pair for a specific purpose is deleted, adding the specific purpose to the purpose of a default key of the network device.

12. A program for causing a computer to execute the steps according to claim 10.

13. A program for causing a computer to execute the steps according to claim 11.

Images