Image forming apparatus, method for controlling the same, and program
The image forming apparatus enforces multi-factor authentication with deadlines and notifications to ensure timely activation, addressing vulnerabilities in existing methods and enhancing security against cyber threats.
Patent Information
- Application Number
- JP2024086947
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-05-29
- Publication Date
- 2025-12-11
AI Technical Summary
Existing multi-factor authentication methods for image forming devices, particularly for remote UIs, are vulnerable to unauthorized access if users fail to enable one-time passwords, allowing malicious actors to exploit the system.
An image forming apparatus that enforces multi-factor authentication by setting a deadline for users to activate one-time passwords, disabling device functions if the deadline is not met, and providing notifications to users to ensure timely activation.
Enhances security by reducing the risk of unauthorized access and ensuring that multi-factor authentication is consistently applied, thereby fortifying the device against cyber threats.
Smart Images

Figure 2025179968000001_ABST
Abstract
Description
[Technical Field]
[0001] The present invention relates to an image forming apparatus that performs authentication, a control method thereof, and a program. [Background technology]
[0002] In recent years, cyber attacks have become more sophisticated, and the introduction of multi-factor authentication as a countermeasure against them is progressing. Multi-factor authentication consists of three elements: "knowledge information," "possession information," and "biometric information." "Knowledge information" is information known only to the individual, such as a password or PIN. "possession information" is information held only by the individual, such as an IC card or hardware token (one-time password). "Biometric information" is information or characteristics unique to the individual's living organism, such as fingerprints, veins, or face. Multi-factor authentication, which combines multiple pieces of "knowledge information," "possession information," and "biometric information," can counter cyber attacks and reduce the risk of unauthorized use of the system.
[0003] When using the operation panel of an image forming device installed in an office, a method is provided for user authentication using an IC card distributed as an employee ID card. Since user authentication can be completed simply by holding the IC card over the screen, this method is convenient and has become widespread.
[0004] There are also image forming devices that provide multi-factor authentication means that combine an IC card, which is "possessed information," with a PIN or password, which is "knowledge information." There are also image forming devices that provide multi-factor authentication means that combine an IC card, which is "possessed information," with biometric authentication, etc. (see Patent Document 1).
[0005] In addition, the image forming device has a web server function that can be accessed from a web browser on a PC terminal (personal computer terminal). This allows users to remotely access the image forming device using the web browser on their PC terminal and operate a user interface created in HTML. Hereinafter, this user interface created in HTML will be referred to as the remote UI. Generally, "knowledge information" such as an ID and password is used as a means of authenticating users who use the remote UI of the image forming device.
[0006] One way to achieve multi-factor authentication for the Remote UI is to use one-time passwords, which is an authentication method that uses one-time passwords. Secret information created by the image forming device is displayed using a QR code or similar, and the secret information is shared when the code is read by a one-time password generation application on the user's smartphone. The one-time password is calculated using the secret information and the current time. When a user logs in to the Remote UI, multi-factor authentication is achieved by authenticating the one-time password generated by the application on the user's smartphone in addition to the username and password.
[0007] It is expected that multi-factor authentication for this remote UI will be enabled by an administrator, but security could be improved by forcibly enabling multi-factor authentication for all users at once. [Prior art documents] [Patent documents]
[0008] [Patent Document 1] Patent Publication No. 2019-155610 Summary of the Invention [Problem to be solved by the invention]
[0009] One of the multi-factor authentication methods for image forming devices is multi-factor authentication using one-time passwords on the Remote UI, and when enabling this, an administrator may force all users to set it up. Multi-factor authentication using one-time passwords is only enabled when a user sets it up using their own smartphone when logging in for the first time. Multi-factor authentication will not be applied unless this activation process is performed. If a malicious person steals a specific user's ID and password, there is a risk that they will enable multi-factor authentication on that user's behalf.
[0010] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a method for reducing the risk that a user will leave multi-factor authentication unenabled when multi-factor authentication for a remote UI is enabled by an administrator. [Means for solving the problem]
[0011] An image forming apparatus according to one embodiment of the present invention is an image forming apparatus that performs multi-factor authentication when a user uses an image forming function, and is characterized by having a setting means for enabling a setting that forces the multi-factor authentication, and a disabling means for disabling the functions of a user who has not set user information required to perform multi-factor authentication beyond the period during which multi-factor authentication can be set, when the setting means enables the setting that forces the multi-factor authentication. [Effects of the Invention]
[0012] The present invention provides a method for reducing the risk to users who do not enable multi-factor authentication, and can provide an image forming device with security against cyber attacks. [Brief explanation of the drawings]
[0013] [Figure 1] FIG. 1 illustrates a network configuration. [Figure 2] FIG. 2 is a diagram illustrating a hardware configuration of an MFP. [Figure 3]FIG. 2 is a diagram illustrating a software configuration. [Figure 4] FIG. 10 illustrates a user interface for multi-factor authentication settings. [Figure 5] FIG. 10 illustrates a user interface for user management. [Figure 6] FIG. 10 is a diagram showing a user interface for editing my profile. [Figure 7] 10 is a flowchart showing the operation flow during user authentication in the Remote UI. [Figure 8] 1A to 1C are diagrams showing screens and screen transitions that the Remote UI provides to a web browser on a PC. [Figure 9] 10 is a flowchart illustrating an operation flow of a request for enabling multi-factor authentication. [Figure 10] FIG. 10 is a diagram illustrating an example of a notification when the multi-factor authentication activation deadline has passed. [Figure 11] 10 is a flowchart showing screens and screen transitions in a local UI. [Figure 12] 10 is a flowchart illustrating an operation flow during user authentication in a local UI. DETAILED DESCRIPTION OF THE INVENTION
[0014] Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[0015] [Embodiment 1] An embodiment of the present invention will be described using an MFP (Multifunction Peripheral) equipped with functions such as copying, printing, and scanning, which is installed in an office, as an example of an image forming apparatus to which the present invention is applied.
[0016] <System configuration> A network configuration in an office environment of this embodiment will be described with reference to Fig. 1. A communication device 101 is an MFP (Multifunction Peripheral) to which the present invention is applied. The communication device 101 communicates with an information processing device 102 (e.g., a personal computer (PC)) connected via a network LAN 103. A user can access the communication device 101 from a web browser on a PC terminal and use the remote UI of the communication device 101. The communication device 101 can also receive print jobs and access requests for documents stored in the communication device 101 from a terminal (e.g., PC 102).
[0017] In this embodiment, the communication device 101 is described as an MFP, but it may be an inkjet printer or a fax machine. Also, the information processing device 102 is described as a PC, but it may be a mobile terminal such as a smartphone or tablet, and any device having a browser function is applicable.
[0018] Each user owns one or more mobile terminals 104. To implement this embodiment, the mobile terminals do not need to be connected to the network LAN 103. A mobile application compatible with TOTP (Time-based One-time Password), which will be described later, is installed on the mobile terminal 104, and is used to generate one-time passwords. Although not shown, it is assumed that there are multiple other MFPs, PC terminals, and mobile terminals with the same configuration in the office environment, and each of these can be linked in a manner similar to the mechanism described below.
[0019] <Hardware configuration> 2 is a simplified diagram showing the hardware configuration of the communication device 101. The CPU 201 is a central processing unit (processor) that controls the overall operation of the communication device 101. The RAM (Random Access Memory) 203 is a volatile memory and a work area that is used as a temporary storage area for expanding various control programs stored in the ROM 202 and HDD 204.
[0020] The ROM 202 is a nonvolatile memory that stores a boot program for the communication device 101. The HDD 204 is a nonvolatile hard disk with a larger capacity than the RAM 203. The HDD 204 stores a control program for the communication device. The OS (Operating System) and application programs are also stored in the HDD 204.
[0021] When the communication device 101 starts up, the CPU 201 executes a boot program stored in the ROM 202. This boot program reads out an OS (Operating System) program stored in the HDD 204 and loads it on the RAM 203. After executing the boot program, the CPU 201 subsequently executes the OS program loaded on the RAM 203, thereby controlling the communication device 101. The CPU 201 also stores data used for operations according to the control program on the RAM 203 and reads and writes the data.
[0022] In the communication device 101, one CPU 201 executes each process shown in the flowcharts described below, but other configurations are also possible. For example, multiple CPUs or microprocessors (MPUs) can cooperate to execute each process shown in the flowcharts described below. Also, some of the processes described below can be executed using hardware circuits such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field-Programmable Gate Array).
[0023] The operation panel 205 is a touch-operable display. The printer 206 is a printer engine that prints print data received from an external device via a communication unit 208 and digital data acquired from a scanner 207. The scanner 207 is a scanner device that reads paper documents and converts them into digital data. The printer 206 and scanner 207 are controlled by the CPU 201 and ROM 202, making it possible to provide an image forming function to the user.
[0024] The communication unit 208 is a network interface for connecting to the Internet or an office LAN (Local Area Network). The IC card reader 209 is a device for reading information used for user authentication from an IC card, and is a unit required for realizing IC card authentication.
[0025] <Software configuration> 3 is a simplified diagram showing the software configuration of the communication device 101. A local UI 301 of the communication device 101 uses the display of the operation panel 205 to provide a user interface for a user locally accessing the communication device 101 to change settings and use functions of the communication device 101. A remote UI 302 has an HTTP (Hypertext Transfer Protocol) server function and provides a user remotely accessing the communication device 101 with a user interface configured in HTML (HyperText Markup Language).
[0026] A user can access the remote UI 302 using a web browser on a PC terminal to change the settings and use the functions of the communication device 101. The web browser on the PC terminal displays a user interface configured in HTML. The user can change the settings and use the functions by operating the user interface displayed on the web browser.
[0027] The user authentication service 303 is a software module that authenticates users who use the local UI 301 and the remote UI 302. The user authentication service 303 authenticates users who use the local UI 301 with an IC card or a PIN number. It also authenticates users who use the remote UI 302 with a username, password, and one-time password. The IC card reader driver 304 is a driver that controls the IC card reader 209, obtains information from the IC card, and provides the IC card information to the user authentication service 303.
[0028] <One-time password> The one-time password used in this embodiment will be described below. The one-time password can be generated using TOTP (Time-based One-time Password) defined in RFC6238. In this method, a one-time password, which is authentication information, is generated using a TOTP secret generated for each user and time information. The TOTP secret is a random number. In recent years, mobile applications (smartphone applications) that support TOTP have become widespread.
[0029] Examples include Google's Google Authenticator (registered trademark) and Microsoft's Microsoft Authenticator (registered trademark). The TOTP secret is stored in a mobile application by registering the TOTP secret as a character string in the TOTP-compatible mobile application or by using the mobile application to scan a QR code containing the TOTP secret information. This allows the TOTP secret to be shared between the TOTP secret issuer and the mobile application. The TOTP-compatible mobile application generates a one-time password based on the TOTP secret and the time.
[0030] In addition to TOTP-compatible mobile applications, there are also TOTP-compatible plug-ins that can be installed as an extension of a PC web browser. In this embodiment, the TOTP secret issuer is the user authentication service 303. Each user of the communication device 101 uses a TOTP-compatible mobile application or web browser plug-in. Generally, a one-time password generated using software such as a mobile application or web browser plug-in is called a software token. An authentication method using a software token is called software token authentication.
[0031] In this embodiment, upon receiving a request from the local UI 301 or remote UI 302 that has detected a user operation, the user authentication service 303 generates a TOTP secret, generates a one-time password, and verifies the one-time password.
[0032] In addition, in this embodiment, a state in which a TOTP secret associated with an account is recorded in the user information table described below is determined to be a one-time password valid state, and a state in which a TOTP secret is not recorded is determined to be a one-time password invalid state.
[0033] <User information> The following describes the user information managed by the user authentication service 303. The user authentication service 303 stores and manages user information in a user information table (Table 1) as shown in Table 1. The user information table is a database recorded on the HDD 204. Note that a database of another node on the network may be used after encrypting the communication path and storage and preventing tampering. The user information table records the card ID, PIN, password, TOTP secret, user role, email address, etc. used for IC card authentication.
[0034] [Table 1]
[0035] A role is information indicating a user's usage rights for the communication device 101. Examples of each role and usage rights are shown in the role information table (Table 2) below. In addition to the role definitions that the communication device 101 has when shipped from the factory, the user may be able to set detailed usage rights and create new roles. Note that a setting change in Table 2 refers to the act of changing values set in the communication device 101, such as user authentication settings and user management, which will be described later. Note that it may also be possible to change a wide variety of settings, such as the network settings and print function settings of the communication device 101. Administrator is a role given to an administrator user, and GeneralUser and / or LimitedUser are roles given to general users.
[0036] [Table 2]
[0037] <User authentication settings> Next, a description will be given of the user authentication setting provided in the communication apparatus 101. Fig. 4 shows an example of a UI (user interface) for the user authentication setting of the communication apparatus 101 provided by the remote UI 302. A similar UI may be provided for the administrator not only by the remote UI 302 but also by the local UI 301.
[0038] Setting 401 shows the entire screen for configuring user authentication settings. Only administrators with the Administrator role can access it. Setting 402 is a multi-factor authentication setting for local access. Setting 403 is a multi-factor authentication setting for remote access. Settings 404 are authentication settings for the local UI, and provide options of "no authentication" and "IC card authentication."
[0039] Setting 405 allows the user to select whether to enable or disable multi-factor authentication settings for local access. Although not shown in the figures in this proposal, turning this setting on enables multi-factor authentication that combines an IC card, which is "possessed information," with a PIN, which is "knowledge information." Authentication using a one-time password generated from a hardware token or software token as "possessed information" may also be applied. While this embodiment provides separate multi-factor authentication settings for the local UI and the remote UI, a single multi-factor authentication setting may be provided as a common setting that applies to both the local UI and the remote UI.
[0040] Setting 406, "Use Multi-Factor Authentication (One-Time Password)," is a setting related to multi-factor authentication for the Remote UI. The following options are available to the user: "No coercion" "Enforce the use of one-time passwords for administrators only" "Force all users to use one-time passwords" If "Not Enforced" is selected, users accessing the Remote UI are authenticated using a user name and password. Whether or not to use a one-time password is up to each user. If a user has enabled a one-time password, the user is prompted to enter a one-time password in addition to authenticating the user name and password. If a one-time password is not enabled, the user is logged in to the Remote UI 302 only if the user name and password are successfully authenticated, without being prompted to enter a one-time password.
[0041] If "Enforce use of one-time passwords for administrators only" or "Enforce use of one-time passwords for all users" is selected, and if a user of that account attempts user authentication to the Remote UI 302 without first enabling one-time passwords, a screen for setting a one-time password is displayed when logging in to the Remote UI, prompting the user to set a one-time password.
[0042] Setting 407 "Multi-factor authentication configurable period" is a setting that specifies the expiration date of one-time passwords when "Enforce use of one-time passwords only for administrators" or "Enforce use of one-time passwords for all users" is selected. In other words, it is used to set the period during which multi-factor authentication can be configured.
[0043] If the one-time password is not activated within this period, the process is defined in setting 408 "Processing when not activated within the configurable period." Disable a user's account - Disable Remote UI login The process will be performed according to one of the settings.
[0044] When a user's account is disabled, all authentication methods, including the local UI and remote UI, are stopped. In this case, the user will not be able to log in unless an administrator undoes the account disablement.
[0045] When disabling Remote UI login, only the use of the Remote UI is prohibited. Use of the Local UI can continue. Some usage environments only use Local UI authentication using an IC card, so in such environments, the account itself is not disabled, but only the use of the Remote UI is prohibited.
[0046] Setting 409 "Notify user of multi-factor authentication activation request" is a setting for notifying the user that the multi-factor authentication setting has been activated. The means of notifying the user is at least email. There are two settings for when to notify the user: setting 410 for whether to notify when the multi-factor authentication setting is activated in setting 405, and setting 411 for notifying the user periodically. For periodic notifications, the sending interval and sending time can be set, and in Figure 4, the setting is to notify at 12:00 every seven days. The method of notification is not shown in this proposal, but it may be set to send at a specified time.
[0047] These settings for the expiration date of multi-factor authentication and the notification setting for requesting activation of multi-factor authentication are intended to solve the problem that if a user does not activate multi-factor authentication using one-time passwords, a third party who has stolen the user's ID and password can set a one-time password and take over the account.
[0048] <User Management> 5 shows an example of a UI for managing user accounts of the communication apparatus 101, provided by the remote UI 302. In addition to the remote UI 302, a similar UI may be provided for the administrator on the local UI 301.
[0049] Screen 501 is a user management screen for managing a list of user accounts. Only administrators with the Administrator role can access it. The user management screen 501 provides functions for registering new user accounts and selecting registered accounts to edit or delete them. For example, if an "Admin" selects the "Alice" account on the user management screen 501 and presses the edit button, the remote UI 302 displays the user edit screen 502. On the user edit screen 502, the password, PIN, card ID, email address, role, and so on can be edited and saved.
[0050] The status (enabled / disabled) of the one-time password used for user authentication of the Remote UI is also displayed on the user edit screen 502. On the user edit screen 502, the administrator can initialize (disable) the one-time password by pressing the disable button 503.
[0051] <Edit My Profile> 6 shows an example of a UI for editing My Profile provided by the remote UI 302. The My Profile editing screen 601 is a UI that allows a user who has logged in to the remote UI 302 to check and edit their own account information. It is provided to all users who can log in to the remote UI 302. A similar UI may be provided not only on the remote UI 302 but also on the local UI 301.
[0052] The My Profile Edit screen 601 allows users to edit and save their password, PIN, and email address. Users cannot change their own role. The My Profile Edit screen 601 also provides functions for checking the status of the one-time password used for user authentication of the Remote UI and for enabling or disabling it. When it detects that the Enable button 602 has been pressed, the Remote UI 302 generates a QR code containing the TOTP secret via the user authentication service 303 and displays the one-time password enable screen 603.
[0053] The information in the QR code includes the identifier of the communication device 101 that issues the TOTP secret, the user account name, the TOTP secret, the one-time password generation algorithm, the character length of the one-time password, the validity period (seconds), and the like. otpauth: / / totp / MFP101:alice@comon.com?secret=GVQYVMXCE5KDCMXUKQIKLZJEHCDYHLHG&issuer=MFP101&algorithm=SHA1&digits=6&period=30 The user photographs a QR code (registered trademark) using a TOTP-compatible mobile application on the mobile terminal 104. The mobile application obtains information, including the TOTP secret, from the QR code. Using the information obtained from the QR code and time information, the mobile application generates a one-time password using the method specified in RFC6238 and displays it on the mobile application screen.
[0054] The one-time password activation screen 603 prompts the user to enter a one-time password to confirm that the one-time password has been correctly generated using the mobile device. When a one-time password is entered on the one-time password activation screen 603, the remote UI 302 requests verification from the user authentication service 303. The user authentication service 303 uses the current time information and TOTP secret according to the method specified in RFC6238 to generate a one-time password and verify it against the entered one-time password. The one-time password changes every 30 seconds.
[0055] To allow for differences in the time settings between the mobile device and the communication device 101, one-time passwords 30 seconds before and after may also be calculated and compared with the multiple one-time passwords. If the one-time passwords are successfully matched, the user authentication service 303 associates the TOTP secret with the account and stores it in the user information table (Table 1), completing the one-time password activation process. The settings and user information table described above are stored in the HDD 204 and are referenced when the operations described below are performed.
[0056] <Login behavior> Next, the operation when a user logs in to the communication device 101 will be described with reference to a flowchart. In this embodiment, the procedures shown in the following flow chart are recorded in the software programs of the local UI 301, remote UI 302, user authentication service 303, and IC card reader driver 304. The software programs are stored in non-volatile storage such as the ROM 202 or HDD 204, and are loaded into the RAM 203, and the flow shown in the flowchart is executed by the CPU 201. Furthermore, the software such as the local UI 301, remote UI 302, user authentication service 303, and IC card reader driver 304 provide APIs to each other and operate in harmony by mutually using the APIs. In the description of the operation flow, the calling of APIs will be omitted.
[0057] <Remote UI login operation flow> The operational flow when logging in to the Remote UI will be explained with reference to Figures 7 and 8. Figure 7 is a flowchart showing the operational flow when authenticating a user in the Remote UI. Figure 8 shows the screens created in HTML that the Remote UI provides to a PC's web browser and the screen transitions. When the Remote UI 302 detects access to the Remote UI 302, it displays the Remote UI login screen 801.
[0058] In S701, the user authentication service 303 detects a login operation when the user enters a username and password on the login screen 801 of the Remote UI and presses the login button. In S702, the user authentication service 303 authenticates the user by referencing the user information table (Table 1) and verifying the entered username and password. If verification fails, the service displays an authentication error and then displays the login screen 801, which prompts the user to enter the username and password again. If verification of the username and password is successful, the service identifies the account for which verification was successful.
[0059] Next, in S703, the user authentication service 303 references the TOTP secret in the user information table (Table 1) of the identified account and determines whether the TOTP secret has been registered. If the TOTP secret has been registered, in S704 the user authentication service 303 determines that the one-time password has been activated, and displays the one-time password input screen 802 to request entry of the one-time password.
[0060] Next, in S705, the user authentication service 303 compares the input one-time password with the one-time password calculated from the time information and the TOTP secret, and authenticates the one-time password. If the input one-time password is correct, in S706 the user authentication service 303 performs processing to log the user into the communication device 101. The login processing refers to the user information table (Table 1) and the role information table (Table 2), grants the role of the user who is logging in and the authority associated with the role, and controls the user to log in to the communication device 101.
[0061] The login operation is terminated by displaying a menu screen 803 for allowing the user to use the functions of the communication device 101 provided by the remote UI 302. When the menu screen 803 is displayed, functions that the user does not have permission to use are grayed out to prevent selection. If the one-time password verification fails, the authentication service 303 displays a message to the user to inform them that the one-time passwords do not match, and displays the one-time password input screen 802 again to request the user to re-enter the one-time password. If input errors are made more than a certain number of times, the system determines that the account is under attack and locks out the account for a certain period of time.
[0062] If it is determined in S703 that a TOTP secret has not been registered and that one-time passwords have not been enabled, the user authentication service 303 refers to the setting 406 "Use of multi-factor authentication (one-time password)" stored in the HDD 204 and the role of the identified account in S707. Then, it determines whether the use of one-time passwords is forced for the account attempting to log in. For example, if "Force use of one-time passwords for administrators only" is set and the role of the identified user's account is Administrator, it determines that use of one-time passwords is forced.
[0063] If the use of a one-time password is not forced, in S706 the user authentication service 303 performs processing to log the user into the communication device 101. If the use of a one-time password is forced, in S708 the user authentication service 303 displays a one-time password activation screen 804 and prompts the user to activate the one-time password and confirm the one-time password.
[0064] The user authentication service 303 then verifies the entered one-time password, and if the one-time password is correct, in S709, the user authentication service 303 records the TOTP secret in the user information table (Table 1) and determines whether the one-time password was successfully validated. If it is confirmed that the one-time password has been successfully validated, in S706, the user authentication service 303 performs processing to log the user in to the communication device 101. If it detects that the user has pressed the Cancel button to refuse to validate the one-time password, in S710, the user authentication service 303 displays the login screen 801 of the remote UI again.
[0065] <Multi-factor authentication activation request operation flow> The operation flow when the setting 410 for periodically notifying the user of a multi-factor authentication activation request is enabled will be described using Fig. 9. The processing of this flowchart starts when the timer processing created in advance by the user authentication service 303 based on the time set in the setting 411 arrives at the set time.
[0066] Table 3 is the same as the user information table (Table 1), but only the necessary items are shown for the purpose of explanation.
[0067] [Table 3]
[0068] In S901, the user authentication service 303 starts notification processing at a predetermined time according to the settings in 411. In S902, the user authentication service 303 references the TOTP secret in the user information table (Table 3), checks whether the TOTP secret has been registered, and identifies account information for which multi-factor authentication has not been set. If the TOTP secret has been registered, it determines that multi-factor authentication has been enabled, and if it has not been registered, it determines that multi-factor authentication has not been set. This identification processing applies to all users for whom multi-factor authentication has not been enabled.
[0069] Next, in S903, the user authentication service 303 checks the activation expiration date of the multi-factor authentication of the RUI in Table 3, compares it with the current time, and checks whether the expiration date has passed for all users. For users who are within the expiration date, in S906, the user authentication service 303 sends an email notification indicating the activation expiration date, as shown in the notification example 1001 in Fig. 10.
[0070] For a user whose account has expired, in S904 the user authentication service 303 checks the process to be taken when the account has expired by referring to the "Process to be taken when the account is not set within the set period" in the setting 408. In S905, if the user's account is set to be invalidated, the user authentication service 303 writes "No" to the setting value for whether the account can be used in the user information table (Table 3) for that user.
[0071] If the value of setting 408 is set to prohibit use of the RUI, in S907 the user authentication service 303 writes "No" to the setting value for RUI usage in the user information table (Table 3) for that user. For users whose accounts were invalidated in S905 or whose use of the RUI was prohibited in S907, in S906 the user authentication service 303 notifies them by email indicating that the expiration date has passed, as shown in notification example 1002. In S908, the user authentication service 303 sends the email notification, and then the periodic execution process ends.
[0072] Although not shown in this proposal, for users whose subscriptions have already expired, email notifications may be sent each time S901 is periodically executed, or only once at the time the subscription expires.
[0073] <Flow when the Remote UI multi-factor authentication activation period has expired when logging in to the Local UI> 11 and 12, an embodiment in which a warning screen is displayed and settings can be made when the activation period for multi-factor authentication for the remote UI has expired when logging in from the local UI will be described. FIG. 11 shows the screens and screen transitions that the local UI displays on the operation panel 205. FIG. 12 is a flowchart showing the operation flow during IC card authentication in the local UI. The processing in this flowchart begins when the user holds their own IC card over the IC card reader 209.
[0074] If "IC card authentication" is set in the authentication settings 404 of the local UI, when the communication device 101 starts up, the local UI 301 displays an IC card authentication screen 1101 on the operation panel 205. The user authentication service 303 uses the IC card reader driver 304 to operate the IC card reader 209 and make it ready to detect an IC card.
[0075] In S1201, the user authentication service 303 detects via the IC card reader driver 304 that an IC card has been held over the card reader 209. In S1202, the user authentication service 303 acquires the card ID of the detected IC card and authenticates the IC card by comparing it with the IC cards registered in the user information table (Table 1), and determines the result. In the case of an unregistered card ID, an authentication error is displayed, and then the IC card authentication screen 1101 is displayed again. If the comparison with the registered card ID is successful, the account associated with the card ID is identified.
[0076] In S1203, the user authentication service 303 checks whether the specified account has a value in the RUI activation expiration date field in the user information table (Table 3) and whether the account has expired by comparing it with the current time.
[0077] If the activation period has not passed, in S1211, the user authentication service 303 refers to the user information table (Table 1) and the role information table (Table 2) to grant the role of the user who is logging in and the authority associated with the role. Then, it performs control to log the user in to the communication device 101. In S1212, the user authentication service 303 displays the menu screen 1102 for allowing the user to use the functions of the communication device 101 provided by the local UI 301, and ends the login operation. In the display of the menu screen 1102, it performs control to gray out functions that the user does not have authority to use so that they cannot be selected.
[0078] If the expiration date has passed in S1203, the user authentication service 303 checks in S1221 whether the item for notifying users of expiration in the user information table (Table 3) is enabled. If the setting is such that no notification is to be sent, the user authentication service 303 performs login processing in S1211. If the setting is such that notification is to be sent, the user authentication service 303 displays a message in S1204, as shown on the warning screen 1103, indicating that the Remote UI activation date has expired. The warning screen displays the following options: Configure settings Set up later Do not display this screen as I do not use it. In S1205, the user authentication service 303 checks the setting values selected by the user. If "Perform settings" is selected, in S1206, the user authentication service 303 starts the web browser 305 and accesses the HTTP server of the remote UI, causing the web browser to display browser screen 1104. The screen displayed here is the same as screen 804. Next, in S1209, the user authentication service 303 checks whether the one-time password entered on browser screen 1104 is correct.
[0079] The process of verifying whether the one-time password is correct is the same as the procedure of the remote UI described in embodiment 1. If the one-time password is correct, in S1211 the user authentication service 303 performs login processing and displays the menu screen 1102. If the one-time password is incorrect, in S1210 the user authentication service 303 transitions to the IC card authentication screen 1101.
[0080] If "Set later" is selected in S1205, in S1207 the user authentication service 303 performs processing to update the RUI activation expiration date item in the user information table (Table 3) to a date and time extended from the current date and time by the period set in the "Multi-factor authentication configurable period" setting 407. If "Do not display this screen as I will not use" is selected in S1205, in S1208 the user authentication service 303 changes the setting value of the item in the user information table (Table 3) regarding whether to notify of expiration to "Do not do."
[0081] As described above, the communication device 101 described in this embodiment provides a method for reducing the risk to users who do not enable multi-factor authentication, and can provide an image forming device with security against cyber attacks.
[0082] [Other Examples] The present invention can also be realized by supplying a program that realizes one or more functions of the above-described embodiments to a system or device via a network or a storage medium, and having one or more processors in the computer of the system or device read and execute the program. It can also be realized by a circuit (e.g., ASIC) that realizes one or more functions.
[0083] Although the preferred embodiments of the present invention have been described in detail above, the present invention is not limited to such specific embodiments, and various modifications and changes are possible within the scope of the gist of the present invention described in the claims. [Explanation of symbols]
[0084] 301 Local UI 302 Remote UI 303 User Authentication Service
Claims
1. An image forming apparatus that performs multi-factor authentication when a user uses an image forming function, a setting means for enabling the setting for forcing the multi-factor authentication; and a disabling means for disabling the functions of a user who has not set user information required to execute multi-factor authentication beyond the period during which multi-factor authentication can be set, when the setting means enables the setting to force multi-factor authentication.
2. 2. The image forming apparatus according to claim 1, wherein the invalidation of the user's functions is the suspension of the user's account or the suspension of use of some of the functions of the image forming apparatus.
3. 3. The image forming apparatus according to claim 1, further comprising a notification unit that notifies a user that the multi-factor authentication has been forced.
4. 4. The image forming apparatus according to claim 3, wherein the setting unit sets the period during which the multi-factor authentication can be set, as well as the timing of the notification unit notifying the user, in addition to the setting to force the multi-factor authentication.
5. 5. The image forming apparatus according to claim 1, wherein the multi-factor authentication is one-time password authentication that is executed after IC card authentication.
6. A control method for an image forming apparatus that performs multi-factor authentication when a user uses an image forming function, comprising: a setting step of enabling the setting for enforcing multi-factor authentication; a disabling step of disabling functions of a user who has not set user information required to execute multi-factor authentication beyond a period during which multi-factor authentication can be set, when the setting for forcing multi-factor authentication is enabled by the setting step.
7. 7. The control method according to claim 6, wherein the invalidation of the user's functions is the suspension of the user's account or the suspension of use of some of the functions of the image forming apparatus.
8. The control method according to claim 6 or 7, further comprising a notification step of notifying a user that the multi-factor authentication has been forced.
9. The control method according to claim 8, wherein the setting step includes setting the multi-factor authentication to be forced, setting a period during which the multi-factor authentication can be set, and setting the timing of notifying the user by the notification step.
10. 10. The control method according to claim 6, wherein the multi-factor authentication is one-time password authentication that is performed after authentication using an IC card.
11. A program for causing a computer to execute the control method according to any one of claims 6 to 10.
Citation Information
Patent Citations
Image formation device, authentication method of image formation device, program and print system
JP2019155610A