JP2009159053A - Information processing apparatus, certificate control method, and certificate control program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an information processing apparatus, a certificate control method and a certificate control program, capable of properly controlling digital certificates in an environment where a plurality of applications utilize digital certificates. <P>SOLUTION: The information processing apparatus having a plurality of applications each performing communication using digital certificates has a control means for controlling the correlation between the applications and the digital certificate for each of the plurality of applications, wherein the applications each utilize the correlated digital certificate in the control means. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to an information processing apparatus, a certificate management method, and a certificate management program, and more particularly to an information processing apparatus having an application that uses a digital certificate, a certificate management method, and a certificate management program.

  In recent years, with the development and popularization of networks such as the Internet and LAN, multifunction devices have communication functions. A multifunction device having a communication function can be connected to an external device via a network.

  In this way, MFPs that can be connected to external devices have mechanisms such as access control that prohibits unauthorized access from users who do not have the right to use, digital signatures that prevent impersonation and tampering, and encryption that prevents eavesdropping. It has been demanded. Therefore, in the past, spoofing and tampering are prevented by performing communication using a digital certificate.

By the way, although a plurality of applications for performing communication can be mounted on the multifunction peripheral, conventionally, management of digital certificates has been performed for each application.
JP 2004-320715 A JP 2005-039790 A JP 2007-174314 A

  However, when a digital certificate is performed for each application, there is a problem that implementation of the application and use of resources of the multifunction machine become very inefficient. That is, there is a high possibility that almost the same implementation of digital certificate management is duplicated in each application. In addition, even if the same digital certificate is used by each application, there is no common recognition among applications, so a digital certificate is introduced separately, and a storage area for the multifunction device is required. It will consume more.

  The present invention has been made in view of the above points, and is an information processing apparatus and certificate management capable of appropriately managing digital certificates in an environment in which a plurality of applications using digital certificates exist. The purpose is to provide a method and certificate management program.

  Therefore, in order to solve the above-described problem, the present invention provides an information processing apparatus having a plurality of applications that perform communication using digital certificates, and manages the association of each of the plurality of applications with a digital certificate. And the application uses a digital certificate associated with the management means.

  In such an information processing apparatus, it is possible to appropriately manage digital certificates in an environment where a plurality of applications using digital certificates exist.

  According to the present invention, it is possible to provide an information processing apparatus, a certificate management method, and a certificate management program capable of appropriately managing a digital certificate in an environment where there are a plurality of applications using the digital certificate. it can.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the present embodiment, a multifunction peripheral will be described as an example of an information processing apparatus. The multifunction machine 1 is an image forming apparatus that realizes a plurality of functions such as a printer, a copy, a scanner, or a fax in a single housing.

  FIG. 1 is a diagram illustrating an example of a hardware configuration of a multifunction machine according to an embodiment of the present invention. As the hardware of the multifunction device 1, there are a controller 601, an operation panel 602, a facsimile control unit (FCU) 603, an imaging unit 604, and a printing unit 605.

  The controller 601 includes a CPU 611, ASIC 612, NB621, SB622, MEM-P631, MEM-C632, HDD (hard disk drive) 633, memory card slot 634, NIC (network interface controller) 641, USB device 642, IEEE 1394 device 643, Centronics device. 644.

  The CPU 611 is an IC for various information processing. The ASIC 612 is an IC for various image processing. The NB 621 is a north bridge of the controller 601. The SB 622 is a south bridge of the controller 601. The MEM-P 631 is a system memory of the multifunction device 1. The MEM-C 632 is a local memory of the multifunction machine 1. The HDD 633 is storage of the multifunction device 1. The memory card slot 634 is a slot for setting a memory card 635. The NIC 641 is a controller for network communication using a MAC address. The USB device 642 is a device for providing a USB standard connection terminal. The IEEE 1394 device 643 is a device for providing a connection terminal of the IEEE 1394 standard. The Centronics device 644 is a device for providing connection terminals of Centronics specifications. The operation panel 602 is hardware (operation device) for an operator to input to the multifunction device 1 and hardware (display device) for an operator to obtain an output from the multifunction device 1.

  FIG. 2 is a diagram illustrating a software configuration example of the multifunction peripheral according to the embodiment of the present invention.

  In FIG. 1, the multifunction machine 1 includes an OS (Operating System) 101, a J2ME (Java (registered trademark) 2 Micro Edition) 102, an OSGi (Open Services Gateway Initiative) framework 103, a bundle 104, a native code 105, and the like. Is done.

  The OS 101 is a so-called OS (Operating System). The J2ME 102 is a Java (registered trademark) platform that provides a Java (registered trademark) execution environment and the like. The J2ME 102 in the present embodiment adopts CDC (Connected Device Configuration) as an assumed execution environment (configuration), and employs the JVM 1021 as a Java (registered trademark) virtual machine. The JVM 1021 converts the byte code into a native code that can operate on the OS 101 and executes it.

  The OSGi framework 103 is a standardized technology by the OSGi Alliance, and is a software platform that provides an execution environment for software components created based on an open software componentization technology based on the Java (registered trademark) language. On the OSGi framework 103, Java (registered trademark) language software is implemented in the form of software components called "bundles". One bundle is constituted by one JAR (Java (registered trademark) ARchive) file, and can be installed dynamically independently (without restarting the apparatus). The bundle 104 indicates such a bundle. There may be a plurality of bundles 104. The native code 105 is a program that operates directly on the OS 101 and is created by C language or the like, for example.

  In the multi function device 1, each software component is mounted as a bundle 104, a native code 105, or a normal (non-bundle) JAR file. FIG. 3 is a diagram illustrating a configuration example of software components of the multifunction machine according to the embodiment of the present invention.

  As shown in the figure, software components (hereinafter simply referred to as “components”) in the multifunction device 1 are classified into layers such as an application mechanism 10, a service mechanism 20, a device mechanism 30, and an aspect layer 40. The vertical relationship between layers in the figure is based on the call relationship between layers. Basically, the upper layer in the figure calls the lower layer. That is, in FIG. 3, component relationships are organized and shown based on the call relationship between the bundle 104 or the native code 105. Each component is stored in, for example, the HDD 633 and is loaded into the MEM-P 631 at the time of execution to cause the CPU 611 to execute the function.

  The application mechanism 10 includes a component for allowing a user to use resources such as functions provided by the multifunction machine 1 or information (data). In the figure, a printer application 11, a PCFAX application 12, a document storage application 13, and the like are illustrated.

  The printer application 11 executes print processing (print job) in response to a print request transmitted from a PC or the like connected via a network. The PCFAX application 12 executes a FAX transmission process (FAX transmission job) in response to a FAX transmission request transmitted from a PC or the like connected via a network. The document storage application 13 controls processing for storing the image data scanned by the imaging unit 604 in the HDD 633.

  The service mechanism 20 includes components that provide more basic functions (services) that are commonly used than the components belonging to the application mechanism 10. In the figure, a scan service 21, a plotter service 22, a stored document service 23, a user repository service 24, a UI service 25, a memory service 26, a communication service 27, and the like are illustrated.

  The scan service 21 controls image data reading processing using the imaging unit 604. The plotter service 22 controls image data printing processing using the printing unit 605. The stored document service 23 controls storage or reading of image data in the HDD 633. The user repository service 24 manages user information (account information, address book information, etc.) recorded in the HDD 633. The UI service 25 generates a screen to be displayed on an operation panel 602 or a PC (Personal Computer) connected via a network. The communication service 27 controls communication using various protocols.

  The device mechanism 30 includes a component generally called a device driver that controls a device provided in the multifunction machine 1.

  The aspect layer 40 includes transverse components that are commonly used by the application mechanism 10, the service mechanism 20, and the device mechanism 30. In the figure, the aspect layer 40 includes a certificate status management unit 41, a certificate alias management unit 42, a device certificate storage unit 43, a CA certificate storage unit 44, and the like.

  The certificate status management unit 41 manages the status of the device certificate. Here, the device certificate is used to prove that the creator of the communication data is the multifunction device 1 and that the communication data has not been tampered with when the multifunction device 1 performs network communication. A digital certificate such as a public key certificate. In the present embodiment, it is called a “device certificate” in order to avoid confusion with a CA certificate described later. The device certificate is issued as a self-signed certificate in the device, or issued and signed by a certificate authority (CA) and introduced into the multifunction device 1. The status of the device certificate refers to information indicating whether or not a device certificate has been installed. More specifically, in the present embodiment, five areas (hereinafter referred to as “device certificate storage areas”) are prepared in advance as storage areas for storing device certificates. The device certificate status refers to information indicating whether or not a device certificate has been introduced to each device certificate storage area. Each device certificate storage area has a name (identification name), and the name is treated as an alias for the device certificate stored in each device certificate storage area. Therefore, specifically, the certificate status management unit 41 manages information indicating whether a device certificate is introduced for each alias.

  The introduction of the device certificate is executed via the device certificate operation screen. FIG. 4 is a diagram showing a display example of the device certificate operation screen. In the figure, the device certificate operation screen 510 includes a list 511, a create button 512, a request button 513, an introduction button 514, a delete button 515, an export button 516, a use application setting button 517, and the like.

  The list 511 displays an alias, an issuer, an issuer, an expiration date, a certificate status, and the like for each device certificate (device certificate storage area for storing a device certificate). The alias is the alias (alias) of the device certificate or the name of the device certificate storage area. The issuer, issuer, and expiration date are the issuer, issuer, and expiration date of the device certificate. The certificate status indicates whether or not a device certificate has been installed in the multifunction device 1 (that is, the status of the device certificate).

  When the creation button 512 is pressed, processing for newly creating a device certificate (received from the CA) is started. When the request button 513 is pressed, a certificate request creation process for receiving a signature from an arbitrary CA is started. When the introduction button 514 is pressed, a process for introducing the created device certificate into the device certificate storage area related to the row where the check button is checked in the list 511 is started. When the export button 516 is pressed, a process for exporting the public key of the device certificate related to the checked line is started. When the use application setting button 517 is pressed, processing for setting an application that uses each device certificate is started. Here, the application mainly refers to various software components belonging to the communication service 27 and refers to an application that performs secure communication using a device certificate.

  The certificate alias management unit 42 manages the association between the alias (alias) of each device certificate and the application that uses the certificate. In the present embodiment, one device certificate can be used from a plurality of applications. The association is set on the use application setting screen displayed when the use application setting button 517 is pressed on the device certificate operation screen 510.

  FIG. 5 is a diagram illustrating a display example of the use application setting screen. In the use application setting screen 520a shown in the figure, a device certificate to be used can be selected from a pull-down list for each application. On the pull-down list, a list of alias names of installed device certificates or a list of names of device certificate storage areas regardless of whether they are installed or not are displayed.

  The device certificate storage unit 43 saves the device certificate in a storage medium (for example, the HDD 633), reads out from the storage medium, and the like. However, the storage medium is preferably a secure device.

  The CA certificate storage unit 44 stores a CA (Certificate Authority) certificate in a storage medium, reads out from the storage medium, and the like. Here, the CA certificate refers to a digital certificate such as a CA that has issued a device certificate. Here, “CA etc.” means each CA such as an intermediate certificate authority and a root certificate authority. Therefore, the CA certificate storage unit 44 manages a list of CA certificates.

  In the present embodiment, attention is particularly paid to functions realized by the components in the aspect layer 40. A processing procedure executed in the multifunction machine 1 regarding the function will be described below.

  First, processing executed to generate a GUI (Graphical User Interface) such as the device certificate operation screen 510 and the usage certificate setting screen 520a will be described. FIG. 6 is a sequence diagram for explaining a process of collecting information necessary for creating each screen.

  First, each application 51 using one of the device certificates has its identification information (for example, application name) for the certificate status management unit 41 at a predetermined timing (for example, when the application is installed). ) Is registered (S101 to S103). Therefore, the certificate status management unit 41 manages a list of application names.

  Subsequently, the UI service 25 executes the following processing when a display of the device certificate operation screen 510 or the like is requested or before that. First, the UI service 25 acquires a list of application names using the device certificate from the certificate status management unit 41 (S104, S105).

  Subsequently, the UI service 25 requests the certificate alias management unit 42 to obtain a list of names of device certificate storage areas (that is, aliases of device certificates regardless of whether they have been installed or not installed). (S106). The certificate alias management unit 42 acquires the name added to each device certificate storage area on the storage medium in which the device certificate is stored from the storage medium (S107, S108), and displays a list of the acquired names. The list of aliases is returned to the UI service 25 (S109).

  Subsequently, the UI service 25 designates one alias included in the acquired list of aliases, and information on the device certificate (or device certificate storage area) related to the alias (hereinafter referred to as “certificate information”). .) Is inquired of the device certificate storage unit 43 (S110). The device certificate storage unit 43 acquires the certificate information of the device certificate related to the designated alias from the storage medium (S111, S112). The certificate information includes whether or not it has been introduced, an issuer, an issuer, an expiration date, and the like. Among these, the issuer, the issuer, and the expiration date are acquired only when the device certificate has been introduced. The device certificate storage unit 43 returns the acquired certificate information to the UI service 25 (S113). Note that the processes in steps S110 to S113 are repeated by the number of aliases included in the list of aliases acquired in step S109 (S110-n to S113-n).

  Based on the information acquired by the above processing, the UI service 25 generates the device certificate operation screen 510 and the use application setting screen 520a when the display of these screens is requested. For example, the device certificate operation screen 510 is generated based on the list of aliases acquired in step S109 and the certificate information acquired in steps S110 to S113. In addition, the use application setting screen 520a is generated based on the application list acquired in step S105 and the alias list acquired in step S109. That is, on the use application setting screen 520a, the list of aliases acquired in step S109 is set in the list box arranged for each application. The device certificate operation screen 510, the use application setting screen 520a, and the like are generated as, for example, Web pages (HTML data) and are connected to the operation panel 602 or the multifunction device 1 via a network (Personal Computer). Displayed on a computer display device.

  Next, a processing procedure when a device certificate is introduced will be described. FIG. 7 is a sequence diagram for explaining a processing procedure when a device certificate is introduced.

  In the device certificate operation screen 510, when the check button 518 related to the unintroduced row is checked and the introduction button 514 is pressed, the certificate introduction screen is displayed under the control of the UI service 25. On the certificate introduction screen, a device certificate to be introduced is selected. The device certificate to be introduced is issued in advance by the CA when the creation button 512 is pressed, and is stored together with the certificate information. However, in this state, the device certificate cannot be used by the application. By the act of introduction, the device certificate can be associated with the application, and thus can be used from the application.

  When a device certificate to be introduced is specified on the certificate introduction screen, the UI service 25 requests the device certificate storage unit 43 to store the device certificate and its certificate information using an alias as a key (S201). ). The device certificate storage unit 43 inquires about the installation status of the device certificate related to the designated alias (S202). The certificate status management unit 41 acquires the introduction status for the device certificate storage area related to the alias (S203), and returns the result to the device certificate storage unit 43 (S204).

  When the device certificate has not been introduced for the alias, the device certificate storage unit 43 stores the device certificate to be introduced and its certificate information in the device certificate storage area related to the alias in the recording medium ( S205). Subsequently, the device certificate storage unit 43 requests the certificate status management unit 41 to change the device certificate related to the alias to already installed (S206). In response to the request, the certificate status management unit 41 updates the installation status for the alias to installed.

  If it is returned in step S204 that introduction has been completed, a plurality of device certificates cannot be introduced for the same alias, so step S205 and subsequent steps are not executed, and an error is returned to the UI service 25. Is done.

  Next, a processing procedure when an association between an application and a device certificate is requested via the use application setting screen 520a will be described. FIG. 8 is a sequence diagram for explaining a processing procedure when associating a device certificate.

  When the device certificate alias for each application is selected by operating the pull-down list on the use application setting screen 520a and the registration button 521 is pressed, the UI service 25 sets the application name and the application name according to the installation contents on the screen. A pair with an alias is designated, and the certificate alias management unit 42 is requested to associate with the pair (S301). The certificate alias management unit 42 saves information indicating the association between the application name and the alias associated with the specified combination in the storage medium (S302).

  Next, a processing procedure when a device certificate is used by an application will be described. FIG. 9 is a sequence diagram for explaining a processing procedure when using a device certificate.

  When it is necessary to use the device certificate, the application 51 designates its own identification information (application name) and inquires of the alias management unit 42 about the alias of the device certificate associated with the application 51 (S401). The alias management unit 42 acquires an alias associated with the designated application name based on the information recorded on the recording medium (information stored in step S302 in FIG. 8) (S403), and the alias Is returned to the application 51 (S404).

  Subsequently, the application 51 designates the acquired alias name and requests the device certificate storage unit 43 to acquire the device certificate (S405). The device certificate storage unit 43 specifies an alias name and inquires of the certificate status management unit 41 about the installation status of the device certificate (S406). The certificate status management unit 41 acquires the introduction status for the device certificate storage area related to the alias (S407), and returns the result to the device certificate storage unit 43 (S408).

