Apparatus management system and apparatus management program

Abstract

To provide an apparatus management system and an apparatus management program capable of reducing the possibility of security risks such as unauthorized login to the apparatus management system.SOLUTION: In the apparatus management system provided with an apparatus management unit for managing at least one image forming apparatus, the apparatus management unit manages at least one system user who is a user of the apparatus management system, manages for each system user an authentication system of the second step of authentication processing for login including at least one step of authentication for the system user to login to the apparatus management system, and includes an e-mail system for receiving and using an authentication code sent to a specific e-mail address and an authentication application system for using the authentication code acquired by the authentication application as choices of the authentication systems of the second step of authentication.SELECTED DRAWING: Figure 15

Description

[Technical Field]

[0001] The present invention relates to a device management system and a device management program for managing electronic devices. [Background technology]

[0002] BACKGROUND ART Conventionally, device management systems that manage electronic devices are known (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2004-289313 Summary of the Invention [Problem to be solved by the invention]

[0004] However, conventional device management systems have a problem in that unauthorized login to the device management system may occur.

[0005] Therefore, an object of the present invention is to provide a device management system and a device management program that can reduce the possibility of security risks such as unauthorized login to the device management system. [Means for solving the problem]

[0006] The device management system of the present invention is a device management system comprising a device management unit that manages at least one electronic device, wherein the device management unit manages at least one user of the device management system, and the device management unit manages, for each user, an authentication method of specific-step authentication as authentication of a specific step of a login authentication process including at least one authentication step for the user to log in to the device management system, and the device management unit is characterized in that the authentication method options for the specific-step authentication include a code reception method that receives and uses an authentication code sent to a specific destination, and an authentication app method that uses an authentication code obtained by an authentication app.

[0007] With this configuration, the device management system of the present invention includes, as an option for authentication methods for specific step authentication, not only the code reception method but also the authentication app method, which is more secure than the code reception method, thereby reducing the possibility of security risks such as unauthorized login to the device management system.

[0008] In the device management system of the present invention, the device management unit manages at least one group to which at least one of the electronic devices and at least one of the users belong, and the device management unit manages whether the specific step authentication is valid for each group. When executing the login authentication process for the user, the device management unit executes the specific step authentication if the specific step authentication is valid for at least one of the groups to which the user belongs, and when executing the login authentication process for the user, the device management unit may not execute the specific step authentication if the specific step authentication is invalid for all of the groups to which the user belongs.

[0009] With this configuration, when executing login authentication processing for a user, the device management system of the present invention executes specific step authentication if specific step authentication is enabled in at least one group to which the user belongs, and when executing login authentication processing for a user, it does not execute specific step authentication if specific step authentication is disabled in all groups to which the user belongs, thereby reducing the possibility of unnecessarily reducing security.

[0010] In the device management system of the present invention, when the device management unit executes the specific step authentication for the user, the device management unit may set the authentication method of the specific step authentication to an authentication method that is managed in association with the user.

[0011] With this configuration, when the device management system of the present invention executes specific step authentication for a user, the authentication method for the specific step authentication is set to the authentication method managed in association with the user, thereby improving the possibility that the specific step authentication will be executed using the authentication method desired by the user.

[0012] In the device management system of the present invention, when generating a user information editing screen as a screen for editing information about the user, the device management unit displays an authentication method setting portion on the user information editing screen as a portion for setting an authentication method for the specific step authentication if the specific step authentication is enabled in at least one of the groups to which the user belongs, and when generating the user information editing screen for editing information about the user, the device management unit does not need to display the authentication method setting portion on the user information editing screen if the specific step authentication is disabled in all of the groups to which the user belongs.

[0013] With this configuration, when the device management system of the present invention generates a user information editing screen for editing information about a user, if specific-step authentication is enabled in at least one group to which the user belongs, it displays the authentication method setting portion on the user information editing screen, and when it generates a user information editing screen for editing information about a user, if specific-step authentication is disabled in all groups to which the user belongs, it does not display the authentication method setting portion on the user information editing screen, thereby reducing the possibility that the user will perform more settings than necessary and improving convenience.

[0014] In the device management system of the present invention, the device management unit manages at least one group to which at least one of the electronic devices and at least one of the users belong, and the device management unit manages administrators of the groups for each of the groups, and the device management unit may set the authentication method of the specific step authentication managed in association with the users belonging to the group to the code reception method in response to instructions from the administrator of the group.

[0015] With this configuration, the device management system of the present invention sets the authentication method of the specific step authentication managed in association with a user belonging to a group to the code reception method in response to instructions from the administrator of the group.Therefore, even if the authentication method of the specific step authentication managed in association with a user is the authentication app method and the user is no longer able to use the registered authentication app and the specific step authentication is no longer successful, the authentication method of the specific step authentication managed in association with the user can be changed to the code reception method, thereby improving the possibility of the specific step authentication being successful.

[0016] In the device management system of the present invention, when the user is newly registered, the device management unit may set the authentication method of the specific step authentication for this user to the code reception method.

[0017] With this configuration, when a user is newly registered, the device management system of the present invention sets the authentication method for the specific step authentication of the user to the code reception method, so that users who are satisfied with the code reception method as the authentication method for the specific step authentication do not need to perform the registration work of an authentication app, thereby improving convenience.

[0018] In the device management system of the present invention, when the authentication method of the specific step authentication associated with the user is changed from an authentication method other than the authentication app method to the authentication app method, the device management unit may request registration of the authentication app.

[0019] With this configuration, the device management system of the present invention requests registration of an authentication app when the authentication method of the specific step authentication associated with a user is changed from an authentication method other than the authentication app method to the authentication app method, thereby reducing the possibility that the user will forget to perform the authentication app registration work and improving convenience.

[0020] In the device management system of the present invention, when the authentication method of the specific step authentication associated with the user is the authentication app method, if registration of the authentication app fails, the device management unit may change the authentication method of the specific step authentication associated with the user to the code reception method.

[0021] With this configuration, when the authentication method for the specific step authentication associated with a user is the authentication app method, if registration of the authentication app fails, the device management system of the present invention changes the authentication method for the specific step authentication associated with this user to the code reception method, thereby improving the possibility that the specific step authentication will be successful without any problems even if an authentication app is not registered, and improving convenience.

[0022] A device management program of the present invention causes a computer to realize a device management system having a device management unit that manages at least one electronic device, wherein the device management unit manages at least one user of the device management system, and the device management unit manages, for each user, an authentication method of specific-step authentication as authentication of a specific step of a login authentication process that includes at least one authentication step for the user to log in to the device management system, and the device management unit includes, as options for the authentication method of the specific-step authentication, a code reception method that receives and uses an authentication code sent to a specific destination, and an authentication app method that uses an authentication code obtained by an authentication app.

[0023] With this configuration, a computer executing the device management program of the present invention includes, in its options for authentication methods for specific step authentication, not only the code reception method but also the authentication app method, which is more secure than the code reception method, thereby reducing the possibility of security risks such as unauthorized login to the device management system. [Effects of the Invention]

[0024] The device management system and device management program of the present invention can reduce the possibility of security risks such as unauthorized login to the device management system. [Brief explanation of the drawings]

[0025] [Figure 1] 1 is a block diagram of a system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a block diagram of the device management system shown in FIG. 1 when configured by one computer. [Figure 3] FIG. 3 is a diagram showing an example of device management information shown in FIG. 2. [Figure 4] FIG. 3 is a diagram showing an example of user management information shown in FIG. [Figure 5] FIG. 3 is a diagram showing an example of group management information shown in FIG. [Figure 6]FIG. 2 is a block diagram of the image forming apparatus shown in FIG. [Figure 7] FIG. 2 is a block diagram of an example of a user terminal shown in FIG. [Figure 8] FIG. 2 is a block diagram of an example of the smart device shown in FIG. [Figure 9] 7 is a flowchart of the operation of the image forming apparatus shown in FIG. 6 when notifying the toner level. [Figure 10] 3 is a flowchart showing the operation of the device management system shown in FIG. 2 when a new system user is registered. [Figure 11] 10 is a flowchart showing the operation of the device management system shown in FIG. 2 when two-factor authentication settings for a group are updated. [Figure 12] 12 is a diagram showing an example of a group authentication setting screen displayed in the operation shown in FIG. 11. FIG. [Figure 13] 3 is a flowchart of the operation of the device management system shown in FIG. 2 when information about a system user is edited in accordance with an instruction from the system user. [Figure 14] 14 is a diagram showing an example of an authentication method setting disabled screen displayed in the operation shown in FIG. 13. FIG. [Figure 15] FIG. 14 is a diagram showing an example of an authentication method setting screen displayed in the operation shown in FIG. 13. [Figure 16] 14 is a flowchart of the authentication application registration process shown in FIG. 13. [Figure 17] FIG. 17 is a diagram showing an example of an authentication application installation instruction screen displayed in the operation shown in FIG. 16. [Figure 18] FIG. 17 is a diagram showing an example of an authentication application registration screen displayed in the operation shown in FIG. 16. [Figure 19] 10 is a flowchart of the operation of the smart device shown in FIG. 8 when a private key indicated by a two-dimensional code is read by an authentication application. [Figure 20]10 is a flowchart of the operation of the device management system shown in FIG. 2 when the authentication method for the second step of the two-factor authentication of a system user is set to the email method in response to an instruction from a group administrator. [Figure 21] FIG. 21 is a diagram showing an example of an email format setting screen displayed in the operation shown in FIG. 20. [Figure 22] 3 is a flowchart of a part of the operation of the device management system shown in FIG. 2 when a system user logs in. [Figure 23] 23 is a continuation of the flowchart shown in FIG. 22. [Figure 24] FIG. 24 is a diagram showing an example of a knowledge authentication screen displayed in the operations shown in FIGS. 22 and 23. [Figure 25] FIG. 24 is a diagram showing an example of an e-mail authentication screen displayed in the operations shown in FIGS. 22 and 23. [Figure 26] FIG. 24 is a diagram showing an example of an authentication application authentication screen displayed in the operations shown in FIGS. 22 and 23. [Figure 27] 10 is a flowchart illustrating the operation of the smart device shown in FIG. 1 when displaying an authentication code. DETAILED DESCRIPTION OF THE INVENTION

[0026] Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[0027] First, the configuration of a system according to an embodiment of the present invention will be described.

[0028] FIG. 1 is a block diagram of a system 10 according to the present embodiment.

[0029] As shown in FIG. 1, the system 10 includes a device management system 20 that manages an image forming device as an electronic device. The device management system 20 may be configured with a single computer such as a PC (Personal Computer), or may be configured with multiple computers. The device management system 20 may be configured as a cloud server. The device management system 20 is managed, for example, by the manufacturer of the image forming device. The device management system 20 is used, for example, by service personnel belonging to a service company that performs maintenance on the image forming device.

[0030] The system 10 includes an image forming device 30, such as an MFP (Multifunction Peripheral) or a dedicated printer. The system 10 can include at least one other image forming device with a similar configuration to the image forming device 30. The image forming device is installed at the office location of a user of the image forming device, such as a customer of a service company. Each image forming device is assigned a serial number as identification information.

[0031] The system 10 includes a user terminal 40, such as a PC, smartphone, or tablet terminal, used by a user of the device management system 20, such as a service person (hereinafter referred to as a "system user"). The system 10 can include at least one other user terminal in addition to the user terminal 40 that has a similar configuration to the user terminal 40.

[0032] The system 10 includes a smart device 50, such as a smartphone or tablet terminal, that is used by a system user, such as a service person. The system 10 may also include at least one other smart device that has a similar configuration to the smart device 50.

[0033] The device management system 20 and the image forming apparatus can communicate with each other via a network 11 such as a LAN (Local Area Network) or the Internet.

[0034] The device management system 20 and the user terminal can communicate with each other via a network 12 such as a LAN or the Internet.

[0035] FIG. 2 is a block diagram of the device management system 20 when configured with one computer.

[0036] As shown in Figure 2, the equipment management system 20 includes an operation unit 21, which is an operation device such as a keyboard or mouse through which various operations are input; a display unit 22, which is a display device such as an LCD (Liquid Crystal Display) that displays various information; a communication unit 23, which is a communication device that communicates with external devices via a network such as a LAN or the Internet, or directly via a wired or wireless connection without using a network; a memory unit 24, which is a non-volatile memory device such as a semiconductor memory or an HDD (Hard Disk Drive) that stores various information; and a control unit 25 that controls the entire equipment management system 20.

[0037] The storage unit 24 can store a device management program 24a for managing the image forming apparatus. The device management program 24a may be installed in the device management system 20 during the manufacturing stage of the device management system 20, or may be additionally installed in the device management system 20 from an external storage medium such as a USB (Universal Serial Bus) memory, or may be additionally installed in the device management system 20 from a network.

[0038] The storage unit 24 is capable of storing information 24b for managing the image forming apparatus (hereinafter referred to as "device management information").

[0039] FIG. 3 is a diagram showing an example of the device management information 24b.

[0040] The device management information 24b shown in Fig. 3 includes a device ID as identification information for the image forming device, the name of the user of the image forming device, i.e., the name of the service company's customer, and a toner level as the remaining amount of toner as a consumable in the image forming device, all associated with each image forming device. The device management information 24b shown in Fig. 3 is drawn with some information omitted. For example, the device management information 24b shown in Fig. 3 indicates that "the image forming device with the device ID "D00001" is used by XX Co., Ltd., and the cyan, magenta, yellow, and black toner levels are 50%, 35%, 60%, and 10%, respectively."

[0041] As shown in FIG. 2, the storage unit 24 can store information 24c for managing system users (hereinafter referred to as "user management information").

[0042] FIG. 4 is a diagram showing an example of the user management information 24c.

[0043] The user management information 24c shown in FIG. 4 includes, for each system user, a user ID as identification information for the system user, a password for the system user, the name of the system user (hereinafter referred to as the "user name"), the email address of the system user, authentication method information indicating the authentication method for the second stage of two-factor authentication, and a private key, all associated with that system user. The second stage of two-factor authentication can be achieved by an email method, which is a code reception method in which an authentication code sent by email to a specific email address is received and used, or an authentication app method, which uses an authentication code obtained by an authentication app. The user management information 24c shown in FIG. 4 is partially omitted. For example, the user management information 24c shown in FIG. 4 indicates that the system user with the user ID "U0001" has the password "1234567," the user name "Yamada Taro," the email address "Taro@example.com," the authentication method for the second stage of two-factor authentication is the authentication app method, and the private key "1234···cba." " It is shown that

[0044] As shown in FIG. 2, the storage unit 24 can store information 24d for managing groups to which system users and image forming apparatuses belong (hereinafter referred to as "group management information").

[0045] FIG. 5 is a diagram showing an example of the group management information 24d.

[0046] The group management information 24d shown in FIG. 5 includes, in association with each group, a group ID as identification information for the group, information indicating system users belonging to the group (hereinafter referred to as "belonging user information"), information indicating a group administrator (hereinafter referred to as "group administrator") among the system users belonging to the group (hereinafter referred to as "group administrator information"), information indicating image forming devices belonging to the group (hereinafter referred to as "belonging device information"), and two-factor authentication valid / invalid information indicating whether two-factor authentication is valid. The belonging user information and group administrator information indicate system users by user IDs. The belonging device information indicates image forming devices by device IDs. The group management information 24d shown in FIG. 5 is drawn with some information omitted. For example, the group management information 24d shown in FIG. 5 indicates that "a group with a group ID of 'G001' includes users with user IDs such as 'U0001' and 'U0002', a system user with a user ID of 'U9999' is the group administrator, image forming devices with device IDs such as 'D00001' and 'D00002' belong to the group, and two-factor authentication is enabled."

[0047] 2 includes, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory) that stores programs and various data, and a RAM (Random Access Memory) that serves as a memory used as a work area for the CPU of the control unit 25. The CPU of the control unit 25 executes programs stored in the storage unit 24 or the ROM of the control unit 25.

