Determination method in image forming apparatus and processing apparatus

Abstract

To provide an image forming device or the like, which is capable of appropriately performing a policy check.SOLUTION: An image forming device includes: a storage unit configured to store user authentication information; a setting unit configured to set, for each user, an authentication requirement for the authentication information; an authentication unit configured to authenticate the user based on the authentication information; and a determination unit configured to perform determination as to whether the authentication information on the user authenticated by the authentication unit satisfies the authentication requirement corresponding to the user.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] This disclosure relates to an image forming apparatus and the like.

Background Art

[0002] In machines such as image forming apparatuses, in order to ensure security, there are some that have a function of performing processing and control based on a security policy, and technologies related to security policies have also been proposed. For example, a technology has been proposed in which the security level specified by a user from security levels divided step by step according to a security policy is collectively set for all target items of security checks (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] One type of security policy is a set of rules (policies) regarding passwords. For example, some machines include a function to set rules (policies) regarding passwords in order to ensure machine security. When such a function is enabled, a check (policy check) is performed to determine whether the password meets the policy. If usability is prioritized, it is conceivable that policy checks be performed only when the password is changed or a new user is registered. On the other hand, if security is prioritized, it is conceivable that policy checks be performed not only when the password is changed or a new user is registered, but also when the user logs in. Whether to prioritize usability or security depends on the user and the usage scenario, so it is desirable that policy checks be performed according to the settings made by the user, and according to the usage scenario of the machine. However, prior art such as Patent Document 1 did not take these issues into consideration.

[0005] In light of the issues described above, this disclosure aims to provide an image forming apparatus, etc., that can appropriately perform policy checks. [Means for solving the problem]

[0006] To solve the above-mentioned problems, the image forming apparatus of the present disclosure is characterized by comprising: a storage unit for storing user authentication information; a setting unit for setting authentication requirements for the authentication information for each user; an authentication unit for authenticating the user based on the authentication information; and a determination unit for determining whether the authentication information of a user authenticated by the authentication unit satisfies the authentication requirements corresponding to that user.

[0007] Furthermore, the determination method in the processing apparatus of this disclosure is characterized by storing user authentication information, setting authentication requirements for the authentication information for each user, authenticating the user based on the authentication information, and determining whether the authentication information of the authenticated user satisfies the authentication requirements corresponding to that user. [Effects of the Invention]

[0008] This disclosure makes it possible to provide an image forming apparatus, etc., that can perform appropriate policy checks. [Brief explanation of the drawing]

[0009] [Figure 1] This is a perspective view of the image forming apparatus in the first embodiment. [Figure 2] This is a diagram illustrating the functional configuration of the image forming apparatus in the first embodiment. [Figure 3] This figure shows an example of the data structure of user information in the first embodiment. [Figure 4] This figure shows an example of the data structure of deleted user information in the first embodiment. [Figure 5] This figure shows an example of the data structure of the setting table in the first embodiment. [Figure 6] This is a flowchart of the main processing in the first embodiment. [Figure 7] This is a flowchart of the login eligibility determination process in the first embodiment. [Figure 8] This is a flowchart of the password change process in the first embodiment. [Figure 9] This figure shows an example of the settings screen in the first embodiment. [Figure 10] This figure shows an example of the settings screen in the first embodiment. [Figure 11] This figure shows an example of the data structure of user information in the second embodiment. [Figure 12] This figure shows an example of the data structure of the setting table in the second embodiment. [Figure 13] This is a flowchart of the login eligibility determination process in the second embodiment. [Figure 14] This is a flowchart of the password change process in the second embodiment. [Figure 15] This figure shows an example of the settings screen in the second embodiment. [Figure 16]It is a diagram showing an example of the data configuration of user information in the third embodiment. [Figure 17] It is a diagram showing an example of the data configuration of the setting table in the third embodiment. [Figure 18] It is a flowchart of the login availability determination process in the third embodiment. [Figure 19] It is a flowchart of the password change process in the third embodiment. [Figure 20] It is a diagram showing an example of the screen of the setting screen in the third embodiment.

Mode for Carrying Out the Invention

[0010] Hereinafter, an embodiment for implementing the present disclosure will be described with reference to the drawings. Note that the following embodiments are examples for explaining the present disclosure, and the technical scope of the invention described in the claims is not limited to the following description.

[0011] [1. First Embodiment] [1.1 Functional Configuration] The first embodiment is an embodiment when the image forming apparatus of the present disclosure is applied to the multifunction device 10. The multifunction device 10 is also called an MFP (Multi-Function Peripheral / Printer) and has basic functions as an MFP (copy function, print function, scan function, etc.).

[0012] FIG. 1 is an external perspective view of the multifunction device 10 according to the first embodiment, and FIG. 2 is a block diagram showing the functional configuration of the multifunction device 10. As shown in FIG. 2, the multifunction device 10 includes a control unit 100, an image input unit 120, an image forming unit 130, a display unit 140, an operation unit 150, a storage unit 160, and a communication unit 190.

[0013] The control unit 100 is a functional unit for controlling the entire multifunction device 10. The control unit 100 realizes various functions by reading and executing various programs stored in the memory unit 160, and is composed of, for example, one or more arithmetic units (CPU (Central Processing Unit)). The control unit 100 may also be configured as a SoC (System on a Chip) having multiple functions among those described below.

[0014] The control unit 100 functions as an image processing unit 102, a user management unit 104, an authentication unit 106, a setting unit 108, and an authentication information determination unit 110 by executing a program stored in the storage unit 160.

[0015] The image processing unit 102 performs various image-related processing. For example, the image processing unit 102 performs sharpening and grayscale conversion processing on images input via the image input unit 120 and the communication unit 190.

[0016] The user management unit 104 manages users who use the multifunction printer 10. For example, the user management unit 104 manages users registered to use the multifunction printer 10 by storing user information (user information) of the multifunction printer 10 in the user information storage area 162, which will be described later. User information includes not only the user's own information such as the user's name and authority, but also authentication information (login name, password, etc.) used to authenticate the user.

[0017] Furthermore, the user management unit 104 manages users by updating and deleting stored user information. For example, when a user changes their password, the unit updates the password by storing the new password in the user information of the user whose password is being changed.

[0018] Furthermore, if a user is deleted, the user management unit 104 deletes the user information of the user to be deleted from the user information storage area 162 and stores the deleted user's information in the deleted user information storage area 164. Also, if there is a user who has not logged into the multifunction printer 10 for a certain period of time, the user management unit 104 may delete the user information of that user, thereby removing that user from the list of users who can use the multifunction printer 10. Also, if a user is registered, the user management unit 104 stores the user information of that user in the user information storage area 162. At this time, if the setting table 166 described later is set to "enabled" to prohibit the reuse of the multifunction printer 10 for a deleted user, and an operation to register the same user as the deleted user is performed within the set period, the user management unit 104 may prohibit the registration of that user.