When the device certificate has been introduced, the device certificate storage unit 43 acquires the device certificate from the device certificate storage area related to the alias in the storage medium (S409, S410),
The acquired device certificate is returned to the application 51 (S411). Thereafter, the application 51 that has acquired the device certificate executes communication or the like using the device certificate.

  Incidentally, in the use application setting screen 520a shown in FIG. 5, only one device certificate can be associated with one application. Therefore, the use application setting screen may be configured as follows.

  FIG. 10 is a diagram illustrating a display example of the second use application setting screen. In the use application setting screen 520b shown in the figure, for each device certificate, a check button for setting whether or not the certificate can be used (or necessity) is arranged for each application. According to such a configuration, a plurality of device certificates can be set as usage targets for each application. For example, certificate 1 and certificate 3 are set as usage targets for “SSL / TLS” in the figure.

  Moreover, FIG. 11 is a figure which shows the example of a display of a 3rd utilization application setting screen. In the use application setting screen 530c shown in FIG. 6, the device certificate recommended for use for each application is indicated by “◎”. Which device certificate is recommended may be set, for example, when an application is installed, and ◎ may be displayed based on the setting. According to such a configuration, it is possible to provide a criterion for determination when the user makes settings. If a device certificate different from the recommended device certificate is selected (checked), the following screen may be displayed.

  FIG. 12 is a diagram illustrating a display example of a certificate selection confirmation screen. As shown in the figure, the certificate selection confirmation screen 530 displays a message indicating that “certificate 1” is recommended for S / MIME. When a message different from the recommended device certificate is selected by the message, it is possible to call attention. It should be noted that, on the use application setting screens 520a to 520c, etc., an association between an unintroduced device certificate (device certificate storage area) and an application may be performed. In this case, the device certificate is introduced after the association. However, by enabling such a setting, it is possible to give flexibility to a series of operations of introduction and association.

  As described above, according to the MFP 1 in the present embodiment, the device certificate used by a plurality of applications by the certificate status management unit 41, the certificate alias management unit 42, the device certificate storage unit 43, and the like. The certificate alias management unit 42 manages the association between the application and the device certificate.

  Therefore, redundant management of device certificates can be avoided. Also, the device certificate cannot be selected depending on the application, and the associated device certificate can be forcibly used, so that security can be improved.

  For example, the alias may be changeable on the device certificate operation screen 510 or the like.

  Next, handling of the CA certificate in the multifunction machine 1 will be described. Information regarding the CA certificate is managed as a property value of the JVM 1201. Each application can obtain the property value by making an inquiry to the JVM 1201.