[0048] The control unit 25 executes the device management program 24a to implement a device management unit 25a that manages the image forming apparatus.

[0049] FIG. 6 is a block diagram of the image forming apparatus 30. As shown in FIG.

[0050] As shown in FIG. 6, the image forming apparatus 30 includes an operation unit 31, which is an operation device such as a button through which various operations are input; a display unit 32, which is a display device such as an LCD that displays various information; a printer 33, which is a printing device that prints images on a recording medium such as paper; a toner level sensor 34 that detects the toner level in a toner container attached to the printer 33; a scanner 35, which is a reading device that reads images from a document; a communication unit 36, which is a communication device that communicates with an external device via a network such as a LAN or the Internet, or directly via a wired or wireless connection without using a network; a memory unit 37, which is a non-volatile memory device such as a semiconductor memory or HDD that stores various information; and a control unit 38 that controls the entire image forming apparatus 30.

[0051] The printer 33 has a replaceable toner container.

[0052] The toner level detected by the toner level sensor 34 becomes 100% when a new toner container is installed in the image forming apparatus 30 .

[0053] The storage unit 37 can store a toner level notification program 37a for notifying the device management system 20 of the toner level. The toner level notification program 37a may be installed in the image forming device 30 during the manufacturing stage of the image forming device 30, or may be additionally installed in the image forming device 30 from an external storage medium such as a USB memory, or may be additionally installed in the image forming device 30 from a network.