[0019] The authentication unit 106 realizes the user authentication function in the multifunction printer 10 by authenticating the user. For example, the authentication unit 106 displays a login screen on the display unit 140, and if the authentication information entered by the user via the login screen matches the authentication information contained in any of the pre-stored user information, it authenticates the user corresponding to that authentication information as a user who will use the multifunction printer 10.

[0020] The authentication method described above is called knowledge authentication, but the authentication unit 106 can use various other authentication methods. For example, the authentication unit 106 can use authentication methods such as possession authentication or biometric authentication. The authentication unit 106 may also authenticate the user using an external device that provides authentication functions, such as an authentication server. In this case, the authentication unit 106 sends the authentication information entered by the user via the login screen to the authentication server and authenticates the user according to the authentication result received from the authentication server.

[0021] The setting unit 108 provides setting means for performing various settings (system settings) of the multifunction printer 10. For example, the setting unit 108 displays a screen (setting screen) for displaying and changing the settings of the multifunction printer 10 on the display unit 140 in response to user operation, and applies the settings to the multifunction printer 10 by storing the content entered via the setting screen in the setting table 166, which will be described later.

[0022] The authentication information determination unit 110 determines whether the authentication information of a user authenticated by the authentication unit 106 satisfies the authentication requirements. Here, the authentication requirements are the requirements for determining whether the authentication information used to authenticate a user is appropriate. Authentication requirements are policies set by administrators to ensure the security of an organization, etc. Authentication requirements are sometimes called security policies. In this embodiment, as an example of authentication requirements, a password policy, which is a policy regarding passwords, will be explained as an example. For example, the authentication information determination unit 110 determines whether the password included in the user information corresponding to the authenticated user satisfies the authentication requirements for passwords (password policy). Note that authentication requirements may also include policies regarding the user's account name, the number of times and the period for changing the password, and the authentication method (for example, whether email authentication is required).

[0023] The image input unit 120 inputs images to the multifunction printer 10. The image input unit 120 is composed of, for example, a scanner device that reads a document placed on the document glass. The scanner device is a device that converts an image into an electrical signal using an image sensor such as a CCD (Charge Coupled Device) or CIS (Contact Image Sensor), and then quantizes and encodes the electrical signal. The image input unit 120 is also composed of an interface (terminal) for reading images stored in a USB (Universal Serial Bus) memory, and images may be input by reading from the USB memory. Alternatively, the image input unit 120 may also input images by receiving them from other devices via the communication unit 190.

[0024] The image forming unit 130 forms (prints) an image on a recording medium such as recording paper. The image forming unit 130 is composed of a printing device such as a laser printer using an electrophotographic method. For example, the image forming unit 130 feeds recording paper from a paper feed tray 132 provided in the multifunction printer 10, forms an image on the surface of the recording paper, and ejects the recording paper from an output tray 134 provided in the multifunction printer 10.

[0025] The display unit 140 displays various information. The display unit 140 is composed of a display device such as an LCD (Liquid Crystal Display), an OLED (Electro-Luminescence) display, or a microLED (Light Emitting Diode) display.

[0026] The operation unit 150 receives operation instructions from the user of the multifunction printer 10. The operation unit 150 is composed of input devices such as key switches (hard keys) and touch sensors. The method for detecting input by contact (touch) in the touch sensor can be any common detection method, such as resistive, infrared, electromagnetic induction, or capacitive touch. The multifunction printer 10 may also be equipped with a touch panel in which the display unit 140 and the operation unit 150 are integrally formed.

[0027] The storage unit 160 stores various programs and data necessary for the operation of the multifunction printer 10. The storage unit 160 is composed of storage devices such as a semiconductor memory SSD (Solid State Drive) or an HDD (Hard Disk Drive).

[0028] The storage unit 160 reserves a user information storage area 162 and a deleted user information storage area 164, and stores the setting table 166.

[0029] The user information storage area 162 stores user information. User information includes, for example, an ID that identifies the user (e.g., "1"), a login name (e.g., "Admin") and password (e.g., "ABC@123"), the user's username (e.g., "Administrator a"), the user's last login date and time (e.g., "May 12, 2022, 20:00:02"), and the user's permission level (e.g., "Administrator").

[0030] The login name and password included in the user information are authentication information used to authenticate the user. The permission level is information that indicates the user's permissions. In this embodiment, the permission level will store either "administrator," who has the authority to manage the multifunction device 10, or "general user," who does not have the authority to manage the multifunction device 10.

[0031] The deleted user information storage area 164 stores information about users deleted from the multifunction printer 10 (deleted user information). Deleted user information includes, for example, as shown in Figure 4, an ID that identifies the user (e.g., "101"), a login name (e.g., "UserX"), a password (e.g., "abc@789"), the user's username (e.g., "UserX"), the date and time the user's information was deleted (e.g., "April 1, 2022, 17:00:00"), and the user's permission level (e.g., "General User").

[0032] The settings table 166 is a table that stores information regarding the settings of the multifunction printer 10. As shown in Figure 5, for example, the settings table 166 is a table that associates the name of a setting item with the configurable range, which indicates the range and type of settings that can be set for that setting item, and the setting content that has been set for that setting item. For example, the settings table 166 stores initial values ​​as setting content in advance, and the setting content is updated by the setting unit 108.

[0033] In this embodiment, the setting table 166 will include the following settings. • Settings related to user authentication function • Password policy settings • Settings related to when (where) the system checks whether a user's password complies with the password policy.

[0034] The password policy is a set of rules (policy, authentication requirements) regarding passwords, which are authentication information. The settings stored in setting table 166 are described in detail below.

[0035] (Settings related to user authentication function) The settings table 166 includes a setting (D100 in Figure 5) for whether or not to enable the user authentication function. When the user authentication function is enabled, the authentication unit 106 performs user authentication, and if the user is authenticated, that user can use the multifunction printer 10. On the other hand, when the user authentication function is disabled, the authentication unit 106 does not perform user authentication, and any user can use the multifunction printer 10.

[0036] (Password policy settings) The settings table 166 includes settings related to the password policy, such as whether or not to enable the password policy setting function (D110 in Figure 5), and settings for the content of the password policy (authentication requirements) (D120 in Figure 5).

[0037] A password policy is a type of security policy that outlines the requirements that passwords, which are authentication credentials, must meet. When the password policy setting function is enabled, policy checks are performed on passwords.

[0038] Furthermore, in this embodiment, the following settings are stored for each permission level as part of the password policy configuration. (1) Minimum password length The minimum password length indicates the minimum required length (string length, number of digits) for a password. The minimum password length can be set separately for users with "administrator" privileges (D122a in Figure 5) and users with "regular user" privileges (D122b in Figure 5). A minimum password length of "0" indicates that there are no restrictions on password length, and any length password can be set.

[0039] (2) Password creation rules Password creation rules indicate whether passwords created by users must adhere to specific rules. For example, if the password creation rule is "enabled," the password must include at least one of each of the following: a number, an uppercase letter, an lowercase letter, and a symbol. In this case, if the password creation rule is "disabled," there are no restrictions on the types of characters that must be included in the password. Password creation rules can be set separately for users with "administrator" privileges (D124a in Figure 5) and users with "regular user" privileges (D124b in Figure 5).