FIG. 13 is a diagram conceptually showing properties in the JVM. As shown in the figure, for example, values such as SSL cipher suites property p1, CA certificate access password property p2, and CA certificate storage location property p3 are set as property values. The value of the SSL cipher suites property p1 indicates a recommended value of the encryption type (method) when performing SSL (Secure Socket Layer) communication. The value of the CA certificate access password property p2 indicates a password required to access the CA certificate. The value of the CA certificate storage location property p3 indicates the storage location of the CA certificate. The property value can be set by a “setProperty ()” method. Property value acquisition can be performed by the “getProperty ()” method. Property value handling (setting in the JVM 1201, etc.) is performed using a Java (registered trademark) encryption extension function (JCE (Java (registered trademark) Cryptography Extension)). ) Provider. FIG. 14 is a diagram showing a JCE provider. JCE shown in the J2ME 102 in the figure is an extension function of the Java (registered trademark) standard, and provides means for arbitrarily extending the implementation for a predetermined interface. The extended implementation is called a provider. In the present embodiment, an example in which handling of the property value is implemented in the provider 107 will be described.

  FIG. 15 is a sequence diagram for explaining the property value setting and reference processing procedures.

  When a program module calls a cryptographic function via the JCE 1022 (S501), the call is delegated to the provider 107 (S502). In response to the call, the provider 107 sets the values of the properties p1, p2, and p3 for the JVM 1021 (S503).

  Subsequently, when a certain program module (which may not be the same as the program module according to step S501) requests the JVM 1021 to reference the value of the property p1, p2, or p3 (S504), the JVM 1021 The value set in is returned (S505).

  In this way, by setting the property value to the provider, the property value can be set when a call related to the encryption function is made without making the higher-level program module aware of the property value setting. . Note that the call in step S501 is also performed when the JVM 1021 is activated. Therefore, each property value is set at least before the reference is requested by the application 51 or the like.

  For example, FIG. 16 is a sequence diagram for explaining a processing procedure during SSL encryption communication.

  When an application 51 calls the SSL encryption communication function via the JCE 1022 (S601), the call is delegated to the provider 107 (S602). In response to the call, the provider 107 sets the value of the SSL cipher suites property p1 in the JVM 1021 (S603). Subsequently, the JCE 1022 acquires the value of the SSL cipher suites property p1 from the JVM 1021 (S604, S605), and enables SSL communication by the encryption method specified for the value (S606).

  When SSL encryption communication is requested through JSSE (Java (registered trademark) Secure Socket Extension), values such as the CA certificate storage location property p3 and the SSL encryption Suites property p1 are used in JSSE. Therefore, it is possible to prevent communication by an arbitrary encryption method of the upper application. Therefore, when the configuration is such that an application can be freely added (by a third party or the like) as in the multi-function device 1 according to the present embodiment, it is possible to appropriately ensure security regarding network communication.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to such specific embodiment, In the range of the summary of this invention described in the claim, various deformation | transformation・ Change is possible.