[0054] The storage unit 37 can store level notification time information 37b that indicates the level notification time as the time at which the toner level is notified to the device management system 20. The level notification time indicated in the level notification time information 37b may be a specific time in a day, or may be a specific number of times in a day.

[0055] The control unit 38 includes, for example, a CPU, a ROM that stores programs and various data, and a RAM as memory used as a work area for the CPU of the control unit 38. The CPU of the control unit 38 executes programs stored in the storage unit 37 or the ROM of the control unit 38.

[0056] The control unit 38 executes the toner level notification program 37a to realize a toner level notification unit 38a that notifies the device management system 20 of the toner level.

[0057] FIG. 7 is a block diagram of an example of the user terminal 40. As shown in FIG.

[0058] As shown in Figure 7, the user terminal 40 includes an operation unit 41, which is an operation device such as a keyboard or mouse through which various operations are input; a display unit 42, which is a display device such as an LCD that displays various information; a communication unit 43, which is a communication device that communicates with external devices via a network such as a LAN or the Internet, or directly via a wired or wireless connection without using a network; a memory unit 44, which is a non-volatile memory device such as a semiconductor memory or HDD that stores various information; and a control unit 45 that controls the entire user terminal 40.

[0059] The storage unit 44 can store a program for a web browser (hereinafter referred to as the "web browser program") 44a and a program for an email client (hereinafter referred to as the "email client program") 44b. The web browser program 44a and the email client program 44b may each be installed on the user terminal 40 during the manufacturing stage of the user terminal 40, or may be additionally installed on the user terminal 40 from an external storage medium such as a USB memory, or may be additionally installed on the user terminal 40 from a network.

[0060] The control unit 45 includes, for example, a CPU, a ROM that stores programs and various data, and a RAM as memory used as a work area for the CPU of the control unit 45. The CPU of the control unit 45 executes programs stored in the storage unit 44 or the ROM of the control unit 45.

[0061] The control unit 45 executes the web browser program 44a to realize a web browser 45a, and the control unit 45 executes the email client program 44b to realize an email client 45b.

[0062] FIG. 8 is a block diagram of an example of a smart device 50.

[0063] As shown in Figure 8, smart device 50 includes an operation unit 51 which is an operation device such as a button through which various operations are input, a display unit 52 which is a display device such as an LCD that displays various information, a camera 53, a communication unit 54 which is a communication device that communicates with external devices via a network such as a LAN or the Internet, or directly via a wired or wireless connection without using a network, a memory unit 55 which is a non-volatile memory device such as a semiconductor memory or HDD that stores various information, and a control unit 56 that controls the entire smart device 50.

[0064] The storage unit 55 can store a program for an authentication application (hereinafter referred to as the "authentication application program") 55a. The authentication application program 55a may be installed in the smart device 50 during the manufacturing stage of the smart device 50, or may be additionally installed in the smart device 50 from an external storage medium such as a USB memory, or may be additionally installed in the smart device 50 from a network.

[0065] The storage unit 55 can store a private key 55b for the authentication application.

[0066] The control unit 56 includes, for example, a CPU, a ROM that stores programs and various data, and a RAM as memory used as a work area for the CPU of the control unit 56. The CPU of the control unit 56 executes programs stored in the storage unit 55 or the ROM of the control unit 56.

[0067] Control unit 56 executes authentication application program 55a to implement authentication application 56a. For example, either Google Authenticator by Google (registered trademark) or Microsoft Authenticator by Microsoft (registered trademark) may be adopted as authentication application 56a.

[0068] The operation of the system 10 will now be described.

[0069] First, the operation of the image forming apparatus 30 when notifying the toner level will be described.

[0070] FIG. 9 is a flowchart of the operation of the image forming apparatus 30 when notifying the toner level.

[0071] As shown in FIG. 9, the toner level notification unit 38a of the image forming device 30 determines whether the current time is one of the level notification times indicated in the level notification time information 37b (S101) until it determines that the current time is one of the level notification times indicated in the level notification time information 37b.

[0072] When the toner level notification unit 38a determines in S101 that the current time is one of the level notification times indicated in the level notification time information 37b, it generates toner-related information including the device ID of the image forming device 30 and the toner levels for each color, such as cyan, magenta, yellow, and black, detected by the toner level sensor 34 (S102).

[0073] When the process of S102 is completed, the toner level notification unit 38a notifies the device management system 20 of the toner-related information generated in S102 (S103), and then executes the process of S101.

[0074] When the device management unit 25a of the device management system 20 receives toner-related information from the image forming device, it updates the toner level associated in the device management information 24b with the device ID in the toner-related information with the toner level in the toner-related information.

[0075] Next, the operation of the device management system 20 when a new system user is registered will be described.

[0076] FIG. 10 is a flowchart showing the operation of the device management system 20 when a new system user is registered.

[0077] For example, a system user with specific authority, such as an administrator of the device management system 20 or a group administrator of one of the groups, can log in to the device management system 20 from a web browser on the user terminal via a website provided by the device management system 20, and then input a command to newly register another system user (hereinafter referred to as a "user registration command") to the device management system 20 from the web browser on the user terminal via the website provided by the device management system 20. The user registration command includes the user name and email address of the system user to be newly registered. The user registration command also includes the group ID of the group to which the newly registered system user belongs. When a user registration command is input, the device management unit 25a of the device management system 20 performs the operation shown in FIG. 10.

[0078] As shown in FIG. 10, the device management unit 25a generates a user ID and a password for a new system user to be registered (S121).

[0079] When the process of S121 is completed, the device management unit 25a specifies the email method as the authentication method for the second stage of the two-factor authentication (S122).

[0080] When the processing of S122 is completed, the device management unit 25a associates the user ID and password generated in S121 with the user name and email address included in the user registration instruction and the authentication method identified in S122 and registers them in the user management information 24c (S123).