[0040] (3) Reuse of previous passwords is prohibited. The "Prohibit Reuse of Previous Password" setting indicates whether or not a user can set the same password again as the currently set password. This setting can be configured separately for users with "Administrator" privileges (D126a in Figure 5) and users with "Regular User" privileges (D126b in Figure 5).

[0041] (Settings regarding the timing of policy checks) The configuration table 166 includes settings related to the timing (location) of policy checks (D130 in Figure 5). In this embodiment, the timing of policy checks is set to (1) when logging in and (2) when registering / changing a password, and it is possible to configure whether or not to perform a policy check at each timing.

[0042] (1) When logging in If the login policy check is enabled, after a user sets a password, when that user logs in to the multifunction printer 10, the system checks whether the user's password complies with the password policy. If the user's password does not comply with the password policy, the user's login will be denied. Whether or not to perform the login policy check can be configured separately for users with "administrator" privileges (D132a in Figure 5) and users with "regular user" privileges (D132b in Figure 5).

[0043] The login method (authentication method) for the multifunction printer 10 shall be a login method using a login name and password (login name / password authentication), however, other login methods may also be used.

[0044] In addition to username / password authentication, the following methods are available for logging in: • Quick Authentication (Quick Login) Quick authentication is a method in which, during login, the display unit 140 displays a list of users who can log in to the multifunction printer 10 using icons, and then authenticates and grants login permission to the selected user. • IC card authentication (IC card login) IC card authentication is a method in which, when logging in, the user is read by the multifunction printer 10, and if the information read from the IC card is appropriate, the user is authenticated and allowed to log in based on that information.

[0045] It should be noted that IC card authentication is a type of possession authentication, and the user's possession used for authentication does not have to be an IC card. Furthermore, possession authentication, such as IC card authentication, may be combined with knowledge authentication. For example, IC card authentication includes the following combinations of authentication: • IC card + login name / password • IC card + login name / password + email address • IC card + user number

[0046] The user number is a number that identifies a user and is issued in advance to users who use the multifunction printer 10, and is also stored in the multifunction printer 10. Note that the login method using only the user number (user number authentication) does not display a password input screen, so it may be excluded from policy checks (no setting).

[0047] Furthermore, when various login methods are used as described above, it is possible to configure whether or not to perform a policy check for each login (each authentication) to the multifunction device 10. The setting for whether or not to perform a policy check depending on the authentication method can be configured separately for users with "administrator" privileges (D134a in Figure 5) and users with "general user" privileges (D134b in Figure 5).

[0048] Furthermore, it may be possible to configure whether or not to perform a policy check for each login method. For example, it may be possible to configure the system to perform a policy check when quick authentication is used, but not when IC card authentication is used. In this case, if a login method that performs a policy check is used, and the password of the user attempting to log in does not meet the password policy, the multifunction printer 10 will prevent (reject) that user from logging in. The setting for whether or not to perform a policy check for each login method can be configured separately for users with "administrator" privileges (D136a in Figure 5) and users with "general user" privileges (D136b in Figure 5).

[0049] (2) When registering / changing the password next time after changing the password policy settings For example, if a user is already using the multifunction printer 10, and the password policy setting function is changed from disabled to enabled, or if the content of the password policy is changed, it will be necessary to register a password or change an existing password. In such cases, if the setting is "enabled," a policy check will be performed on the changed password the next time the password is registered / changed after the password policy settings have been changed, such as when the password policy setting function is enabled. If the changed password does not meet the policy check during password registration / change, a message such as a warning will be displayed, prompting the user to change the password again, but login to the multifunction printer 10 will still be possible.

[0050] Furthermore, whether or not to perform a policy check the next time a password is registered / changed after the password policy settings have been changed can be configured separately for users with "administrator" privileges (D138a in Figure 5) and users with "regular user" privileges (D138b in Figure 5).

[0051] Furthermore, the timing of policy checks for users with "administrator" privileges may be fixed to "enabled" at all times, as shown in Figure 5, ensuring that policy checks are always performed during login and password registration / change. On the other hand, the timing of policy checks for users with "regular user" privileges may be selectable as either enabled or disabled, allowing settings to be tailored to the usage scenario of the multifunction printer 10.

[0052] In this way, the multifunction printer 10 stores the above settings in the settings table 166, allowing for precise configuration of the timing (location) of password policy checks.

[0053] Furthermore, the settings table 166 may include a setting (D140 in Figure 5) to determine whether or not to delete the registration of general users who have not logged in for a certain period of time from the multifunction printer 10. If the setting to delete the registration of general users who have not logged in for a certain period of time from the multifunction printer 10 is enabled, the user information of users who have not logged in to the multifunction printer 10 beyond the set period will be deleted by the user management unit 104. In addition, the settings table 166 may include a setting (D150 in Figure 5) to determine whether or not to prohibit the reuse of the multifunction printer 10 by deleted users. If the setting to prohibit the reuse of the multifunction printer 10 by deleted users is enabled, the user corresponding to the deleted user information will not be able to register as a user of the multifunction printer 10 again within the set period.

[0054] The communication unit 190 communicates with other devices and equipment via a network such as a LAN (Local Area Network) or WAN (Wide Area Network). The communication unit 190 is composed of communication devices and communication modules, such as a NIC (Network Interface Card) used in wired / wireless LANs. The communication unit 190 may also have an interface (network I / F) that can connect to a network. Furthermore, the communication unit 190 may be connected to a communication network such as a public telephone network, LAN, or the Internet, and may be capable of transmitting data to the outside via the communication network using communication methods such as facsimile or email.

[0055] [1.2 Processing Flow] The processes performed by the multifunction device 10 will be explained with reference to Figures 6 to 8. The processes shown in Figures 6 to 8 are executed, for example, by the control unit 100 reading a program stored in the storage unit 160. In the following explanation, it will be assumed that both the user authentication function and the password policy setting function are "enabled".

[0056] Furthermore, in the following explanation, policy checks indicate whether the password, which is authentication information included in the user information, conforms to the password policy (authentication requirements), which is the set of rules (policy) for that password.

[0057] [1.2.1 Main Processing] Referring to Figure 6, the flow of the main processing performed by the multifunction device 10 will be explained. First, the control unit 100 (authentication unit 106) displays the login screen on the display unit 140 (step S100).

[0058] Next, the control unit 100 (authentication unit 106) determines whether or not authentication information has been entered (step S102). The entered authentication information is information corresponding to the authentication method used by the authentication unit 106, and includes a combination of login name and password, information read from an IC card, or information indicating an item selected from a list of users displayed on the login screen. If no login operation is performed, the authentication unit 106 repeats the process in step S102 (step S102; No).

[0059] On the other hand, when authentication information is entered, the control unit 100 performs a login permission determination process to authenticate the user based on the authentication information and determine whether or not to allow the user to log in to the multifunction printer 10 (step S102; Yes → step S104). The login permission determination process will be described later.