FIG. 2 is a diagram illustrating an example of a hardware configuration of a multifunction machine according to an embodiment of the present invention. FIG. 3 is a diagram illustrating a software configuration example of a multifunction machine according to an embodiment of the present invention. 2 is a diagram illustrating a configuration example of software components of a multifunction machine according to an embodiment of the present invention. It is a figure which shows the example of a display of an apparatus operation screen. It is a figure which shows the example of a display of a utilization application setting screen. It is a sequence diagram for demonstrating the collection process of the information required for creation of each screen. It is a sequence diagram for demonstrating the process sequence at the time of the introduction of a device certificate. It is a sequence diagram for demonstrating the process sequence at the time of the correlation of a device certificate. It is a sequence diagram for demonstrating the process sequence at the time of apparatus certificate utilization. It is a figure which shows the example of a display of a 2nd utilization application setting screen. It is a figure which shows the example of a display of a 3rd utilization application setting screen. It is a figure which shows the example of a display of a certificate selection confirmation screen. It is a figure which shows the property in JVM notionally. It is a figure which shows the provider of JCE. FIG. 10 is a sequence diagram for explaining a property value setting and reference processing procedure; It is a sequence diagram for demonstrating the process sequence at the time of SSL encryption communication start.

Explanation of symbols

1 MFP 10 Application mechanism 11 Printer application 12 PCFAX application 13 Document storage application 20 Service mechanism 21 Scan service 22 Plotter service 23 Document storage service 24 User repository service 25 UI service 26 Memory service 27 Communication service 30 Device mechanism 40 Aspect layer 41 Certification Certificate status management unit 42 Certificate alias management unit 43 Device certificate storage unit 44 CA certificate storage unit 101 OS
102 J2ME
103 OSGi Framework 104 Bundle 105 Native Code 271 Print Server 272 Mail Receiving Server 273 FAX Server 274 HTTP Server 275 Mail Transfer Client 276 FAX Communication Client 277 File Transfer Client 601 Controller 602 Operation Panel 603 Facsimile Control Unit 604 Imaging Unit 605 Printing Unit 611 CPU
612 ASIC
621 NB
622 SB
631 MEM-P
632 MEM-C
633 HDD
634 Memory card slot 635 Memory card 641 NIC
642 USB device 643 IEEE 1394 device 644 Centronics device 1021 JVM