[0081] When the processing of S123 is completed, the device management unit 25a adds the user ID generated in S121 to the belonging user information that is associated in the group management information 24d with the group ID included in the user registration instruction (S124), and terminates the operation shown in Figure 10.

[0082] Next, the operation of the device management system 20 when the two-factor authentication setting for a group is updated will be described.

[0083] FIG. 11 is a flowchart of the operation of the device management system 20 when the two-factor authentication setting for a group is updated.

[0084] For example, a system user with specific authority, such as a group administrator of one of the groups, can log in to the device management system 20 from a web browser on the user terminal via a website provided by the device management system 20, and then input an instruction to start setting up two-factor authentication for the group (hereinafter referred to as a "group two-factor authentication setting start instruction") to the device management system 20 from the web browser on the user terminal via the website provided by the device management system 20. The group two-factor authentication setting start instruction includes the group ID of the group for which the two-factor authentication settings are to be updated. When the group two-factor authentication setting start instruction is input, the device management unit 25a of the device management system 20 performs the operation shown in FIG. 11.

[0085] As shown in FIG. 11, the device management unit 25a displays a screen for setting up two-factor authentication in a group (hereinafter referred to as the "group authentication setting screen") 300 (see FIG. 12) on the display unit of the user terminal via the web browser of the user terminal (S141).

[0086] FIG. 12 is a diagram showing an example of the group authentication setting screen 300. As shown in FIG.

[0087] The group authentication setting screen 300 shown in FIG. 12 includes a check box 301 as a widget for specifying whether to enable two-factor authentication, an update button 302 as a widget for updating the two-factor authentication setting for the group, and a cancel button 303 as a widget for canceling the two-factor authentication setting for the group.

[0088] At the time when the display of the group authentication setting screen 300 is started, if the two-factor authentication valid / invalid information associated in the group management information 24d with the group ID in the group two-factor authentication setting start instruction (hereinafter referred to as the "target group ID" in the explanation of the operation shown in FIG. 11) indicates that "two-factor authentication is valid", the device management unit 25a sets the checkbox 301 to a checked state, and if the two-factor authentication valid / invalid information associated in the group management information 24d with the target group ID indicates that "two-factor authentication is not valid", the device management unit 25a sets the checkbox 301 to an unchecked state.

[0089] As shown in FIG. 11, when the process of S141 is completed, the device management unit 25a determines whether the update button 302 has been pressed (S142).

[0090] If the device management unit 25a determines in S142 that the update button 302 has not been pressed, it determines whether the cancel button 303 has been pressed (S143).

[0091] If the device management unit 25a determines in S143 that the cancel button 303 has not been pressed, it executes the process of S142.

[0092] When the device management unit 25a determines in S142 that the update button 302 has been pressed, it updates the two-factor authentication valid / invalid information associated with the target group ID in the group management information 24d with the content specified on the group authentication setting screen 300 at the time the update button 302 was pressed (S144). Specifically, if the check box 301 is checked at the time the update button 302 is pressed, the device management unit 25a sets the two-factor authentication valid / invalid information associated with the target group ID in the group management information 24d to "two-factor authentication is valid," and if the check box 301 is unchecked at the time the update button 302 is pressed, the device management unit 25a sets the two-factor authentication valid / invalid information associated with the target group ID in the group management information 24d to "two-factor authentication is not valid."

[0093] When the device management unit 25a determines in S143 that the cancel button 303 has been pressed, or when the processing of S144 is completed, the device management unit 25a terminates the display of the group authentication setting screen 300 on the display unit of the user terminal via the web browser of the user terminal (S145), and terminates the operation shown in Figure 11.

[0094] Next, the operation of device management system 20 when information about a system user is edited in response to an instruction from the system user will be described.

[0095] FIG. 13 is a flowchart showing the operation of the device management system 20 when information about a system user is edited in response to an instruction from the system user.

[0096] After logging in to the device management system 20 from the web browser of the user terminal via a website provided by the device management system 20, the system user can input an instruction to start editing information about the system user himself / herself (hereinafter referred to as a "user information editing start instruction") to the device management system 20 from the web browser of the user terminal via the website provided by the device management system 20. When the user information editing start instruction is input, the device management unit 25a of the device management system 20 executes the operation shown in Fig. 13.

[0097] As shown in Figure 13, the device management unit 25a determines whether there is a group among all groups associated in the belonging user information of the group management information 24d with the user ID of the system user who input the instruction to start editing user information (hereinafter referred to as the "target user ID" in the explanation of the operation shown in Figure 13) for which two-factor authentication is indicated as valid in the two-factor authentication valid / invalid information of the group management information 24d (S161).

[0098] If the device management unit 25a determines in S161 that there is no group among all groups associated with the target user ID in the belonging user information of the group management information 24d for which two-factor authentication is indicated as being enabled in the two-factor authentication enable / disable information of the group management information 24d, it displays a screen for editing information about system users (hereinafter referred to as the "user information editing screen") 310 (see Figure 14), which is a screen that does not allow the authentication method for the second stage of two-factor authentication to be set (hereinafter referred to as the "authentication method setting disabled screen"), on the display unit of the user terminal via the web browser of the user terminal (S162).

[0099] FIG. 14 is a diagram showing an example of the authentication method setting disabled screen 310. As shown in FIG.

[0100] The authentication method setting unavailable screen 310 shown in Figure 14 includes a text box 311 as a widget for inputting the user name of the system user, a text box 312 as a widget for inputting the email address of the system user, an update button 313 as a widget for updating information about the system user, and a cancel button 314 as a widget for canceling the update of information about the system user.

[0101] When the device management unit 25a starts displaying the authentication method setting impossible screen 310, it inputs the user name associated with the target user ID in the user management information 24c into a text box 311. When the device management unit 25a starts displaying the authentication method setting impossible screen 310, it inputs the email address associated with the target user ID in the user management information 24c into a text box 312.

[0102] As shown in FIG. 13, when the process of S162 is completed, the device management unit 25a determines whether the update button 313 has been pressed (S163).

[0103] If the device management unit 25a determines in S163 that the update button 313 has not been pressed, it determines whether the cancel button 314 has been pressed (S164).

[0104] If the device management unit 25a determines in S164 that the cancel button 314 has not been pressed, it executes the process of S163.

[0105] When the device management unit 25a determines in S163 that the update button 313 has been pressed, it updates the user name and email address associated with the target user ID in the user management information 24c with the content specified on the authentication method setting disabled screen 310 at the time the update button 313 was pressed (S165). Specifically, the device management unit 25a updates the user name associated with the target user ID in the user management information 24c with the user name input in the text box 311 at the time the update button 313 was pressed. In addition, the device management unit 25a updates the email address associated with the target user ID in the user management information 24c with the email address input in the text box 312 at the time the update button 313 was pressed.

[0106] When the device management unit 25a determines in S164 that the cancel button 314 has been pressed, or when the processing of S165 is completed, the device management unit 25a terminates the display of the authentication method setting impossible screen 310 on the display unit of the user terminal via the web browser of the user terminal (S166), and terminates the operation shown in Figure 13.

[0107] If the device management unit 25a determines in S161 that there is a group among all groups associated with the target user ID in the belonging user information of the group management information 24d for which two-factor authentication is indicated as being valid in the two-factor authentication valid / invalid information of the group management information 24d, the device management unit 25a turns off a flag (hereinafter referred to as the "authentication app registration flag") for registering an authentication app to the device management system 20 (S167).

[0108] When the processing of S167 is completed, the device management unit 25a causes a user information editing screen (hereinafter referred to as the "authentication method setting screen") 320 (see Figure 15) on which the authentication method for the second stage of two-factor authentication can be set, to be displayed on the display unit of the user terminal via the web browser of the user terminal (S168).