[0060] Next, the control unit 100 determines whether or not login is permitted (step S106). If login is not permitted, the control unit 100 returns to step S100 (step S106; No → step S100).

[0061] On the other hand, if login is permitted, the control unit 100 logs the user authenticated in step S104 into the multifunction printer 10 and displays the login screen on the display unit 140 (step S106; Yes → step S108). The login screen is a screen used by the user who has logged into the multifunction printer 10 to operate the multifunction printer 10, and includes the home screen, job execution screen, settings screen, etc.

[0062] Next, the control unit 100 determines whether or not a password change operation has been performed (step S110). A password change operation is, for example, an operation in which a settings screen is displayed on the display unit 140 and the changed password entered on the settings screen is registered in the multifunction device 10.

[0063] If a password change operation is performed, the control unit 100 executes a password change process to change the password (step S110; Yes → step S112). The password change process will be described later. If no password change operation is performed, the control unit 100 omits the process in step S112 (step S110; No).

[0064] Next, the control unit 100 determines whether or not the user has performed a logout operation (step S114). If a logout operation has been performed, the control unit 100 logs out the user who is logged into the multifunction printer 10 (step S114; Yes → step S116). On the other hand, if a logout operation has not been performed, the control unit 100 returns to step S108 (step S114; No → step S108).

[0065] [1.2.2 Login Eligibility Determination Process] Referring to Figure 7, the login eligibility determination process will be explained. First, the control unit 100 (authentication unit 106) authenticates the user based on the authentication information entered in step S102 of Figure 6, and determines whether or not the user authentication was successful (step S130).

[0066] The control unit 100 (authentication information determination unit 110), if the user is authenticated, performs a policy check according to the user's privileges based on the settings stored in the setting table 166. First, the control unit 100 (authentication information determination unit 110) identifies the privileges of the authenticated user (step S130; Yes → step S132). For example, the authentication information determination unit 110 identifies the user's privileges by reading the privilege category stored in the user information of the user authenticated in step S130.

[0067] Next, the control unit 100 (authentication information determination unit 110) determines whether or not to perform a policy check during login (step S134). For example, the authentication information determination unit 110 refers to the setting table 166 and determines that a policy check should be performed during login if the setting to perform a policy check during login is "enabled" for users with the privileges identified in step S132. On the other hand, if the setting is "disabled", the authentication information determination unit 110 determines that a policy check should not be performed during login.

[0068] The control unit 100 (authentication information determination unit 110), when performing a policy check during login, refers to the setting table 166 and determines whether or not to perform a policy check for users with the privileges identified in S132, according to the authentication method (step S134; Yes → step S136).

[0069] When the control unit 100 (authentication information determination unit 110) performs a policy check according to the authentication means, it refers to the setting table 166 and determines whether the authentication method used by the user is an authentication method for which a policy check is performed (step S136; Yes → step S138).

[0070] The control unit 100 (authentication information determination unit 110) determines whether the password of the user authenticated in step S130 satisfies the password policy if the authentication method used by the user is an authentication means that performs a policy check (step S138; Yes → step S140). For example, the authentication information determination unit 110 refers to the setting table 166, reads the password policy settings for the user's privileges authenticated in step S130, and determines whether the user's password satisfies the password policy. In this case, it is determined whether the length of the user's password is equal to or greater than the minimum password length and / or whether the user's password satisfies the password creation rules. The authentication information determination unit 110 determines that the password policy is satisfied if the user's password satisfies all of the contents set as the password policy. On the other hand, the authentication information determination unit 110 determines that the password policy is not satisfied if the user's password does not satisfy even one of the contents set as the password policy.

[0071] The control unit 100 (authentication information determination unit 110) allows the user to log in if the password of the user authenticated in step S130 satisfies the password policy (step S140; Yes → step S142). On the other hand, the control unit 100 (authentication information determination unit 110) rejects the login and prevents the user from logging in if the password of the user authenticated in step S130 does not satisfy the password policy (step S140; No → step S144).

[0072] For example, if a user authenticated in step S130 enters a password with a length of 3 digits during login, the password policy setting function is enabled, and the minimum password length is 5 digits, then the user's password does not meet the password policy. In this case, the user cannot log in to the multifunction printer 10.

[0073] If the password does not meet the password policy, the user will not be able to log in to the multifunction printer 10, and will need to change their password. For example, the control unit 100 (authentication information determination unit 110) may display a message on the display unit 140 prompting the user to request a password change from the administrator of the multifunction printer 10 if the password does not meet the password policy. The control unit 100 (authentication information determination unit 110) may also notify the administrator of the multifunction printer 10 that there is a user who cannot log in to the multifunction printer 10 because the password does not meet the password policy. In this way, the authentication information determination unit 110 can prompt the user to take the necessary action to log in to the multifunction printer 10, even if the user who could not log in to the multifunction printer 10 due to not meeting the password policy does not have a means to change their password.

[0074] Furthermore, if the control unit 100 (authentication information determination unit 110) determines in step S136 that it does not need to perform a policy check according to the authentication means, it skips step S138 and executes the process in step S140 (step S136; No → step S140). In other words, if a policy check according to the authentication means is not performed, the authentication information determination unit 110 performs a policy check on the password of the user authenticated in step S130, regardless of the authentication means used by the user.

[0075] Furthermore, if the control unit 100 (authentication information determination unit 110) determines in step S134 that a policy check is not required during login (step S134; No), it omits the policy check and allows login. Similarly, if the control unit 100 (authentication information determination unit 110) determines in step S138 that the authentication method used by the user is not an authentication means that requires a policy check (step S138; No), it omits the policy check and allows login. In this case, the policy check for the password of the user authenticated in step S130 is omitted, and the user is allowed to log in as is.

[0076] Furthermore, if the control unit 100 (authentication unit 106) fails to authenticate the user in step S130, it rejects the user's login (step S130; No → step S144).

[0077] By executing the process described above, the control unit 100 (authentication information determination unit 110) performs a policy check in the following cases. • When policy checks are performed during login, but not when policy checks are performed according to the authentication method. • When a policy check is performed during login, and the policy check is performed according to the authentication method, and the authentication method that is subject to the policy check is used.

[0078] On the other hand, the control unit 100 (authentication information determination unit 110) does not perform a policy check in the following cases: • When policy checks are not performed during login. • When a policy check is performed during login, and the policy check is performed according to the authentication method, but an authentication method that is not subject to policy check is used.

[0079] In this way, the control unit 100 (authentication information determination unit 110) can perform policy checks when a user logs in, depending on their permissions and login method. It can also prevent users whose passwords do not meet the password policy from logging in.

[0080] [1.2.3 Password Change Process] Referring to Figure 8, the password change process will be explained. First, the control unit 100 (user management unit 104) displays a screen for changing and registering a password on the display unit 140 and obtains the changed password entered via that screen (step S160).