Claims (12)

An information processing apparatus having a plurality of applications that communicate using a digital certificate,
An information processing apparatus comprising management means for managing association of each of the plurality of applications with a digital certificate, wherein the application uses a digital certificate associated with the management means.   2. The apparatus according to claim 1, further comprising setting accepting means for accepting the setting of the association via a setting screen for setting an association between the application and the digital certificate, and registering the set association in the managing means. Information processing device.   The information processing apparatus according to claim 2, wherein the setting accepting unit is configured to set an association between the storage area for storing the digital certificate and the application on the setting screen.   The information processing apparatus according to claim 3, wherein the management unit manages association between an identification name for the storage area and an identification name of the application. A certificate management method executed by an information processing apparatus having a plurality of applications that communicate using a digital certificate,
A recording procedure for recording an association with a digital certificate for each of the plurality of applications in a storage medium;
A certificate management method, wherein the application includes a certificate use procedure that uses a digital certificate associated with the storage medium. A setting acceptance procedure for accepting the setting of the association via a setting screen for setting the association between the application and the digital certificate;
6. The certificate management method according to claim 5, wherein the recording procedure records an association relating to the setting accepted in the setting acceptance procedure on the recording medium.   7. The certificate management method according to claim 6, wherein the setting reception procedure sets an association between a storage area for storing the digital certificate and the application on the setting screen.   8. The certificate management method according to claim 7, wherein the recording procedure records an association between an identification name for the storage area and an identification name of the application. To an information processing device that has multiple applications that communicate using digital certificates,
A recording procedure for recording an association with a digital certificate for each of the plurality of applications in a storage medium;
A certificate management program for causing the application to execute a certificate use procedure that uses a digital certificate associated with the storage medium. A setting acceptance procedure for accepting the setting of the association via a setting screen for setting the association between the application and the digital certificate;
10. The certificate management program according to claim 9, wherein the recording procedure records an association relating to the setting accepted in the setting acceptance procedure on the recording medium.   The certificate management program according to claim 10, wherein the setting reception procedure sets an association between a storage area for storing the digital certificate and the application on the setting screen.   12. The certificate management program according to claim 11, wherein the recording procedure records an association between an identification name for the storage area and an identification name of the application.

Images