[0109] FIG. 15 is a diagram showing an example of the authentication method setting screen 320. As shown in FIG.

[0110] 15 includes a text box 321 as a widget for inputting the user name of the system user, a text box 322 as a widget for inputting the email address of the system user, an authentication method setting section 323 as a section for setting the authentication method for the second stage of two-factor authentication, an update button 324 as a widget for updating information about the system user, and a cancel button 325 as a widget for canceling the update of information about the system user. Authentication method setting section 323 includes a radio button (hereinafter referred to as the "email method radio button") 323a as a widget for selecting the email method as the authentication method for the second stage of two-factor authentication, and a radio button (hereinafter referred to as the "authentication app method radio button") 323b as a widget for selecting the authentication app method as the authentication method for the second stage of two-factor authentication. Only one of email method radio button 323a and authentication app method radio button 323b is selected at any one time.

[0111] When device management unit 25a starts displaying authentication method settable screen 320, it inputs the user name associated with the target user ID in user management information 24c into text box 321. When device management unit 25a starts displaying authentication method settable screen 320, it also inputs the email address associated with the target user ID in user management information 24c into text box 322. When device management unit 25a starts displaying authentication method settable screen 320, if the email method is indicated in the authentication method information associated with the target user ID in user management information 24c, device management unit 25a selects email method radio button 323a out of email method radio button 323a and authentication application method radio button 323b, and when the authentication method information associated with the target user ID in user management information 24c indicates the authentication application method, it selects authentication application method radio button 323b out of email method radio button 323a and authentication application method radio button 323b.

[0112] As shown in FIG. 13, when the process of S168 ends, the device management unit 25a determines whether the update button 324 has been pressed (S169).

[0113] If the device management unit 25a determines in S169 that the update button 324 has not been pressed, it determines whether the cancel button 325 has been pressed (S170).

[0114] If the device management unit 25a determines in S170 that the cancel button 325 has not been pressed, it executes the process of S169.

[0115] When the device management unit 25a determines in S169 that the update button 324 has been pressed, it determines whether or not the radio button 323b for the authentication application method was selected at the time the update button 324 was pressed, that is, whether or not the method was switched from the email method to the authentication application method, when the authentication method information associated with the target user ID in the user management information 24c indicates the email method (S171).

[0116] If the device management unit 25a determines in S171 that the radio button 323b for the authentication app method was selected at the time the update button 324 was pressed, that is, that the method was switched from the email method to the authentication app method, when the authentication method information associated with the target user ID in the user management information 24c indicates the email method, the device management unit 25a sets an authentication app registration flag (S172).

[0117] When the device management unit 25a determines in S171 that the authentication application method radio button 323b was not selected when the update button 324 was pressed, i.e., the email method was not switched to the authentication application method, in a state where the email method is indicated in the authentication method information associated with the target user ID in the user management information 24c, or when the device management unit 25a completes the process in S172, the device management unit 25a updates the user name, email address, and authentication method information associated with the target user ID in the user management information 24c with the content specified on the authentication method setting screen 320 when the update button 324 was pressed (S173). Specifically, the device management unit 25a updates the user name associated with the target user ID in the user management information 24c with the user name entered in the text box 321 when the update button 324 was pressed. The device management unit 25a also updates the email address associated with the target user ID in the user management information 24c with the email address entered in the text box 322 when the update button 324 was pressed. In addition, if the radio button 323a for the email method is selected at the time the update button 324 is pressed, the device management unit 25a sets the email method to the authentication method information associated with the target user ID in the user management information 24c, and if the radio button 323b for the authentication application method is selected at the time the update button 324 is pressed, the device management unit 25a sets the authentication application method to the authentication method information associated with the target user ID in the user management information 24c.

[0118] When the device management unit 25a determines in S170 that the cancel button 325 has been pressed, or when the processing of S173 is completed, the device management unit 25a terminates the display of the authentication method setting screen 320 on the display unit of the user terminal via the web browser of the user terminal (S174).

[0119] When the process of S174 ends, the device management unit 25a determines whether the authentication application registration flag is set (S175).

[0120] If the device management unit 25a determines in S175 that the authentication application registration flag is not set, the operation shown in FIG. 13 ends.

[0121] If the device management unit 25a determines in S175 that the authentication application registration flag is set, it executes an authentication application registration process (see FIG. 16) for registering the authentication application in the device management system 20 (S176).

[0122] FIG. 16 is a flowchart of the authentication application registration process shown in FIG.

[0123] As shown in FIG. 16, the device management unit 25a causes a screen (hereinafter referred to as the "authentication app installation instruction screen") 330 (see FIG. 17) for instructing the installation of an authentication app on a smart device to be displayed on the display unit of the user terminal via the web browser of the user terminal (S181).

[0124] FIG. 17 is a diagram showing an example of the authentication application installation instruction screen 330. As shown in FIG.

[0125] The authentication app installation instruction screen 330 shown in Figure 17 includes a message 331 instructing the installation of the authentication app on the smart device, a cancel button 332 as a widget for canceling the registration of the authentication app in the device management system 20, and a next button 333 as a widget for proceeding to the next step.

[0126] As shown in FIG. 13, when the process of S181 is completed, the device management unit 25a determines whether or not the next button 333 has been pressed (S182).

[0127] If the device management unit 25a determines in S182 that the next button 333 has not been pressed, it determines whether the cancel button 332 has been pressed (S183).

[0128] If the device management unit 25a determines in S183 that the cancel button 332 has not been pressed, it executes the process of S182.

[0129] If the device management unit 25a determines in S183 that the cancel button 332 has been pressed, it terminates the display of the authentication application installation instruction screen 330 on the display unit of the user terminal via the web browser of the user terminal (S184).

[0130] When the device management unit 25a determines in S182 that the Next button 333 has been pressed, it terminates the display of the authentication application installation instruction screen 330 on the display unit of the user terminal via the web browser of the user terminal (S185).

[0131] When the process of S185 is completed, the device management unit 25a generates a secret key to be used for generating an authentication code (S186).

[0132] When the processing of S186 is completed, the device management unit 25a causes a screen for registering the authentication app to the device management system 20 (hereinafter referred to as the "authentication app registration screen") 340 (see FIG. 18) to be displayed on the display unit of the user terminal via the web browser of the user terminal (S187).

[0133] FIG. 18 is a diagram showing an example of the authentication application registration screen 340. As shown in FIG.

[0134] The authentication app registration screen 340 shown in Figure 18 includes a two-dimensional code 341 indicating the private key generated in S186, a message 342 instructing the authentication app to read the two-dimensional code 341 and enter the authentication code displayed on the authentication app, a text box 343 as a widget for entering the authentication code, a cancel button 344 as a widget for canceling the registration of the authentication app to the device management system 20, and a register button 345 as a widget for registering the authentication app to the device management system 20.

[0135] The system user can launch the authentication app on the smart device and use the camera on the smart device to photograph the two-dimensional code 341 on the authentication app registration screen 340, thereby causing the authentication app to read the private key indicated by the two-dimensional code 341. The following description will be given taking smart device 50 as an example of a smart device.

[0136] FIG. 19 is a flowchart of the operation of the smart device 50 when the private key indicated by the two-dimensional code 341 is read by the authentication application 56a.

[0137] As shown in FIG. 19, the authentication application 56a determines whether the two-dimensional code 341 has been photographed by the camera 53 until it determines that the two-dimensional code 341 has been photographed by the camera 53 (S201).

[0138] When the authentication application 56a determines in S201 that the two-dimensional code 341 has been photographed by the camera 53, it reads the private key indicated by the two-dimensional code 341 photographed by the camera 53 (S202).