[0081] Next, the control unit 100 (authentication information determination unit 110) determines whether or not to perform a policy check (step S162). For example, if the password policy settings have been changed, the authentication information determination unit 110 refers to the setting table 166 and reads whether the setting to perform a policy check when registering / changing the password for the next time after the password policy settings have been changed is valid for the privileges of the user (logged-in user) authenticated in step S130 of Figure 7. If the read setting is "valid", the authentication information determination unit 110 determines that a policy check will be performed when the password is changed, and if it is "invalid", it determines that a policy check will not be performed when the password is changed. On the other hand, if the password policy settings have not been changed before the password is registered / changed, or if the setting to perform a policy check when registering / changing the password for the next time after the password policy settings have been changed is invalid, the authentication information determination unit 110 determines that a policy check will not be performed when the password is changed.

[0082] When performing a policy check, the control unit 100 (authentication information determination unit 110) determines whether the changed password obtained in step S160 satisfies the password policy corresponding to the login user's privileges (step S162; Yes → step S164). For example, the authentication information determination unit 110 reads the password policy settings corresponding to the login user's privileges from the setting table 166 and determines whether the changed password satisfies the contents of the read settings (requirements that the password must satisfy).

[0083] The control unit 100 (user management unit 104) determines whether the password can be changed if the changed password satisfies the password policy (step S164; Yes → step S166). The following are examples of cases in which the password can be changed. • When the reuse of the previous password is not prohibited. • When reusing the previous password is prohibited, and the previous password and the new password are different.

[0084] The control unit 100 (user management unit 104) changes the password if it can be changed (step S166; Yes → step S168). For example, the user management unit 104 stores the password obtained in step S160 as the password for the logged-in user's user information.

[0085] On the other hand, if the password cannot be changed, the control unit 100 returns to step S160 (step S166; No → step S160). At this time, the control unit 100 may display a message on the display unit 140 indicating that the password cannot be reused.

[0086] Furthermore, if the control unit 100 (authentication information determination unit 110) determines in step S164 that the password does not meet the password policy, it displays a message (warning message) indicating that the password does not meet the password policy on the display unit 140 (step S164; No → step S170). The message may also include a sentence prompting the user to change the password again (re-enter the password). After processing in step S170, the control unit 100 returns to step S160.

[0087] Furthermore, if the control unit 100 (user management unit 104) determines in step S162 that a policy check is not necessary, it skips the processing in step S164 and executes the processing in step S166 (step S162; No → step S166). In this case, if the login user's password can be changed, the password obtained in step S160 is changed without a policy check being performed on the changed password.

[0088] In this way, the control unit 100 (authentication information determination unit 110) can perform a policy check according to the login user's privileges when registering or changing a password. Furthermore, the control unit 100 can prevent the registration of passwords that do not meet the password policy by having the authentication information determination unit 110 perform the policy check.

[0089] In this way, the control unit 100 executes the processes shown in Figures 6 to 8, and depending on the user's privileges when using the multifunction printer 10, it can perform a policy check on the user's password at the timing set for policy checks, such as when logging in or when registering / changing a password. Note that, even if not described above, the order of the steps may be changed or some steps omitted, as long as it is consistent with the original explanation.

[0090] [1.3 Example of Operation] An example of operation of this embodiment will be described with reference to Figures 9 and 10. Figures 9 and 10 are diagrams showing example settings screens, and it is assumed that the screen shown in Figure 9 and the screen shown in Figure 10 are connected.

[0091] The settings screen W100 shown in Figure 9 includes an area E100 for configuring whether or not to enable the password policy setting function. Additionally, the settings screen W100 includes an area E102 for configuring the password policy for users with "administrator" privileges, and an area E104 for configuring the password policy for users with "regular user" privileges.

[0092] Furthermore, the settings screen W110 shown in Figure 10 includes area E110 for setting the timing of policy checks for users with "general user" privileges. Users such as administrators of the multifunction device 10 can configure password policy settings and policy check timing settings via settings screens W100 and W110.

[0093] Next, we will explain the usage scenarios and setting examples for the multifunction printer 10 of this embodiment. Note that the timing of policy checks for users with "general user" privileges is determined by the settings from setting 1 to setting 3 shown below. Setting 1: Perform policy checks upon login. Setting 2: Perform a policy check the next time a password is registered / changed after the password policy settings have been changed. Setting 3: Perform policy checks when various login methods are used. The login methods will be quick login and IC card authentication.

[0094] Furthermore, the following examples illustrate usage scenarios. Example 1: When multifunction printer 10 is used in government agencies and other organizations that prioritize security. Example 2: When one multifunction printer 10 is used in an office sharing situation where multiple companies share a single room.

[0095] In Example 1, enabling all of the above settings 1 through 3 will enhance the security of the multifunction printer 10.

[0096] In Example 2, strengthening security would compromise usability, so it might be advisable to lower the security level to some extent. For example, enable only setting 2. That is, the policy check would only be performed the next time a password is registered / changed after the password policy settings have been changed.

[0097] In the explanation above, the policy check was described as checking whether the password complies with the password policy, but checks may also be performed on other items subject to security checks (target items). For example, the target items for other security checks may be email addresses. In this case, the policy check for email addresses may be to check whether the email address is registered, or whether the number of registered email addresses is greater than or equal to a predetermined number. Note that email addresses may also be authentication information. In addition, authentication information other than email may also be items subject to security checks.

[0098] Furthermore, the items subject to the security check may also be the user's registration information. In this case, the policy check on the user's registration information may include checking whether the user's department name and contact information are registered, or whether the user's icon (such as a profile picture) is registered. Note that there may be multiple items subject to the policy check.

[0099] Furthermore, although the above explanation assumed that the user's permission type is either "administrator" or "regular user," the permission types can be designed and configured as appropriate, and it is sufficient that security policy settings can be configured according to the permission type.

[0100] Thus, the multifunction printer of this embodiment has a function to set rules (policies) for passwords in order to ensure the security of the machine, and the location where the password conforms to the policy can be set on a settings screen where the policy can be enabled or disabled. In other words, the multifunction printer of this embodiment is provided with setting means for making settings related to policy checks, such as on a settings screen, and performs policy checks according to the contents set by the setting means.

[0101] In particular, the multifunction printer of this embodiment allows for user-specific settings based on user privileges, enabling fine-tuning of policy checks for each machine usage scenario, and allowing for adjustment of security levels for each target item and each user. As a result, the multifunction printer of this embodiment achieves policy checks tailored to the user and usage scenario, ensuring security while maintaining the convenience of the multifunction printer for each usage scenario. Furthermore, users can adjust the degree of detailed password policy checks depending on the usage scenario of the multifunction printer (installation location, etc.) by adjusting the timing of policy checks.

[0102] Furthermore, the multifunction printer of this embodiment allows for setting requirements (such as minimum password length and required character types) for passwords (authentication information), which are the target items for security checks, on a per-user basis, according to the user's authority. Additionally, the multifunction printer of this embodiment allows for detailed setting of the location (timing) of policy checks on a per-user basis, according to the user's authority. This enables the multifunction printer of this embodiment to adjust the security level applied to each security check target item on a per-user basis, rather than setting a single security level for all users. Moreover, there may be multiple security check target items, and it is possible to specify the security level to apply to each security check target item.