[0139] When the processing of S202 is completed, the authentication application 56a stores the private key read in S202 in the storage unit 55 (S203).

[0140] When the processing of S203 ends, the authentication application 56a generates an authentication code using the private key read in S202 and the current time (S204).

[0141] When the processing of S204 is completed, the authentication application 56a displays the authentication code generated in S204 on the display unit 52 (S205), and ends the operation shown in FIG.

[0142] Therefore, the system user can input the authentication code displayed on the display unit 52 of the smart device 50 into the text box 343 (see Figure 18) of the authentication app registration screen 340 (see Figure 18) displayed on the display unit of the user terminal via the operation unit of the user terminal.

[0143] As shown in FIG. 16, when the process of S187 is completed, the device management unit 25a determines whether or not the registration button 345 has been pressed (S188).

[0144] If the device management unit 25a determines in S188 that the registration button 345 has not been pressed, it determines whether the cancel button 344 has been pressed (S189).

[0145] If the device management unit 25a determines in S189 that the cancel button 344 has not been pressed, it executes the process of S188.

[0146] If the device management unit 25a determines in S189 that the cancel button 344 has been pressed, it terminates the display of the authentication application registration screen 340 on the display unit of the user terminal via the web browser of the user terminal (S190).

[0147] When determining in S188 that the registration button 345 has been pressed, the device management unit 25a terminates the display of the authentication application registration screen 340 on the display unit of the user terminal via the web browser of the user terminal (S191).

[0148] When the processing of S191 is completed, the device management unit 25a generates an authentication code using the private key indicated by the two-dimensional code 341 at the time the registration button 345 was pressed and the time at which the registration button 345 was pressed (S192).

[0149] When the processing of S192 is completed, the device management unit 25a determines whether the authentication code entered in the text box 343 at the time the registration button 345 was pressed matches the authentication code generated in S192 (S193).

[0150] If the device management unit 25a determines in S193 that the authentication code entered in the text box 343 at the time the registration button 345 was pressed matches the authentication code generated in S192, it registers the private key indicated by the two-dimensional code 341 at the time the registration button 345 was pressed as the private key associated with the target user ID in the user management information 24c (S194).

[0151] When the processing of S184 or S190 is completed or when the device management unit 25a determines in S193 that the authentication code entered in the text box 343 at the time the registration button 345 was pressed does not match the authentication code generated in S192, the device management unit 25a sets the authentication method information associated with the target user ID in the user management information 24c to the email method (S195).

[0152] When the process of S194 or S195 ends, the device management unit 25a ends the authentication application registration process shown in FIG.

[0153] As shown in FIG. 13, when the authentication application registration process in S176 ends, the device management unit 25a ends the operation shown in FIG.

[0154] Next, the operation of the device management system 20 when the authentication method for the second stage of two-factor authentication of a system user is set to email authentication in response to an instruction from the group administrator will be described.

[0155] FIG. 20 is a flowchart of the operation of the device management system 20 when the authentication method for the second stage of two-factor authentication of a system user is set to the email method in response to an instruction from the group administrator.

[0156] After logging in to the device management system 20 from the web browser of the user terminal via a website provided by the device management system 20, the group administrator can input an instruction to start processing to set the authentication method for the second stage of the system user's two-factor authentication to the email method (hereinafter referred to as an "email method setting processing start instruction") to the device management system 20 from the web browser of the user terminal via the website provided by the device management system 20. When the email method setting processing start instruction is input, the device management unit 25a of the device management system 20 executes the operation shown in Fig. 20.

[0157] As shown in FIG. 20, the device management unit 25a displays a screen (hereinafter referred to as the "email method setting screen") 350 (see FIG. 21) for setting the authentication method for the second stage of the system user's two-factor authentication to the email method on the display unit of the user terminal via the web browser of the user terminal (S221).

[0158] FIG. 21 is a diagram showing an example of the email method setting screen 350. As shown in FIG.

[0159] The email method setting screen 350 shown in FIG. 21 includes a message 351 instructing the user to select a system user for whom the authentication method for the second stage of two-factor authentication is to be set to the email method; a drop-down list 352 as a widget for selecting the group ID of a group to which a system user for whom the authentication method for the second stage of two-factor authentication is to be set to the email method belongs; a drop-down list 353 as a widget for selecting the user ID of a system user for whom the authentication method for the second stage of two-factor authentication is to be set to the email method; a set button 354 as a widget for setting the authentication method for the second stage of two-factor authentication to the email method; and a cancel button 355 as a widget for canceling the setting of the authentication method for the second stage of two-factor authentication to the email method.

[0160] The device management unit 25a makes the group IDs of all groups to which the group manager who input the instruction to start the email method setting process belongs as a group manager selectable items in the drop-down list 352.

[0161] The device management unit 25a makes each of all user IDs indicated in the belonging user information associated in the group management information 24d with the group ID selected in the drop-down list 352 selectable items in the drop-down list 353.

[0162] As shown in FIG. 20, when the process of S221 is completed, the device management unit 25a determines whether or not the setting button 354 has been pressed (S222).

[0163] If the device management unit 25a determines in S222 that the setting button 354 has not been pressed, it determines whether the cancel button 355 has been pressed (S223).

[0164] If the device management unit 25a determines in S223 that the cancel button 355 has not been pressed, it executes the process of S222.

[0165] When the device management unit 25a determines in S223 that the cancel button 355 has been pressed, it terminates the display of the email method setting screen 350 on the display unit of the user terminal via the web browser of the user terminal (S224), and terminates the operation shown in Figure 20.

[0166] When the device management unit 25a determines in S222 that the setting button 354 has been pressed, it terminates the display of the email method setting screen 350 on the display unit of the user terminal via the web browser of the user terminal (S225).

[0167] When the processing of S225 is completed, the device management unit 25a sets the authentication method information associated in the user management information 24c with the user ID selected by the drop-down list 353 at the time the setting button 354 was pressed to the email method (S226), and terminates the operation shown in Figure 20.

[0168] Next, the operation of the device management system 20 when a system user logs in will be described.

[0169] 22 is a flowchart of part of the operation of device management system 20 when a system user logs in. FIG. 23 is a flowchart that follows the flowchart shown in FIG.

[0170] A system user can input an instruction to start logging in to the device management system 20 (hereinafter referred to as a "login start instruction") to the device management system 20 from a web browser on the user terminal via a website provided by the device management system 20. When the login start instruction is input, the device management unit 25a of the device management system 20 executes the operations shown in Figures 22 and 23. The series of processes shown in Figures 22 and 23 is a process that includes at least one authentication step for a system user to log in to the device management system 20, and constitutes the login authentication process of the present invention.

[0171] As shown in Figures 22 and 23, the device management unit 25a displays a screen for performing authentication using a user ID and password (hereinafter referred to as the "knowledge authentication screen") 360 (see Figure 24) on the display unit of the user terminal via the web browser of the user terminal (S241).

[0172] FIG. 24 is a diagram showing an example of the knowledge authentication screen 360. As shown in FIG.

[0173] The knowledge authentication screen 360 shown in FIG. 24 includes a text box 361 as a widget for inputting the user ID of the system user, a text box 362 as a widget for inputting the password of the system user, an authentication button 363 as a widget for performing authentication using the user ID and password, and a cancel button 364 as a widget for canceling the execution of authentication using the user ID and password.

[0174] As shown in FIGS. 22 and 23, when the process of S241 ends, the device management unit 25a determines whether or not the authentication button 363 has been pressed (S242).

[0175] If the device management unit 25a determines in S242 that the authentication button 363 has not been pressed, it determines whether the cancel button 364 has been pressed (S243).

[0176] If the device management unit 25a determines in S243 that the cancel button 364 has not been pressed, it executes the process of S242.

[0177] When the device management unit 25a determines in S243 that the cancel button 364 has been pressed, it terminates the display of the knowledge authentication screen 360 on the display unit of the user terminal via the web browser of the user terminal (S244), and terminates the operations shown in Figures 22 and 23.

[0178] When the device management unit 25a determines in S242 that the authentication button 363 has been pressed, it terminates the display of the knowledge authentication screen 360 on the display unit of the user terminal via the web browser of the user terminal (S245).

[0179] When the processing of S245 is completed, the device management unit 25a determines whether the combination of the user ID (hereinafter referred to as the "target user ID") entered in the text box 361 at the time the authentication button 363 was pressed and the password entered in the text box 362 at the time the authentication button 363 was pressed is included in the user management information 24c (S246).

[0180] When the device management unit 25a determines in S246 that the combination of the target user ID and the password entered in the text box 362 at the time the authentication button 363 was pressed is included in the user management information 24c, it determines whether or not there is a group among all groups associated with the target user ID in the belonging user information of the group management information 24d for which two-factor authentication is indicated as being valid in the two-factor authentication valid / invalid information of the group management information 24d (S247).

[0181] When the device management unit 25a determines in S247 that there is a group among all groups associated with the target user ID in the belonging user information of the group management information 24d for which two-factor authentication is indicated as valid in the two-factor authentication valid / invalid information of the group management information 24d, it determines the authentication method indicated in the authentication method information associated with the target user ID in the user management information 24c (S248).

[0182] When the device management unit 25a determines in S248 that the authentication method indicated in the authentication method information associated with the target user ID in the user management information 24c is the email method, it generates an authentication code using the private key associated with the target user ID in the user management information 24c and the current time (S249).

[0183] When the processing of S249 is completed, the authentication application sends the authentication code generated in S249 by email to the email address associated with the target user ID in the user management information 24c (S250).

[0184] When the processing of S250 is completed, the authentication app displays a screen for performing authentication via email (hereinafter referred to as the "email authentication screen") 370 (see Figure 25) on the display unit of the user terminal via the web browser of the user terminal (S251).

[0185] FIG. 25 is a diagram showing an example of the email authentication screen 370. As shown in FIG.

[0186] The email authentication screen 370 shown in FIG. 25 includes a message 371 instructing the user to enter the authentication code sent by email, a text box 372 as a widget for entering the authentication code, an authentication button 373 as a widget for executing the authentication, and a cancel button 374 as a widget for canceling the execution of the authentication.

[0187] The device management unit 25a may include in the message 371 the email address associated with the target user ID in the user management information 24c.

[0188] After receiving the email sent in S250 using, for example, an email client on the user's terminal, the system user can enter the authentication code sent in this email into text box 372.

[0189] As shown in FIGS. 22 and 23, when the process of S251 ends, the device management unit 25a determines whether or not the authentication button 373 has been pressed (S252).

[0190] If the device management unit 25a determines in S252 that the authentication button 373 has not been pressed, it determines whether the cancel button 374 has been pressed (S253).

[0191] If the device management unit 25a determines in S253 that the cancel button 374 has not been pressed, it executes the process of S252.

[0192] When the device management unit 25a determines in S253 that the cancel button 374 has been pressed, it terminates the display of the email authentication screen 370 on the display unit of the user terminal via the web browser of the user terminal (S254), and terminates the operations shown in Figures 22 and 23.

[0193] When the device management unit 25a determines in S252 that the authentication button 373 has been pressed, it terminates the display of the email authentication screen 370 on the display unit of the user terminal via the web browser of the user terminal (S255).

[0194] When the processing of S255 is completed, the device management unit 25a determines whether the authentication code entered in the text box 372 at the time the authentication button 373 was pressed matches the authentication code generated in S249 (S256).

[0195] If the device management unit 25a determines in S248 that the authentication method indicated in the authentication method information associated with the target user ID in the user management information 24c is the authentication app method, it causes a screen for performing authentication using the authentication app method (hereinafter referred to as the "authentication app method authentication screen") 380 (see FIG. 26) to be displayed on the display unit of the user terminal via the web browser of the user terminal (S257).

[0196] FIG. 26 is a diagram showing an example of authentication application authentication screen 380. As shown in FIG.

[0197] The authentication app-based authentication screen 380 shown in FIG. 26 includes a message 381 instructing the user to enter the authentication code acquired by the authentication app, a text box 382 as a widget for entering the authentication code, an authentication button 383 as a widget for executing authentication, and a cancel button 384 as a widget for canceling the execution of authentication.

[0198] The system user can launch the authentication app on the smart device and have the authentication app display the authentication code on the display of the smart device.

[0199] FIG. 27 is a flowchart showing the operation of the smart device when displaying the authentication code.

[0200] As shown in FIG. 27, the authentication application in the smart device generates an authentication code using the private key stored in the storage unit of the smart device and the current time (S271).

[0201] When the processing of S271 is completed, the authentication application displays the authentication code generated in S271 on the display unit of the smart device (S272), and then ends the operation shown in FIG.

[0202] Therefore, the system user can input the authentication code displayed on the display unit of the smart device into text box 382 (see Figure 26) of authentication app method authentication screen 380 (see Figure 26) displayed on the display unit of the user terminal via the operation unit of the user terminal.

[0203] As shown in FIGS. 22 and 23, when the process of S257 ends, the device management unit 25a determines whether or not the authentication button 383 has been pressed (S258).

[0204] If the device management unit 25a determines in S258 that the authentication button 383 has not been pressed, it determines whether the cancel button 384 has been pressed (S259).

[0205] If the device management unit 25a determines in S259 that the cancel button 384 has not been pressed, it executes the process of S258.

[0206] If the device management unit 25a determines in S259 that the cancel button 384 has been pressed, it terminates the display of the authentication app authentication screen 380 on the display unit of the user terminal via the web browser of the user terminal (S260), and terminates the operations shown in Figures 22 and 23.

[0207] When device management unit 25a determines in S258 that authentication button 383 has been pressed, it terminates the display of authentication application authentication screen 380 on the display unit of the user terminal via the web browser of the user terminal (S261).

[0208] When the processing of S261 is completed, the device management unit 25a generates an authentication code using the private key associated with the target user ID in the user management information 24c and the time when the authentication button 383 is pressed (S262).

[0209] When the processing of S262 is completed, the device management unit 25a determines whether the authentication code entered in the text box 382 at the time the authentication button 383 was pressed matches the authentication code generated in S262 (S263).

[0210] If the device management unit 25a determines in S246 that the combination of the target user ID and the password entered in text box 362 at the time the authentication button 363 was pressed is not included in the user management information 24c, or determines in S256 that the authentication code entered in text box 372 at the time the authentication button 373 was pressed does not match the authentication code generated in S249, or determines in S263 that the authentication code entered in text box 382 at the time the authentication button 383 was pressed does not match the authentication code generated in S262, it displays a login failure on the display unit of the user terminal via the web browser of the user terminal (S264) and terminates the operation shown in Figures 22 and 23.

[0211] If the device management unit 25a determines in S247 that there is no group among all the groups associated with the target user ID in the belonging user information of the group management information 24d for which two-factor authentication is indicated as being enabled in the two-factor authentication enable / disable information of the group management information 24d, or determines in S256 that the authentication code entered in the text box 372 at the time the authentication button 373 was pressed matches the authentication code generated in S249, or determines in S263 that the authentication code entered in the text box 382 at the time the authentication button 383 was pressed matches the authentication code generated in S262, the device management unit 25a permits login of the system user identified by the target user ID (S265) and terminates the operation shown in Figures 22 and 23.