[0103] [2. Second Embodiment] Next, the second embodiment will be described. The second embodiment is an embodiment that, in addition to the functions described in the first embodiment, allows users to choose whether or not to perform policy checks on a per-user basis. In this embodiment, Figure 3 of the first embodiment is replaced with Figure 11, Figure 5 of the first embodiment with Figure 12, Figure 7 of the first embodiment with Figure 13, and Figure 8 of the first embodiment with Figure 14. The same reference numerals are used for the same processes, and their descriptions are omitted.

[0104] [2.1 Functional Configuration] Figure 11 shows an example of user information in this embodiment. The user information in this embodiment differs from the user information in the first embodiment shown in Figure 3 in that it also includes a group name (for example, "Accounting Department") indicating the group to which the user belongs. Note that a user does not have to belong to a group, or may belong to multiple groups. Furthermore, the information indicating the group to which the user belongs may be any information other than the group name, such as a group ID, as long as it is information that can identify the group.

[0105] Figure 12 shows an example of the settings table 166 of this embodiment. Compared to the settings table 166 of the first embodiment shown in Figure 5, the settings table 166 of this embodiment also stores a setting regarding the password policy, which specifies whether or not to perform a policy check for each user or group registered in the multifunction device 10 (D200 in Figure 12).

[0106] Furthermore, the configuration table 166 stores the users (D202 in Figure 12) and groups (D204 in Figure 12) that are subject to policy checks. This ensures that when the setting for policy checks per user or group is enabled, policy checks are performed only on the users or groups that are targeted. In this embodiment, it is possible to specify which users and groups are subject to policy checks from among users with "General User" privileges. That is, in this embodiment, all users with "Administrator" privileges are subject to policy checks.

[0107] [2.2 Processing Flow] [2.2.1 Login Eligibility Determination Process] The login eligibility determination process of this embodiment will be explained with reference to Figure 13. In the following explanation, it will be assumed that among users with "General User" privileges, the users and groups subject to policy checks are pre-configured, and that all users with "Administrator" privileges will undergo policy checks.

[0108] In this embodiment, after performing the processing in step S132, the control unit 100 (authentication information determination unit 110) refers to the setting table 166 and determines whether or not to perform a policy check for each user or group (step S200).

[0109] Furthermore, when the control unit 100 (authentication information determination unit 110) performs a policy check for each user or group, it determines whether the user authenticated in step S130 is a user subject to the policy check (step S200; Yes → step S202). For example, if the information shown in Figure 12 is stored as the setting table 166, the authentication information determination unit 110 determines that the user is a user subject to the policy check in any of the following cases. If the privilege identified in step S132 is "administrator". - If the privilege identified in step S132 is "General User", and the user authenticated in step S130 is the user subject to policy checking. If the privilege identified in step S132 is "General User", and the user authenticated in step S130 belongs to the group that is subject to policy checking.

[0110] The control unit 100 (authentication information determination unit 110) executes the process in step S134 if the user authenticated in step S130 is a user subject to policy checking (step S202; Yes → step S134). On the other hand, if the control unit 100 (authentication information determination unit 110) is a user other than a user subject to policy checking, it skips the policy check and allows login (step S202; No → step S142).

[0111] Furthermore, if the control unit 100 (authentication information determination unit 110) determines in step S200 that no policy check is required for each user or group, it skips the processing in step S202 and executes the processing in step S134 (step S200; No → step S134).

[0112] [2.2.2 Password Change Process] Referring to Figure 14, the password change process of this embodiment will be described. In this embodiment, after the processing in step S160, the control unit 100 (authentication information determination unit 110) determines whether or not to perform a policy check for each user or group (step S260).

[0113] The control unit 100 (authentication information determination unit 110) determines whether the logged-in user is a user subject to policy checks when performing policy checks for each user or group (step S260; Yes → step S262). Note that the processing in step S260 and step S262 is the same as the processing in step S200 and step S202 in Figure 13.

[0114] The control unit 100 (authentication information determination unit 110) determines whether the setting to perform a policy check the next time a password is registered / changed after a password policy setting change is valid if the user logged into the multifunction printer 10 is a user subject to policy checks (step S262; Yes → step S162). In this case, if the setting is valid, the control unit 100 (authentication information determination unit 110) performs a policy check (step S162; Yes → step S164), and if the setting is invalid, it omits the policy check (step S162; No → step S166). On the other hand, if the control unit 100 (user management unit 104) determines in step S262 that the user logged into the multifunction printer 10 is not a user subject to policy checks, it determines whether the password can be changed (step S262; No → step S166). In this case, the policy check is omitted.

[0115] Furthermore, if the control unit 100 (authentication information determination unit 110) determines in step S260 that a policy check is not required for each user or group, it omits the processing in step S262 and executes the processing in step S162 (step S260; No → step S162).

[0116] In the above explanation, it was determined whether or not to perform a policy check when registering / changing a password if the logged-in user is a user subject to policy checks. However, this determination may be omitted, and a policy check may be performed unconditionally for the logged-in user. For example, if the control unit 100 performs policy checks for each user group, and the logged-in user is a user subject to policy checks, the execution of step S162 as shown in Figure 14 is omitted. As a result, if the control unit 100 (authentication information determination unit 110) determines in step S262 that the user logged into the multifunction device 10 is a user subject to policy checks, it performs a policy check (step S262; Yes → step S164). If the control unit 100 (authentication information determination unit 110) determines in step S260 that a policy check should not be performed for each user group, it should execute the process in step S162 as shown in Figure 14 (step S260; No → step S162).

[0117] [2.3 Example of Operation] An example of operation of this embodiment will be described with reference to Figure 15. Figure 15 is a diagram showing an example of the settings screen W200. The settings screen W200 of this embodiment includes an area E200 in which settings are made on whether or not to perform policy checks for each user or group. Users can enable the function to perform policy checks for each user or group by checking the box for "[Perform password policy checks only for specific users]".

[0118] Furthermore, the settings screen W200 of this embodiment includes an area E202 for selecting users subject to policy checks and an area E204 for selecting groups subject to policy checks. Area E202 displays a list of users registered in the multifunction device 10, from which users subject to policy checks are selected. Area E204 displays a group list of the multifunction device 10, from which groups subject to policy checks are selected. Note that there may be multiple users or groups subject to policy checks.

[0119] The user selects whether or not to perform policy checks for each user or group, and the users and groups to be subject to policy checks, from areas E200, E202, and E204, and then applies the settings to the multifunction device 10 by pressing the registration button B200. In this way, the user can set whether or not to perform policy checks for each user (or group) and select the users (or groups) to which policy checks will be performed. As a result, as shown in Figure 15, it is possible to enable policy checks for user A and not perform policy checks for user B (no check).

[0120] Next, we will explain the usage scenarios and setting examples of the multifunction printer 10 of this embodiment. In this embodiment, in addition to the settings 1 to 3 shown in the first embodiment, settings 4 and 5 below determine whether or not to perform policy checks on a per-user or per-group basis. Setting 4: Perform policy checks on specified users. Setting 5: Perform policy checks on the specified group.

[0121] In Example 2 of the first embodiment, there is a disadvantage in that the security of the multifunction printer 10 is reduced to some extent. Therefore, in order to improve this disadvantage, the settings are configured to perform policy checks on specific users (employees or temporary staff of partner companies) or specific groups. In other words, by enabling the above settings 4 / 5 (specifying the users / groups on which policy checks should be performed), it becomes possible to maintain a certain level of security and ease of operation even in situations such as office sharing.

[0122] In the above explanation, it was stated that the timing of policy checks can be set for each user or group, but the content of the policy checks can also be set for each user or group. In this case, the multifunction device 10 will pre-associate the content of the policy checks with the users or groups. The control unit 100 will then perform a policy check on the user authenticated in step S130 of Figure 13, based on the content of the policy checks corresponding to that user or the group to which that user belongs.

[0123] For example, for users who need stronger security, such as those in the Human Resources or Accounting Department, or employees of partner companies, the policy checks can be set more strictly (for example, a minimum password length of 8 characters). On the other hand, for users in departments other than Human Resources or Accounting, or users who are not employees of partner companies, the policy checks can be set more loosely (for example, a minimum password length of 5 characters). By making such settings, the multifunction printer 10 can switch the policy check settings for each user and the group to which the user belongs.

[0124] Furthermore, the content of the policy check may be configurable depending on the authentication method. In this case, for example, if the user is authenticated using an IC card and a login name / password, the policy check can be set to be strict, while if the user is authenticated using an IC card, a login name / password, and an email address, the policy check can be set to be lenient.

[0125] Thus, the multifunction printer of this embodiment allows for adjustment of the level of granularity with which password policies are checked for each user, and enables the setting of security levels for each user or group. As a result, the multifunction printer of this embodiment can maintain a certain level of security while ensuring user convenience with greater flexibility, and can provide users with a highly convenient service.

[0126] [3. Third Embodiment] Next, the third embodiment will be described. The third embodiment, like the second embodiment, is an embodiment in which the password policy is checked on a per-user basis. In particular, unlike the second embodiment, the third embodiment checks the password policy according to the function used by the user. The third embodiment will be described focusing on the differences from the second embodiment. In this embodiment, Figure 3 of the first embodiment is replaced with Figure 16, Figure 5 of the first embodiment with Figure 17, Figure 7 of the first embodiment with Figure 18, and Figure 8 of the first embodiment with Figure 19.

[0127] [3.1 Functional Configuration] Figure 16 shows an example of user information in this embodiment. The user information in this embodiment differs from that of the first embodiment shown in Figure 3 in that it also includes information indicating the functions used by the user. In the example in Figure 16, it is assumed that the copy function and the OCR (Optical Character Recognition) function are available on the multifunction printer 10. In addition, information is stored for each user indicating whether they are a user who uses only the copy function or a user who uses both the copy function and the OCR function. In the example in Figure 16, user A is a user who uses both the copy function and the OCR function, and user B is a user who uses only the copy function.

[0128] Figure 17 shows an example of the configuration table 166 of this embodiment. The configuration table 166 of this embodiment differs from the configuration table 166 of the first embodiment shown in Figure 5 in that the timing of policy checks can be set according to the user's permissions and the functions used by the user.

[0129] For example, setting table 166 includes settings for users with "administrator" privileges (D300 in Figure 17) and settings for users with "general user" privileges. However, for "general user" privileges, different settings are possible depending on the function being used. In the example in Figure 17, settings are included for users with "general user" privileges who only use the copy function (D310 in Figure 17) and for users who use both the copy function and the OCR function (D320 in Figure 17).

[0130] Furthermore, the configuration table 166 includes settings for whether or not to perform a policy check during login (D302, D312, D322 in Figure 17) and whether or not to perform a policy check when registering / changing a password after a password policy change (D304, D314, D324 in Figure 17), depending on the combination of permissions and functions used.

[0131] [3.2 Processing Flow] [3.2.1 Login Eligibility Determination Process] The login eligibility determination process of this embodiment will be described with reference to Figure 18. In this embodiment, the control unit 100 (authentication information determination unit 110) performs the processing in step S132 and then identifies the function used by the authenticated user in step S130 (step S300). For example, the control unit 100 identifies the function used by the authenticated user in step S130 by reading the information on the function used included in the user information of the authenticated user.

[0132] Next, the control unit 100 (authentication information determination unit 110) determines whether the user authenticated in step S130 will perform a policy check when logging in, based on the permissions identified in step S132 and the functions to be used identified in step S300 (step S302).

[0133] For example, the authentication information determination unit 110 reads the settings from the settings table 166 that correspond to the authority identified in step S132 and the function to be used identified in step S300. Specifically, if the settings table 166 stores the information shown in Figure 17, the authentication information determination unit 110 reads the setting (D302 in Figure 17) that determines whether or not to perform a policy check upon login for a user with the authority of "administrator," if the authority identified in step S132 is "administrator." Similarly, if the authentication information determination unit 110 reads D312 in Figure 17 if the authority identified in step S132 is "general user" and the function used by the user identified in step S300 is only the copy function. Furthermore, if the authentication information determination unit 110 reads D322 in Figure 17 if the authority identified in step S132 is "general user" and the functions used by the user identified in step S300 are both the copy function and the OCR function. The authentication information determination unit 110 then determines that if the setting to perform a policy check during login is "enabled" among the read settings, a policy check will be performed during login; if the setting is "disabled", it determines that a policy check will not be performed during login.

[0134] The control unit 100 (authentication information determination unit 110) performs a policy check when logging in by executing the processes from steps S136 to S144 in Figure 18 based on the settings read in step S302 (step S302; Yes). On the other hand, if the control unit 100 (authentication information determination unit 110) does not perform a policy check when logging in, it omits the policy check and allows the login (step S302; No → step S142). In this way, the authentication information determination unit 110 can omit the policy check if the user authenticated in step S130 does not use the function that is subject to the policy check.

[0135] [3.2.2 Password Change Process] The password change process of this embodiment will be described with reference to Figure 19. In this embodiment, after the processing in step S160, the control unit 100 (authentication information determination unit 110) identifies the authority of the logged-in user and the functions used by that user (step S360). The processing in step S360 is the same as the processing in steps S132 and S300 in Figure 18.

[0136] Furthermore, the control unit 100 (authentication information determination unit 110) reads the corresponding settings from the setting table 166 based on the authority and functions used identified in step S360, and determines whether or not to perform a policy check (step S362). The process in step S362 is the same as in Figure 18, but differs in that it reads the settings at the time of password registration / change after the setting change.