[0212] When a system user logs in to the device management system 20 from the web browser 45a of the user terminal 40 via a website provided by the device management system 20, the system user can check various types of information managed by the device management system 20, such as various types of information about image forming devices that belong to the group to which the system user himself belongs, via the web browser 45a. Furthermore, when a system user logs in to the device management system 20 from the web browser 45a of the user terminal 40 via a website provided by the device management system 20, the system user can perform various operations, such as restarting an image forming device, on the image forming devices that belong to the group to which the system user himself belongs from the web browser 45a via the device management system 20.

[0213] As described above, the device management system 20 includes, as options for the second stage of two-factor authentication, i.e., specific step authentication, not only the email method but also the authentication app method, which is more secure than the email method, as shown in FIG. 15, thereby reducing the possibility of security risks such as unauthorized login to the device management system 20.

[0214] When executing the login authentication process (S241 to S265) for a system user, if the second stage of two-factor authentication is enabled for at least one group to which the system user belongs (YES in S247), the device management system 20 executes the second stage of two-factor authentication (S256 or S263), and when executing the login authentication process (S241 to S265) for a system user, if the second stage of two-factor authentication is disabled for all groups to which the system user belongs (NO in S247), the device management system 20 does not execute the second stage of two-factor authentication, thereby reducing the possibility of unnecessarily reducing security.

[0215] When the device management system 20 performs the second stage of two-factor authentication for a system user (YES in S247), it sets the authentication method for the second stage of two-factor authentication to the authentication method that is managed in association with this system user (S248 to S263), thereby improving the possibility that the second stage of two-factor authentication will be performed using the authentication method desired by the system user.

[0216] When generating a user information editing screen for editing information about a system user, if the second stage of two-factor authentication is enabled in at least one group to which the system user belongs (YES in S161), the device management system 20 displays the authentication method setting section 323 on the authentication method setting available screen 320 as the user information editing screen (S168), and when generating a user information editing screen for editing information about a system user, if the second stage of two-factor authentication is disabled in all groups to which the system user belongs (NO in S161), the device management system 20 does not display the authentication method setting section on the authentication method setting unavailable screen 310 as the user information editing screen (S162).This reduces the possibility that the system user will perform more settings than necessary, thereby improving convenience.

[0217] The device management system 20 sets the authentication method for the second stage of authentication of the two-factor authentication managed in association with a system user belonging to a group to the email method in response to instructions from the group administrator of this group (S226). Therefore, when the authentication method for the second stage of authentication of the two-factor authentication managed in association with a system user is the authentication app method, even if the system user loses the smart device on which the registered authentication app is installed and is therefore unable to use the registered authentication app, and the second stage of authentication of the two-factor authentication is no longer successful, the authentication method for the second stage of authentication of the two-factor authentication managed in association with the system user can be changed to the email method, thereby improving the possibility of the second stage of authentication of the two-factor authentication being successful. When the authentication method for the second step of the two-factor authentication managed in association with the system user is the authentication app method, if the system user becomes unable to use the registered authentication app, for example, because the smart device on which the registered authentication app is installed is lost, the system user can request the group administrator of any of the groups to which the system user belongs to change the authentication method for the second step of the two-factor authentication managed in association with the system user to the email method.

[0218] When a new system user is registered (S121), the device management system 20 sets the authentication method for the second stage of the two-factor authentication for this system user to the email method (S122). This eliminates the need for system users who consider the email method to be sufficient as the authentication method for the second stage of the two-factor authentication to perform the registration work for an authentication app, thereby improving convenience.

[0219] When the authentication method for the second stage of two-factor authentication associated with a system user is changed from an authentication method other than the authentication app method to the authentication app method (YES in S171), the device management system 20 requests registration of the authentication app (S176), thereby reducing the possibility that the system user will forget to perform the authentication app registration process and improving convenience.

[0220] When the authentication method for the second stage of the two-factor authentication associated with a system user is the authentication app method (YES in S171), and registration of the authentication app fails (YES in S183, YES in S189, or NO in S193), the device management system 20 changes the authentication method for the second stage of the two-factor authentication associated with this system user to the email method (S195).This increases the likelihood that the second stage of the two-factor authentication will be successful without any problems, even if an authentication app is not registered, thereby improving convenience.

[0221] The login authentication process of the present invention includes two-step authentication, but may include only one-step authentication, or may include three or more steps of authentication.

[0222] In this embodiment, the code receiving method of the present invention is an email method. However, the code receiving method of the present invention may be an authentication method other than an email method. For example, the code receiving method of the present invention may be an SMS method in which an authentication code sent to a specific phone number by SMS (Short Message Service) is received and used.

[0223] In this embodiment, the electronic device of the present invention is an image forming apparatus, but the electronic device of the present invention may be an electronic device other than an image forming apparatus. [Explanation of symbols]

[0224] 20 Equipment management system (computer) 24a Equipment Management Program 25a Equipment Management Department 30 Image forming equipment (electronic equipment) 56a Authentication App 320 Authentication method configurable screen (user information editing screen) 323 Authentication method setting section 323a Radio button for email method 323b Authentication App Method Radio Button

Claims

1. A device management system including a device management unit that manages at least one electronic device, the device management unit manages at least one user of the device management system; the device management unit manages, for each user, an authentication method of a specific step authentication as authentication of a specific step of a login authentication process including at least one step authentication for the user to log in to the device management system; an authentication application method that uses an authentication code acquired by an authentication application; and a code reception method that receives and uses an authentication code sent to a specific destination.

2. the device management unit manages at least one group to which at least one of the electronic devices and at least one of the users belong; the device management unit manages whether the specific step authentication is valid for each of the groups; when executing the login authentication process for the user, if the specific step authentication is valid for at least one of the groups to which the user belongs, the device management unit executes the specific step authentication; 2. The device management system according to claim 1, wherein when the device management unit executes the login authentication process for the user, if the specific step authentication is invalid in all of the groups to which the user belongs, the device management unit does not execute the specific step authentication.

3. 3. The device management system according to claim 2, wherein when the device management unit executes the specific step authentication for the user, the device management unit sets the authentication method of the specific step authentication to an authentication method that is managed in association with the user.

4. when generating a user information editing screen as a screen for editing information about the user, if the specific step authentication is enabled for at least one of the groups to which the user belongs, the device management unit displays an authentication method setting section as a section for setting an authentication method of the specific step authentication on the user information editing screen; The device management system according to claim 2, characterized in that when the device management unit generates the user information editing screen for editing information about the user, if the specific step authentication is disabled in all of the groups to which the user belongs, the device management unit does not display the authentication method setting portion on the user information editing screen.

5. the device management unit manages at least one group to which at least one of the electronic devices and at least one of the users belong; the device management unit manages a manager of the group for each of the groups; The device management system according to claim 1, characterized in that the device management unit sets the authentication method of the specific step authentication managed in association with the user belonging to the group to the code reception method in response to an instruction from the administrator of the group.

6. 2. The device management system according to claim 1, wherein when the user is newly registered, the device management unit sets the authentication method of the specific step authentication of the user to the code reception method.

7. 2. The device management system according to claim 1, wherein the device management unit requests registration of the authentication app when an authentication method of the specific step authentication associated with the user is changed from an authentication method other than the authentication app method to the authentication app method.

8. 2. The device management system according to claim 1, wherein, when an authentication method of the specific step authentication associated with the user is the authentication app method, if registration of the authentication app fails, the device management unit changes the authentication method of the specific step authentication associated with the user to the code reception method.

9. A device management system including a device management unit that manages at least one electronic device is implemented on a computer; the device management unit manages at least one user of the device management system; the device management unit manages, for each user, an authentication method of a specific step authentication as authentication of a specific step of a login authentication process including at least one step authentication for the user to log in to the device management system; a device management program characterized in that the device management unit includes, as options for authentication methods for the specific step authentication, a code reception method that receives and uses an authentication code sent to a specific destination, and an authentication app method that uses an authentication code obtained by an authentication app.

Images