[0137] The control unit 100 (authentication information determination unit 110) performs a policy check based on the settings read in step S362 if a policy check is to be performed (step S362; Yes → step S164). On the other hand, if the control unit 100 (user management unit 104) determines that a policy check is not to be performed, it determines whether or not the password can be changed (step S362; No → step S166). In this case, the policy check is omitted.

[0138] In this way, the control unit 100 can perform policy checks on a user-by-user basis according to the functions used by the user of the multifunction printer 10 by executing the processes shown in Figures 18 and 19.

[0139] [3.3 Example of Operation] An example of operation of this embodiment will be described with reference to Figure 20. Figure 20 is a diagram showing an example of the settings screen W300. The settings screen W300 of this embodiment includes an area E300 for setting the timing of policy checks according to the functions used by the user.

[0140] Area E300 includes a tabbed user interface (UI). The tab labels indicate the types of functions the user will use, and by switching tabs, the timing of policy checks for users using the functions listed on the tab labels can be configured. Users can switch tabs to configure the timing of policy checks for each type of function they use.

[0141] In the explanation above, it was stated that the timing of policy checks can be set according to the functions used by the user, but the content of the policy checks can also be set according to the functions used by the user. For example, the content of the policy checks could be made stricter for users who use many functions (e.g., users who use the copy function and OCR function), and looser for users who use few functions (e.g., users who use only the copy function). In addition, the multifunction printer 10 may suggest the content of the policy checks to the user (e.g., the administrator of the multifunction printer 10) according to the type and number of functions used.

[0142] Thus, with the multifunction printer of this embodiment, it becomes possible to set the timing of policy checks depending on the functions being used. This allows the multifunction printer of this embodiment to operate in a way that loosens policy checks for users who use fewer functions and tightens them for users who use many functions. This makes it possible to maintain both the convenience of the multifunction printer and a minimum level of security with greater flexibility.

[0143] [4. Variant] This disclosure is not limited to the embodiments described above, and various modifications are possible. That is, embodiments obtained by combining technical means that are appropriately modified without departing from the gist of this disclosure are also included in the technical scope of this disclosure.

[0144] Furthermore, although the embodiments described above are explained separately for explanatory purposes, they can, of course, be combined and implemented to the extent that is technically possible. For example, the second and third embodiments may be combined. In this case, it becomes possible to provide a multifunction device in which the users or groups to be subject to policy checks can be selected, and the timing of policy checks can be changed according to the functions used by the users performing the policy checks.

[0145] Furthermore, although the above-described embodiment was explained as performing policy checks according to user-specific settings in a multifunction printer, which is an image forming apparatus, policy checks according to user-specific settings may also be performed in information processing devices used by multiple users, such as image reading devices like scanners or server devices. In addition, policy checks according to user-specific settings may be performed in services used by multiple users. In this way, information processing devices and services perform policy checks for each user according to settings corresponding to the user's permissions and group.

[0146] Furthermore, in the embodiments, the programs that run in each device are programs that control the CPU and the like (programs that make the computer function) in order to realize the functions of the embodiments described above. The information handled by these devices is temporarily stored in a temporary storage device (for example, RAM) during processing, and then stored in storage devices such as various ROMs (Read Only Memory) and HDDs, and read, modified, and written by the CPU as needed.

[0147] Here, the recording medium for storing the program may be any of the following: semiconductor media (e.g., ROM, non-volatile memory card, etc.), optical recording media / magneto-optical recording media (e.g., DVD (Digital Versatile Disc), MO (Magneto Optical Disc), MD (Mini Disc), CD (Compact Disc), BD (Blu-ray® Disc), etc.), magnetic recording media (e.g., magnetic tape, flexible disk, etc.). Furthermore, in addition to realizing the functions of the embodiments described above by executing the loaded program, the functions of this disclosure may also be realized by processing in cooperation with the operating system or other application programs based on the instructions of the program.

[0148] Furthermore, when distributing the program to the market, it can be stored on a portable storage medium and distributed, or transferred to a server computer connected via a network such as the Internet. In this case, the storage device of the server computer is, of course, also included in this disclosure. [Explanation of symbols]

[0149] 10 Multifunction device 100 Control Unit 102 Image Processing Unit 104 User Management Department 106 Authentication Department 108 Settings Section 110 Authentication Information Determination Unit 120 Image Input Section 130 Image forming unit 140 Display section 150 Operation section 160 Storage section 162 User information storage area 164 Deleted User Information Storage Area 166 Configuration Table 190 Communications Department

Claims

1. A storage unit that stores user authentication information, A setting unit for setting authentication requirements for the aforementioned authentication information on a per-user basis, An authentication unit that authenticates the user based on the aforementioned authentication information, A determination unit that determines whether the authentication information of a user authenticated by the authentication unit satisfies the authentication requirements corresponding to that user, Equipped with, The setting unit can be configured to set the user or group from among the users to be subject to the determination, The image forming apparatus is characterized in that the determination unit omits the determination if the user authenticated by the authentication unit is a user other than the user to be determined or does not belong to the group to be determined.

2. The setting unit is, The aforementioned authentication requirements are set separately for administrators and general users based on their permissions. The image forming apparatus according to claim 1, characterized in that, among the users whose authority is that of a general user, a user or group is set to be the target of the determination.

3. The setting unit can further set the timing for performing the determination, The image forming apparatus according to claim 2, characterized in that the determination unit performs the determination when the timing for performing the determination is set.

4. The aforementioned setting unit allows you to configure whether or not to perform the aforementioned determination when logging in. The image forming apparatus according to claim 3, characterized in that when the determination unit performs the determination during login, if the authentication information of a user authenticated by the authentication unit does not satisfy the authentication requirements corresponding to that user at the time of login, the determination unit prevents the user from logging in.

5. The setting unit can further configure whether or not to perform the determination according to the authentication method used. The image forming apparatus according to claim 4, characterized in that when the determination unit performs the determination during login, if an authentication method that does not perform the determination is used by a user authenticated by the authentication unit, the determination unit omits the determination for that user.

6. The setting unit can further configure whether or not to perform the determination when the authentication information is changed after the authentication requirements have been changed. The image forming apparatus according to claim 3, characterized in that when the determination unit performs the determination when the authentication information is changed, if the changed authentication information of the user changing the authentication information does not meet the authentication requirements corresponding to that user, it displays a message prompting the user to enter the changed authentication information again.

7. The setting unit can be configured to determine whether or not to perform the determination depending on the function to be used. The image forming apparatus according to any one of claims 1 to 6, characterized in that the determination unit omits the determination if the user authenticated by the authentication unit does not use the function for which the determination is to be made.

8. It stores the user's authentication information, For each user, set the authentication requirements for the aforementioned authentication information. Based on the aforementioned authentication information, the user is authenticated. A determination method in a processing device that determines whether the authentication information of an authenticated user satisfies the authentication requirements corresponding to that user, It is possible to set which users or groups from among the aforementioned users are to be subject to the determination. If the authenticated user is a user other than the user subject to the determination, or does not belong to the group subject to the determination, the determination is omitted. A determination method in a processing apparatus characterized by the above.

Images