Guest account generation system, information processing device, and guest account generation program

Abstract

This invention provides a guest account generation system, an information processing device, and a guest account generation program that can generate guest accounts. [Solution] When the device management system receives a signup email as an email for signing up for a guest account as a temporary user account, if the value of at least one specific item that should be included in the signup email among the items that need to be entered for signing up for the guest account is not included in the signup email in a manner that satisfies a specific condition (YES in S268), the device management system replies with an email containing the URL of the signup page as a web page for signing up for the guest account (S270).

Description

Technical Field

[0001] The present invention relates to a guest account generation system, an information processing apparatus, and a guest account generation program that generate a guest account as a temporary user account.

Background Art

[0002] Conventionally, a system that can use resources using a guest account has been known (see, for example, Patent Document 1).

Prior Art Document

Patent Document

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the conventional system, there is a problem that the guest account is fixed and a guest account cannot be generated.

[0005] Therefore, an object of the present invention is to provide a guest account generation system, an information processing apparatus, and a guest account generation program that can generate a guest account.

Means for Solving the Problems

[0006] The guest account generation system of the present invention comprises a guest account generation unit that generates a guest account as a temporary user account, and when the guest account generation unit receives a signup email as an email for signing up for the guest account, if the value of at least one specific item that should be included in the signup email among the items that need to be entered for signing up for the guest account is not included in the signup email in a manner that satisfies certain conditions, the guest account generation unit replies with an email containing the URL of a signup page as a web page for signing up for the guest account.

[0007] With this configuration, the guest account generation system of the present invention, upon receiving a sign-up email, will send back an email containing the URL of the sign-up page if the value of at least one specific item that should be included in the sign-up email among the items that need to be entered for guest account sign-up is not included in the sign-up email under certain conditions, thereby allowing the user to access the URL of the sign-up page and generate a guest account via the sign-up page.

[0008] In the guest account generation system of the present invention, when the guest account generation unit replies with an email containing the URL of the signup page, it may also notify the guest account generation unit of the specific items that are not included in the signup email, provided that the values ​​satisfy the specific conditions.

[0009] With this configuration, when the guest account generation system of the present invention replies to an email containing the URL of the signup page, it notifies the user of specific items that are not included in the signup email, provided that their values ​​meet certain conditions. This allows the user to become aware of specific items that are not included in the signup email, provided that their values ​​meet certain conditions.

[0010] In the guest account generation system of the present invention, the sign-up page includes a field for entering the value of a specific item, and when the guest account generation unit receives the sign-up email, if the value of at least one of the specific items is not included in the sign-up email in a state that satisfies the specific conditions, the unit may enter the value of the specific item included in the sign-up email in a state that satisfies the specific conditions into the field of the specific item included in the sign-up email in a state that satisfies the specific conditions, generate the sign-up page with the field of the specific item not included in the sign-up email in a state that satisfies the specific conditions left blank, and send back an email containing the URL of the generated sign-up page.

[0011] With this configuration, when the guest account generation system of the present invention receives a sign-up email, if the value of at least one specific item is not included in the sign-up email in a state that satisfies the specific conditions, it inputs the value of the specific item included in the sign-up email in a state that satisfies the specific conditions into the field of the specific item included in the sign-up email in a state that satisfies the specific conditions, generates a sign-up page with the field of the specific item not included in the sign-up email in a state that satisfies the specific conditions left blank, and sends back an email containing the URL of the generated sign-up page, thereby facilitating the user's value input work on the sign-up page.

[0012] In the guest account generation system of the present invention, when the guest account generation unit receives the signup email, if the values ​​of all the specified items in the signup email satisfy the specified conditions, it may reply with an email containing a URL for a password registration page, which is a web page for registering the password for the guest account.

[0013] With this configuration, the guest account generation system of the present invention, upon receiving a sign-up email, will return an email containing a URL to the password registration page if the values ​​of all specific items in the sign-up email meet certain conditions, thereby facilitating the user's guest account sign-up process.

[0014] In the guest account generation system of the present invention, when the guest account generation unit receives the sign-up email, if the value of at least one of the specific items is not included in the sign-up email in a state that satisfies the specific conditions, the unit may automatically set the value of the specific item that is not included in the sign-up email in a state that satisfies the specific conditions.

[0015] With this configuration, the guest account generation system of the present invention, upon receiving a sign-up email, automatically sets the value of at least one specific item that is not included in the sign-up email in a state that satisfies certain conditions, thereby simplifying the process of signing up for a guest account by the user.

[0016] In the guest account generation system of the present invention, when the guest account generation unit receives the signup email, it may identify the group to which the guest account belongs based on the domain of the signup email.

[0017] With this configuration, the guest account generation system of the present invention, upon receiving a sign-up email, identifies the group to which the guest account belongs based on the domain of the sign-up email, thereby facilitating the user's guest account sign-up process.

[0018] The information processing device of the present invention comprises a guest account generation unit that generates a guest account as a temporary user account, and when the guest account generation unit receives a signup email as an email for signing up for the guest account, if the value of at least one specific item that should be included in the signup email among the items that need to be entered for signing up for the guest account is not included in the signup email in a manner that satisfies certain conditions, the guest account generation unit replies with an email containing the URL of a signup page as a web page for signing up for the guest account.

[0019] With this configuration, when the information processing device of the present invention receives a sign-up email, if the value of at least one specific item that should be included in the sign-up email among the items that need to be entered for guest account sign-up is not included in the sign-up email under certain conditions, it will send back an email containing the URL of the sign-up page, allowing the user to access the URL of the sign-up page and generate a guest account via the sign-up page.

[0020] The guest account generation program of the present invention provides a computer with a guest account generation unit that generates guest accounts as temporary user accounts, and when the guest account generation unit receives a signup email as an email for signing up for the guest account, if the value of at least one specific item that should be included in the signup email among the items that need to be entered for signing up for the guest account is not included in the signup email in a manner that satisfies certain conditions, the program returns an email containing the URL of a signup page as a web page for signing up for the guest account.

[0021] With this configuration, when a computer that executes the guest account generation program of the present invention receives a signup email, among the items for which values need to be input for guest account signup, if the value of at least one specific item that should be included in the signup email does not meet a specific condition and is not included in the signup email, an email containing the URL of the signup page is replied, so that the user can be made to access the URL of the signup page and generate a guest account via the signup page.

Advantages of the Invention

[0022] The guest account generation system, information processing apparatus, and guest account generation program of the present invention can generate a guest account.

Brief Description of the Drawings

[0023] [Figure 1] It is a block diagram of an example of a system according to an embodiment of the present invention. [Figure 2] It is a block diagram of an example of the image forming apparatus shown in FIG. 1 when configured by an MFP. [Figure 3] It is a block diagram of an example of the device management system shown in FIG. 1 when configured by one computer. [Figure 4] It is a diagram showing an example of tenant management information shown in FIG. 3. [Figure 5] It is a diagram showing an example of group management information shown in FIG. 3. [Figure 6] It is a diagram showing an example of user management information shown in FIG. 3. [Figure 7] It is a diagram showing an example of device management information shown in FIG. 3. [Figure 8] It is a diagram showing an example of group identification information shown in FIG. 3. [Figure 9] It is a block diagram of an example of the user terminal shown in FIG. 1. [Figure 10]Figure 1 is a sequence diagram of the system's operation when the login page is displayed on the user's device. [Figure 11] Figure 10 shows an example of a login page that appears during the operation shown. [Figure 12] Figure 1 is a sequence diagram of the system's operation when the login button is pressed on the login page. [Figure 13] Figure 1 is a sequence diagram of the system's operation when the sign-up page link is clicked on the login page. [Figure 14] Figure 13 shows an example of a signup page that appears during the operation described. [Figure 15] Figure 1 is a sequence diagram of the system's operation when the sign-up button is pressed on the sign-up page. [Figure 16] Figure 3 is a flowchart illustrating part of the operation of the device management system when performing the sign-up process. [Figure 17] This is a continuation of the flowchart shown in Figure 16. [Figure 18] Figures 16 and 17 show an example of a signup page generated by the actions described. [Figure 19] Figures 16 and 17 show an example of a login page displayed on the user's terminal screen as a result of the operations shown in those figures. [Figure 20] Figure 1 is a sequence diagram of the system's operation when the sign-up email link is clicked on the login page. [Figure 21] (a) This figure shows an example of the body text set in the signup email link shown in Figure 11. (b) This figure shows an example of the body text with a specific string of characters added to the body text shown in Figure 21(a). [Figure 22] Figure 3 is a flowchart illustrating some of the operations of the device management system when a signup email is received. [Figure 23]This is a continuation of the flowchart shown in Figure 22. [Figure 24] Figures 22 and 23 show an example of a password registration page displayed on the user terminal's display unit through the actions shown. [Figure 25] Figure 1 is a sequence diagram of the system's operation when the registration button is pressed on the password registration page. [Figure 26] Figure 3 is a flowchart illustrating the operation of the device management system when performing the password registration process. [Figure 27] This figure shows an example of a password registration page generated by the operation shown in Figure 26. [Figure 28] Figure 1 is a sequence diagram of the system's operation when logging in from an image forming apparatus to a device management system. [Modes for carrying out the invention]

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

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

[0026] Figure 1 is a block diagram of an example of the system 10 according to this embodiment.

[0027] As shown in Figure 1, System 10 includes an image forming apparatus 20 for forming an image. System 10 may also include at least one other image forming apparatus with a configuration similar to that of the image forming apparatus 20. The image forming apparatus may be, for example, a dedicated printer or an MFP (Multifunction Peripheral).

[0028] System 10 includes a device management system 30 for managing the image forming apparatus. The device management system 30 may be composed of one computer, such as a PC (Personal Computer), or of multiple computers. The device management system 30 may be configured on the same LAN (Local Area Network) as the image forming apparatus, or it may be configured on the cloud.

[0029] System 10 includes a user terminal 40 used by users of the device management system 30. System 10 may also include at least one other user terminal with a similar configuration to user terminal 40. The user terminal may be configured as a computer, such as a PC.

[0030] Figure 2 is a block diagram of an example of an image forming apparatus 20 that is configured with an MFP (Multi-Function Printer).

[0031] As shown in Figure 2, the image forming apparatus 20 is a computer comprising: an operation unit 21 which is an operation device such as buttons into which various operations are input; a display unit 22 which is a display device such as an LCD (Liquid Crystal Display) that displays various information; a printer 23 which is a printing device that prints images onto a recording medium such as paper; a scanner 24 which is a reading device that reads images from an original document; a communication unit 25 which is a communication device that communicates with external devices via a network such as a LAN or the Internet, or directly by wired or wireless connection without going through a network; a fax communication unit 26 which is a fax device that performs fax communication with an external facsimile device (not shown) via a communication line such as a public telephone line; a storage unit 27 which is a non-volatile storage device such as a semiconductor memory or HDD (Hard Disk Drive) that stores various information; and a control unit 28 that controls the entire image forming apparatus 20.

[0032] The memory unit 27 can store a system communication program 27a for performing communication with the device management system 30 (see Figure 1). The system communication program 27a may be installed in the image forming apparatus 20 during the manufacturing stage, or it may be additionally installed in the image forming apparatus 20 from an external storage medium such as a USB (Universal Serial Bus) memory, or it may be additionally installed in the image forming apparatus 20 from a network.

[0033] The control unit 28 includes, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory) that stores programs and various data, and a RAM (Random Access Memory) used as a working area for the CPU of the control unit 28. The CPU of the control unit 28 executes programs stored in the storage unit 27 or the ROM of the control unit 28.

[0034] The control unit 28 implements a system communication unit 28a that communicates with the device management system 30 by executing a system communication program 27a.

[0035] Figure 3 is a block diagram of an example of a device management system 30 configured with a single computer.

[0036] As shown in Figure 3, the device management system 30 includes an operation unit 31 which is an operation device such as a keyboard or mouse into which various operations are input; a display unit 32 which is a display device such as an LCD that displays various information; a communication unit 33 which is a communication device that communicates with external devices via a network such as a LAN or the Internet, or directly by wired or wireless connection without going through a network; a storage unit 34 which is a non-volatile storage device such as a semiconductor memory or HDD that stores various information; and a control unit 35 that controls the entire device management system 30.

[0037] The memory unit 34 can store a device management program 34a for managing the image forming apparatus. The device management program 34a may be installed in the device management system 30 during the manufacturing stage, or it may be additionally installed in the device management system 30 from an external storage medium such as a USB memory, or it may be additionally installed in the device management system 30 from a network.

[0038] The storage unit 34 is capable of storing tenant management information 34b for managing tenants of the device management system 30.

[0039] Figure 4 shows an example of tenant management information 34b.

[0040] As shown in Figure 4, the tenant management information 34b includes, for each tenant, a tenant ID as identification information for the tenant, and automatic configuration information indicating whether or not to automatically set the value of a specific item if there is a problem with the value of that item when a guest user account (hereinafter referred to as "guest account") is signed up as a temporary user. The tenant management information 34b shown in Figure 4 is depicted with some information omitted.

[0041] The values ​​for the automatic configuration information can be set, for example, by the administrator of the tenant to which this automatic configuration information applies after logging into the device management system 30.

[0042] As shown in Figure 3, the storage unit 34 is capable of storing group management information 34c for managing the groups to which users of the device management system 30 belong.

[0043] Figure 5 shows an example of group management information 34c.

[0044] As shown in Figure 5, the group management information 34c includes, for each group, a group ID as the group's identification information, the tenant ID of the tenant to which the group belongs, identification information of the image forming apparatus that can be used by users belonging to the group (hereinafter, the identification information of the image forming apparatus is referred to as the "device ID"), and the total number of prints by all users belonging to the group. The device ID of the image forming apparatus that can be used by users belonging to the group can be edited, for example, by the administrator of the tenant to which this group belongs after logging into the device management system 30. The group management information 34c shown in Figure 5 is depicted with some information omitted.

[0045] As shown in Figure 3, the storage unit 34 is capable of storing user management information 34d for managing users of the device management system 30.

[0046] Figure 6 shows an example of user management information 34d.

[0047] As shown in Figure 6, the user management information 34d includes, for each user, the username as user identification information, the user's password, the tenant ID of the tenant to which the user belongs, the group ID of the group to which the user belongs, the user's email address, the user's first name, the user's last name, and the user's role. User roles include, for example, tenant administrator, general user, and guest user. The user management information 34d shown in Figure 6 is depicted with some information omitted.

[0048] As shown in Figure 3, the storage unit 34 is capable of storing device management information 34e, which manages information about the image forming apparatus.

[0049] Figure 7 shows an example of device management information 34e.

[0050] As shown in Figure 7, the device management information 34e includes the device ID of the image forming apparatus and the tenant ID of the tenant to which the image forming apparatus belongs, for each image forming apparatus. The device management information 34e shown in Figure 7 is depicted with some information omitted.

[0051] As shown in Figure 3, the memory unit 34 can store group identification information 34f, which is information for identifying the group to which the guest user belongs.

[0052] Figure 8 shows an example of group identification information 34f.

[0053] As shown in Figure 8, the group identification information 34f includes the tenant ID, domain, and group ID for each group. The group identification information 34f shown in Figure 8 is depicted with some information omitted.

[0054] The value of the group identification information 34f can be set, for example, by a tenant administrator after logging into the device management system 30.

[0055] The control unit 35 shown in Figure 3 includes, for example, a CPU, a ROM that stores programs and various data, and RAM as memory used as a workspace for the CPU of the control unit 35. The CPU of the control unit 35 executes programs stored in the storage unit 34 or the ROM of the control unit 35.

[0056] The control unit 35 implements a device management unit 35a that manages the image forming apparatus by executing the device management program 34a. The device management unit 35a is capable of generating guest accounts and constitutes a guest account generation unit. Therefore, the device management system 30 constitutes a guest account generation system that generates guest accounts. Furthermore, the device management program 34a constitutes a guest account generation program for generating guest accounts.

[0057] Figure 9 is a block diagram of an example of a user terminal 40.

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

[0059] The memory unit 44 can store a web browser program 44a as a program for a web browser. The web browser program 44a may be installed on the user terminal 40 during the manufacturing stage, or it may be additionally installed on the user terminal 40 from an external storage medium such as a USB memory, or it may be additionally installed on the user terminal 40 from a network.

[0060] The storage unit 44 can store an email client program 44b, which is a program for an email client. The email client program 44b may, for example, be installed on the user terminal 40 during the manufacturing stage, or it may be additionally installed on the user terminal 40 from an external storage medium such as a USB memory, or it may be additionally installed on the user terminal 40 from a network.

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

[0062] The control unit 45 implements a web browser 45a by executing a web browser program 44a.

[0063] The control unit 45 implements the email client 45b by executing the email client program 44b.

[0064] Next, we will describe the operation of system 10.

[0065] In the following, the image forming apparatus 20 will be described as a representative image forming apparatus. Similarly, the user terminal 40 will be described as a representative user terminal.

[0066] In the following, we will describe Tenant A on behalf of all tenants.

[0067] First, we will explain the operation of System 10 when a web page for logging in to a specific tenant (hereinafter referred to as the "login page") is displayed by the user terminal 40.

[0068] The login page is provided for each tenant by the device management unit 35a of the device management system 30.

[0069] The following describes the operation of System 10 when the login page for tenant A is displayed by user terminal 40.

[0070] Figure 10 is a sequence diagram of the operation of system 10 when the login page is displayed by the user terminal 40.

[0071] The user of user terminal 40 can instruct the web browser 45a on user terminal 40 to access the login page. When instructed to access the login page, the web browser 45a accesses the login page as shown in Figure 10 (S101).

[0072] When the device management unit 35a of the device management system 30 receives an access in S101, it sends the data of the login page targeted by the access in S101 to the web browser 45a of the user terminal 40 (S102).

[0073] When the user terminal 40's web browser 45a receives data transmitted from the device management system 30 in S102, it displays the login page 400 (see, for example, Figure 11) on the display unit 42 based on the received data (S103).

[0074] Figure 11 shows an example of the login page 400 displayed during the operation shown in Figure 10.

[0075] The login page 400 shown in Figure 11 includes a text box 401 as a widget for entering a username, a text box 402 as a widget for entering a password, a login button 403 as a widget for executing login, a sign-up page link 404 as a link to access a web page for guest account sign-up (hereinafter referred to as the "sign-up page"), and a sign-up email link 405 as a link to send an email for guest account sign-up (hereinafter referred to as the "sign-up email"). The sign-up page is provided for each tenant by the device management unit 35a of the device management system 30. If the login page 400 is the login page for tenant A, then the sign-up page targeted by the sign-up page link 404 is the sign-up page for tenant A. The sign-up email link 405 may also be written in HTML (HyperText Markup Language) using the mailto: command.

[0076] Next, we will explain the operation of system 10 when the login button 403 is pressed on login page 400.

[0077] Figure 12 is a sequence diagram of the operation of system 10 when the login button 403 is pressed on the login page 400.

[0078] A user of the user terminal 40 can press the login button 403 via the operation unit 41 of the user terminal 40 when the login page 400 is displayed on the display unit 42 of the user terminal 40. When the login button 403 is pressed, the web browser 45a of the user terminal 40 sends an instruction to execute the login process (hereinafter referred to as "login processing instruction") to the device management system 30 (S121), as shown in Figure 12. The web browser 45a includes the value entered in the text box 401 at the time the login button 403 is pressed as the username in the login processing instruction. The web browser 45a also includes the value entered in the text box 402 at the time the login button 403 is pressed as the password in the login processing instruction.

[0079] When the device management unit 35a of the device management system 30 receives a login processing instruction sent from the user terminal 40 in S121, it performs authentication based on the username and password combination included in the received login processing instruction (S122). The device management unit 35a determines that authentication is successful if the username and password combination included in the login processing instruction is included in the user management information 34d in association with the tenant ID of the target tenant of the login page 400, i.e., tenant A. On the other hand, the device management unit 35a determines that authentication is failed if the username and password combination included in the login processing instruction is not included in the user management information 34d in association with the tenant ID of the target tenant of the login page 400, i.e., tenant A.

[0080] If authentication in S122 is successful, the device management unit 35a notifies the web browser 45a on the user terminal 40 that login is permitted (S123).

[0081] When the web browser 45a of the user terminal 40 receives the notification in S123, it displays permission to log in on the display unit 42 (S124). If the user of the user terminal 40 is already logged into the device management system 30, they can perform various operations on the device management system 30 via the user terminal 40.

[0082] If authentication in S122 fails, the device management unit 35a notifies the user terminal 40's web browser 45a that login is not permitted (S125).

[0083] When the web browser 45a of the user terminal 40 receives the notification in S125, it displays on the display unit 42 that login is not permitted (S126).

[0084] Next, we will describe the behavior of System 10 when the sign-up page link 404 (see Figure 11) is clicked on the login page 400 (see Figure 11).

[0085] Figure 13 is a sequence diagram of the operation of System 10 when the sign-up page link 404 is clicked on the login page 400.

[0086] When the login page 400 is displayed on the display unit 42 of the user terminal 40, the user of the user terminal 40 can click the sign-up page link 404 via the operation unit 41 of the user terminal 40. When the sign-up page link 404 is clicked, the web browser 45a of the user terminal 40 accesses the sign-up page as shown in Figure 13 (S141).

[0087] When the device management unit 35a of the device management system 30 receives an access in S141, it sends the data of the signup page that was the target of the access in S141 to the web browser 45a of the user terminal 40 (S142).

[0088] When the web browser 45a of the user terminal 40 receives data sent from the device management system 30 in S142, it displays the sign-up page 410 (see, for example, Figure 14) on the display unit 42 based on the received data (S143).

[0089] Figure 14 shows an example of the sign-up page 410 that is displayed during the operation shown in Figure 13.

[0090] The sign-up page 410 shown in Figure 14 includes a text box 411 as a widget for entering the first name, a text box 412 as a widget for entering the last name, a text box 413 as a widget for entering the email address, a text box 414 as a widget for entering the username, a text box 415 as a widget for entering the password, a text box 416 as a widget for entering a password to confirm that it is the same as the password entered in text box 415 (hereinafter referred to as the "confirmation password") to reduce the possibility of registering an incorrect password due to a password entry error, and a sign-up button 417 as a widget for performing the sign-up. The first name, last name, email address, username, password, and confirmation password are items that must be entered for guest account sign-up.

[0091] Figure 15 is a sequence diagram of the operation of System 10 when the sign-up button 417 is pressed on the sign-up page 410.

[0092] A user of user terminal 40 can press the sign-up button 417 via the operation unit 41 of user terminal 40 when the sign-up page 410 is displayed on the display unit 42 of user terminal 40. When the sign-up button 417 is pressed, the web browser 45a of user terminal 40 sends an instruction to execute the sign-up process (hereinafter referred to as "sign-up processing instruction") to the device management system 30 (S161), as shown in Figure 15. The web browser 45a includes the value entered in text box 411 at the time the sign-up button 417 is pressed as the first name in the sign-up processing instruction. The web browser 45a includes the value entered in text box 412 at the time the sign-up button 417 is pressed as the last name in the sign-up processing instruction. The web browser 45a includes the value entered in text box 413 at the time the sign-up button 417 is pressed as the email address in the sign-up processing instruction. The web browser 45a includes the value entered in text box 414 at the time the sign-up button 417 is pressed as the username in the sign-up processing instruction. When the sign-up button 417 is pressed, the web browser 45a includes the value entered in the text box 415 as the password in the sign-up instructions. When the sign-up button 417 is pressed, the web browser 45a includes the value entered in the text box 416 as the confirmation password in the sign-up instructions.

[0093] When the device management unit 35a of the device management system 30 receives a sign-up processing instruction sent from the user terminal 40 in S161, it executes the sign-up process (S162).

[0094] Figure 16 is a flowchart showing part of the operation of the device management system 30 when performing the sign-up process. Figure 17 is a flowchart that continues from the flowchart shown in Figure 16.

[0095] As shown in Figures 16 and 17, the device management unit 35a of the device management system 30 identifies the values ​​of first name, last name, email address, username, password, and confirmation password included in the sign-up processing instruction sent from the user terminal 40 in S161 as candidates for first name, last name, email address, username, password, and confirmation password, respectively (S181).

[0096] When the processing in S181 is completed, the device management unit 35a determines whether the candidate for the first name is empty or not (S182).

[0097] If the device management unit 35a determines in S182 that the first name candidate is empty, it prepares an error message indicating that a first name input is required (S183).

[0098] The device management unit 35a determines in S182 that the first name candidate is not empty, or, after the processing in S183 is completed, determines whether the last name candidate is empty or not (S184).

[0099] If the device management unit 35a determines in S184 that the candidate for the last name is empty, it prepares an error message indicating that the last name must be entered (S185).

[0100] The device management unit 35a determines in S184 that the candidate for the last name is not empty, or, after the processing in S185 is completed, determines whether the candidate for the email address is empty (S186).

[0101] If the device management unit 35a determines in S186 that the candidate email address is empty, it prepares an error message indicating that an email address must be entered (S187).

[0102] If the device management unit 35a determines in S186 that the candidate email address is not empty, it determines whether the candidate email address is already registered in the user management information 34d in association with the current target tenant, i.e., tenant ID of tenant A (S188).

[0103] If the device management unit 35a determines in S188 that a candidate email address has already been registered in the user management information 34d in association with the tenant ID of the current target tenant, it prepares an error message indicating that the entered email address has already been registered (S189).

[0104] When the processing in S189 is completed, the device management unit 35a sets the candidate email address to an empty value (S190).

[0105] When the processing in S187 is completed, or when the device management unit 35a determines in S188 that no candidate email address has yet been registered in the user management information 34d in association with the tenant ID of the current target tenant, or when the processing in S190 is completed, it determines whether the candidate username is empty (S191).

[0106] If the device management unit 35a determines in S191 that the candidate username is empty, it determines whether or not to automatically set the value of a specific item based on the automatic setting information associated with the current target tenant, i.e., tenant ID of tenant A, in tenant management information 34b (S192).

[0107] If the device management unit 35a determines in S192 that it will not automatically set the value of a specific item, it prepares an error message indicating that the username must be entered (S193).

[0108] If the device management unit 35a determines in S191 that the candidate username is not empty, it determines whether the candidate username is already registered in the user management information 34d in association with the current target tenant, i.e., tenant ID of tenant A (S194).

[0109] If the device management unit 35a determines in S194 that a candidate username has already been registered in the user management information 34d in association with the tenant ID of the current target tenant, it determines whether or not to automatically set the value of a specific item based on the automatic setting information associated in the tenant management information 34b with the tenant ID of the current target tenant, i.e., tenant A (S195).

[0110] If the device management unit 35a determines in S195 that it will not automatically set the value of a specific item, it prepares an error message indicating that the entered username is already registered (S196).

[0111] When the processing in S196 is completed, the device management unit 35a sets the candidate username to an empty value (S197).

[0112] If the device management unit 35a determines in S192 or S195 that it is necessary to automatically set the value of a specific item, it generates a username that has not yet been registered in the user management information 34d and associated with the current target tenant, i.e., tenant ID of tenant A (S198). The device management unit 35a may generate a username completely randomly in S198. If the candidate username is not an empty value, the device management unit 35a may generate a username in S198 based on the candidate username.

[0113] When the processing in S198 is completed, the device management unit 35a updates the username candidates with the usernames generated in S198 (S199).

[0114] The device management unit 35a determines whether the password candidate is empty (S200) when the processing in S193 is completed, when it determines in S194 that no username candidate has yet been registered in the user management information 34d in association with the tenant ID of the current target tenant, or when the processing in S197 or S199 is completed.

[0115] If the device management unit 35a determines in S200 that the password candidate is empty, it prepares an error message indicating that a password must be entered (S201).

[0116] If the device management unit 35a determines in S200 that the password candidate is not empty, it then determines whether the confirmation password candidate is empty or not (S202).

[0117] If the device management unit 35a determines in S202 that the candidate for the confirmation password is empty, it prepares an error message indicating that a confirmation password must be entered (S203).

[0118] If the device management unit 35a determines in S202 that the candidate for confirmation password is not empty, it determines whether the password candidate and the confirmation password candidate match (S204).

[0119] If the device management unit 35a determines in S204 that the candidate password and the candidate confirmation password do not match, it prepares an error message indicating that the password and the confirmation password do not match (S205).

[0120] When the processing in S205 is completed, the device management unit 35a sets the candidate for the confirmation password to an empty value (S206).

[0121] The device management unit 35a determines whether an error message has been prepared for the operation shown in Figures 16 and 17 in this case, once the processing of S201 or S203 is completed, or whether the candidate password and the candidate confirmation password match in S204, or once the processing of S206 is completed (S207).

[0122] If the device management unit 35a determines in S207 that an error message has been prepared for the operation shown in Figures 16 and 17, it generates a sign-up page 410 (see, for example, Figure 18) with the following fields: first name candidate, last name candidate, email address candidate, username candidate, password candidate, and confirmation password candidate (S208).

[0123] Figure 18 shows an example of a signup page 410 generated by the operations shown in Figures 16 and 17.

[0124] In the sign-up page 410 shown in Figure 18, the first name, last name, email address, username, password, and confirmation password options are pre-filled in text boxes 411, 412, 413, 414, 415, and 416, respectively. In the sign-up page 410 shown in Figure 18, the email address, username, password, and confirmation password options are all empty.

[0125] As shown in Figures 16 and 17, when the processing in S208 is completed, the device management unit 35a sends all the error message data prepared for the operation shown in Figures 16 and 17, and the data for the sign-up page 410 generated in S208, to the user terminal 40's web browser 45a (S209), and then terminates the operation shown in Figures 16 and 17. Therefore, in S209, the user terminal 40's web browser 45a displays all the error messages sent from the device management system 30 on the display unit 42 of the user terminal 40, and also displays the sign-up page 410 sent from the device management system 30 on the display unit 42.

[0126] If the device management unit 35a of the device management system 30 determines in S207 that it did not prepare an error message for the operations shown in Figures 16 and 17, it determines whether or not there is a group ID associated in the group identification information 34f with the current target tenant, i.e., tenant A's tenant ID and the candidate domain of the email address (S210).

[0127] If the device management unit 35a determines in S210 that there is a group ID associated in the group identification information 34f with the combination of the current target tenant's tenant ID and the candidate domain of the email address, it registers the combination of the group ID associated in the group identification information 34f with the combination of the current target tenant's tenant ID and the candidate domain of the email address, along with the candidate first name, candidate last name, candidate email address, candidate username, and candidate password, in the user management information 34d, associating it with the current target tenant, i.e., tenant A's tenant ID (S211). In other words, the device management unit 35a registers a guest account.

[0128] If the device management unit 35a determines in S210 that there is no group ID associated in the group identification information 34f with the combination of the current target tenant's tenant ID and the candidate domain of the email address, it registers the combination of the candidate first name, candidate last name, candidate email address, candidate username, and candidate password in the user management information 34d, associating it with the current target tenant, i.e., tenant A's tenant ID (S212). In other words, the device management unit 35a registers a guest account.

[0129] When the processing in S211 or S212 is completed, the device management unit 35a generates a login page 400 (see, for example, Figure 19) with candidate usernames and passwords entered (S213).

[0130] Figure 19 shows an example of a login page 400 displayed on the display unit 42 of the user terminal 40 by the operations shown in Figures 16 and 17.

[0131] In the login page 400 shown in Figure 19, suggested usernames and passwords are entered into text boxes 401 and 402, respectively.

[0132] As shown in Figures 16 and 17, when the processing in S213 is completed, the device management unit 35a sends the login page 400 data generated in S213 to the web browser 45a of the user terminal 40 (S214), and terminates the operations shown in Figures 16 and 17. Therefore, the web browser 45a of the user terminal 40 displays the login page 400 sent from the device management system 30 on the display unit 42 in S214.

[0133] Next, we will explain the behavior of System 10 when the sign-up email link 405 (see Figure 11) is clicked on the login page 400 (see Figure 11).

[0134] Figure 20 is a sequence diagram of the actions of System 10 when the sign-up email link 405 is clicked on the login page 400.

[0135] When the login page 400 (see Figure 11) is displayed on the display unit 42 of the user terminal 40, the user of the user terminal 40 can click the sign-up email link 405 (see Figure 11) via the operation unit 41 of the user terminal 40. When the sign-up email link 405 is clicked, the web browser 45a of the user terminal 40 instructs the email client 45b to generate an email corresponding to the sign-up email link 405, as shown in Figure 20 (S231).

[0136] When email client 45b receives the instruction in S231, it generates the email specified in S231 (S232). Here, email client 45b inputs the email address set in the signup email link 405 as the recipient email address for the email generated in S232. Also, if the signup email link 405 is set to, for example, the body 421 shown in Figure 21(a), email client 45b inputs the body 421 shown in Figure 21(a) as the body of the email generated in S232.

[0137] Figure 21(a) shows an example of the body text 421 set in the signup email link 405. Figure 21(b) shows an example of the body text 422 in which a specific string has been added to the body text 421 shown in Figure 21(a).

[0138] The text 421 shown in Figure 21(a) shows the fields for first name, last name, and username. First name, last name, and username are specific fields that need to be entered for guest account signup and should be included in the signup email. When the text 421 shown in Figure 21(a) is displayed, the user of the user terminal 40 can enter the value of the first name by associating it with the first name field, the value of the last name by associating it with the last name field, and the value of the username by associating it with the username field, as shown in Figure 21(b). As shown in Figure 21(a), showing the fields in advance can reduce the possibility of missing information. Note that the email address is not included in the body of the signup email, but it is included in the header of the signup email and is a specific field that needs to be entered for guest account signup and should be included in the signup email.

[0139] Once the processing in S232 is complete, the user of user terminal 40 can instruct email client 45b to send an email. As shown in Figure 20, when email client 45b is instructed to send an email, it sends an email, i.e., a signup email (S233).

[0140] In the above scenario, the user terminal 40 clicks the sign-up email link 405 on the login page 400 to send a sign-up email. However, the user terminal 40 may send a sign-up email by means other than clicking the sign-up email link 405 on the login page 400. For example, a user of the user terminal 40 may send a sign-up email by clicking a sign-up email link located elsewhere than the login page 400, such as on a webpage other than the login page 400 provided by the device management system 30, or on a webpage provided by a system outside the device management system 30. Alternatively, a user of the user terminal 40 may generate a sign-up email using the email client 45b by manually entering the email address of the device management system 30 as the recipient's email address.

[0141] The device management unit 35a of the device management system 30 may, when it receives an email with no subject or body, i.e., a blank email, reply with an email having the body 421 shown in Figure 21(a). When the device management unit 35a replies with an email having the body 421 shown in Figure 21(a) when it receives a blank email, the user of the user terminal 40 may send a blank email using the email client 45b of the user terminal 40, with the email address of the device management system 30 as the recipient email address, and then use the email reply from the device management system 30 to create a sign-up email using the email client 45b.

[0142] Next, we will explain how the device management system 30 operates when it receives a sign-up email.

[0143] Figure 22 is a flowchart showing part of the operation of the device management system 30 when a signup email is received. Figure 23 is a flowchart that continues from the flowchart shown in Figure 22.

[0144] When the device management unit 35a of the device management system 30 receives a sign-up email, as shown in Figures 22 and 23, it identifies the first name value, last name value, and username value contained in the sign-up email as candidates for the first name, last name, and username, respectively, and also identifies the email address of the sender of the sign-up email as a candidate for the email address (S251).

[0145] When the processing in S251 is completed, the device management unit 35a determines whether the first name candidate is empty or not (S252).

[0146] If the device management unit 35a determines in S252 that the first name candidate is empty, it prepares an error message indicating that a first name input is required (S253).

[0147] The device management unit 35a determines in S252 that the first name candidate is not empty, or, after the processing in S253 is completed, determines whether the last name candidate is empty or not (S254).

[0148] If the device management unit 35a determines in S254 that the candidate for the last name is empty, it prepares an error message indicating that the last name must be entered (S255).

[0149] In S254, the device management unit 35a determines that the candidate for the last name is not empty, or when the processing in S255 is completed, it determines whether the candidate for the email address is already registered in the user management information 34d in association with the current target tenant, i.e., tenant ID of tenant A (S256).

[0150] If the device management unit 35a determines in S256 that a candidate email address has already been registered in the user management information 34d in association with the tenant ID of the current target tenant, it prepares an error message indicating that the entered email address is already registered (S257).

[0151] When the processing in S257 is completed, the device management unit 35a sets the candidate email address to an empty value (S258).

[0152] The device management unit 35a determines in S256 that no candidate email address has yet been registered in the user management information 34d in association with the tenant ID of the current target tenant, or, after the processing in S258 is completed, it determines whether the candidate username is empty (S259).

[0153] If the device management unit 35a determines in S259 that the candidate username is empty, it determines whether or not to automatically set the value of a specific item based on the automatic setting information associated with the current target tenant, i.e., tenant ID of tenant A, in tenant management information 34b (S260).

[0154] If the device management unit 35a determines in S260 that it will not automatically set the value of a specific item, it prepares an error message indicating that the username must be entered (S261).

[0155] If the device management unit 35a determines in S259 that the candidate username is not empty, it determines whether the candidate username is already registered in the user management information 34d in association with the current target tenant, i.e., tenant ID of tenant A (S262).

[0156] If the device management unit 35a determines in S262 that a candidate username has already been registered in the user management information 34d in association with the tenant ID of the current target tenant, it determines whether or not to automatically set the value of a specific item based on the automatic setting information associated in the tenant management information 34b with the tenant ID of the current target tenant, i.e., tenant A (S263).

[0157] If the device management unit 35a determines in S263 that it will not automatically set the value of a specific item, it prepares an error message indicating that the entered username is already registered (S264).

[0158] When the processing in S264 is completed, the device management unit 35a sets the candidate username to an empty value (S265).

[0159] If the device management unit 35a determines in S260 or S263 that it is necessary to automatically set the value of a specific item, it generates a username that has not yet been registered in the user management information 34d, associated with the current target tenant, i.e., tenant ID of tenant A (S266). The device management unit 35a may generate a username completely randomly in S266. If the candidate username is not an empty value, the device management unit 35a may generate a username in S266 based on the candidate username.

[0160] When the processing in S266 is completed, the device management unit 35a updates the username candidates with the usernames generated in S266 (S267).

[0161] When the processing of S261 is completed, or when the device management unit 35a determines in S262 that no candidate usernames have yet been registered in the user management information 34d in association with the tenant ID of the current target tenant, or when the processing of S265 or S267 is completed, it determines whether or not an error message has been prepared for the operation shown in Figures 22 and 23 (S268).

[0162] If the device management unit 35a determines in S268 that an error message has been prepared for the operation shown in Figures 22 and 23, it generates a sign-up page 410 (see, for example, Figure 18) with suggested first names, last names, email addresses, and usernames entered (S269).

[0163] As shown in Figures 22 and 23, when the processing in S269 is completed, the device management unit 35a sends an email containing all the error messages prepared for the operation shown in Figures 22 and 23, and the URL of the sign-up page 410 generated in S269, to the email address of the sender of the sign-up email (S270), and then terminates the operation shown in Figures 22 and 23. Therefore, after the user of the user terminal 40 receives the email sent in S270 via the email client 45b of the user terminal 40, they can click the URL contained in this email via the operation unit 41 of the user terminal 40. When the URL contained in the email sent in S270 is clicked, the email client 45b causes the user terminal 40's web browser 45a to access this URL. Therefore, as shown in Figure 18, the web browser 45a displays the sign-up page 410 corresponding to this URL on the display unit 42.

[0164] If the device management unit 35a of the device management system 30 determines in S268 that it did not prepare an error message for the operation shown in Figures 22 and 23, it determines whether or not there is a group ID associated in the group identification information 34f with the current target tenant, i.e., tenant A's tenant ID and the candidate domain of the email address (S271).

[0165] If the device management unit 35a determines in S271 that there is a group ID associated in the group identification information 34f with the combination of the current target tenant's tenant ID and the candidate domain of the email address, it registers the combination of the group ID associated in the group identification information 34f with the combination of the current target tenant's tenant ID and the candidate domain of the email address, along with the candidate first name, candidate last name, candidate email address, and candidate username, in the user management information 34d, associating it with the tenant ID of the current target tenant, i.e., tenant A (S272). In other words, the device management unit 35a registers a guest account.

[0166] If the device management unit 35a determines in S271 that there is no group ID associated in the group identification information 34f with the combination of the current target tenant's tenant ID and the candidate domain of the email address, it registers the combination of the candidate first name, candidate last name, candidate email address, and candidate username in the user management information 34d, associating it with the current target tenant, i.e., tenant A's tenant ID (S273). In other words, the device management unit 35a registers a guest account.

[0167] When the processing in S272 or S273 is completed, the device management unit 35a sends an email to the email address of the sender of the signup email (S274) containing the URL of the web page for registering the guest account password (hereinafter referred to as the "password registration page") 430 (see Figure 24) and a message indicating that the guest account registration was successful, and then terminates the operations shown in Figures 22 and 23. Therefore, after the user of the user terminal 40 receives the email sent in S274 via the email client 45b of the user terminal 40, the user can click the URL contained in this email via the operation unit 41 of the user terminal 40. When the URL contained in the email sent in S274 is clicked, the email client 45b causes the web browser 45a of the user terminal 40 to access this URL. Therefore, the web browser 45a displays the password registration page 430 corresponding to this URL on the display unit 42.

[0168] Figure 24 shows an example of a password registration page 430 displayed on the display unit 42 of the user terminal 40 by the operations shown in Figures 22 and 23.

[0169] The password registration page 430 shown in Figure 24 includes a text box 431 as a widget for entering a password, a text box 432 as a widget for entering a confirmation password, and a registration button 433 as a widget for registering the password. The password registration page is provided for each tenant by the device management unit 35a of the device management system 30. If the login page 400 is the login page for tenant A, then the password registration page 430 is the password registration page for tenant A.

[0170] Figure 25 is a sequence diagram of the operation of system 10 when the registration button 433 is pressed on the password registration page 430.

[0171] A user of the user terminal 40 can press the registration button 433 via the operation unit 41 of the user terminal 40 when the password registration page 430 is displayed on the display unit 42 of the user terminal 40. When the registration button 433 is pressed, the web browser 45a of the user terminal 40 sends an instruction to the device management system 30 to execute the password registration process (hereinafter referred to as "password registration instruction") as shown in Figure 25 (S291). The web browser 45a includes the value entered in the text box 431 as the password in the password registration instruction when the registration button 433 is pressed. The web browser 45a also includes the value entered in the text box 432 as the confirmation password in the password registration instruction when the registration button 433 is pressed.

[0172] When the device management unit 35a of the device management system 30 receives a password registration instruction sent from the user terminal 40 in S291, it executes the password registration process (S292).

[0173] Figure 26 is a flowchart showing the operation of the device management system 30 when performing the password registration process.

[0174] As shown in Figure 26, in S291, the device management unit 35a of the device management system 30 identifies the password value and the confirmation password value included in the password registration instruction sent from the user terminal 40 as a password candidate and a confirmation password candidate, respectively (S311).

[0175] When the processing in S311 is completed, the device management unit 35a determines whether the password candidate is empty or not (S312).

[0176] If the device management unit 35a determines in S312 that the password candidate is empty, it prepares an error message indicating that a password must be entered (S313).

[0177] If the device management unit 35a determines in S312 that the password candidate is not empty, it then determines whether the confirmation password candidate is empty or not (S314).

[0178] If the device management unit 35a determines in S314 that the candidate for the confirmation password is empty, it prepares an error message indicating that a confirmation password must be entered (S315).

[0179] If the device management unit 35a determines in S314 that the candidate for confirmation password is not empty, it determines whether the password candidate and the confirmation password candidate match (S316).

[0180] If the device management unit 35a determines in S316 that the candidate password and the candidate confirmation password do not match, it prepares an error message indicating that the password and the confirmation password do not match (S317).

[0181] When the processing in S317 is completed, the device management unit 35a sets the candidate for the confirmation password to an empty value (S318).

[0182] When the processing in S313 or S315 is completed, or when it is determined in S316 that the password candidate and the confirmation password candidate match, or when the processing in S318 is completed, the device management unit 35a determines whether or not an error message has been prepared for the operation shown in Figure 26 (S319).

[0183] If the device management unit 35a determines in S319 that an error message has been prepared for the operation shown in Figure 26, it generates a password registration page 430 (see, for example, Figure 27) in which password candidates and confirmation password candidates are entered (S320).

[0184] Figure 27 shows an example of a password registration page 430 generated by the operation shown in Figure 26.

[0185] In the password registration page 430 shown in Figure 27, the password candidate and confirmation password candidate are entered in text boxes 431 and 432, respectively. In the password registration page 430 shown in Figure 27, the confirmation password candidate is empty.

[0186] As shown in Figure 26, when the processing in S320 is completed, the device management unit 35a sends all the error message data prepared for the operation shown in Figure 26 and the password registration page data generated in S320 to the user terminal 40's web browser 45a (S321), and then terminates the operation shown in Figure 26. Therefore, in S321, the user terminal 40's web browser 45a displays all the error messages sent from the device management system 30 on the display unit 42 of the user terminal 40, and also displays the password registration page 430 sent from the device management system 30 on the display unit 42.

[0187] If the device management unit 35a of the device management system 30 determines in S319 that it did not prepare an error message for the operation shown in Figure 26, it registers a password candidate in the user management information 34d record, which includes a combination of the current target tenant's tenant ID, i.e., tenant A, and the username registered in the user management information 34d in the previous S272 (see Figure 23) or S273 (see Figure 23) (S322).

[0188] When the processing in S322 is completed, the device management unit 35a generates a login page 400 (see, for example, Figure 19) in which the username and password candidates registered in the user management information 34d in the preceding S272 or S273 are entered (S323).

[0189] When the processing in S323 is completed, the device management unit 35a sends the login page 400 data generated in S323 to the web browser 45a of the user terminal 40 (S324), and terminates the operation shown in Figure 26. Therefore, the web browser 45a of the user terminal 40 displays the login page 400 sent from the device management system 30 in the display unit 42 in S324.

[0190] Next, we will explain the operation of system 10 when logging in to the device management system 30 from the image forming apparatus 20.

[0191] Figure 28 is a sequence diagram of the operation of system 10 when logging in from the image forming apparatus 20 to the device management system 30.

[0192] Users of the image forming apparatus 20 can instruct the system to log in to the device management system 30 via the operation unit 21 of the image forming apparatus 20. When the system communication unit 28a of the image forming apparatus 20 receives an instruction to log in to the device management system 30, it sends an instruction to log in to the device management system 30 (hereinafter referred to as "login instruction") to the device management system 30 (S341). The system communication unit 28a includes the username entered via the operation unit 21 of the image forming apparatus 20 in the login instruction. The system communication unit 28a also includes the password entered via the operation unit 21 of the image forming apparatus 20 in the login instruction.

[0193] When the device management unit 35a of the device management system 30 receives a login instruction from the image forming apparatus 20 in S341, it performs authentication based on the username and password combination included in the received login instruction (S342). The device management unit 35a determines that authentication is successful if the username and password combination included in the login instruction is included in the user management information 34d in association with the tenant ID of the tenant A to which the image forming apparatus 20 belongs. On the other hand, the device management unit 35a determines that authentication is failed if the username and password combination included in the login instruction is not included in the user management information 34d in association with the tenant ID of the tenant A to which the image forming apparatus 20 belongs.

[0194] If authentication in S342 is successful, the device management unit 35a determines whether the device ID of the image forming apparatus 20 is included in the device IDs that are indicated as available in the group management information 34c for the group ID shown in user management information 34d, which is associated with the tenant ID of tenant A to which the image forming apparatus 20 belongs, and the username included in the login instruction (S343).

[0195] If the device management unit 35a determines in S343 that the device ID of the image forming apparatus 20 is included in the device IDs that are indicated as available in the group management information 34c for the group ID shown in user management information 34d, which is associated with the tenant ID of tenant A to which the image forming apparatus 20 belongs, i.e., tenant A, and the username included in the login instruction, it notifies the system communication unit 28a of the image forming apparatus 20 of permission to log in (S344).

[0196] When the system communication unit 28a of the image forming apparatus 20 receives the notification in S344, it displays permission to log in on the display unit 22 (S345). If the user of the image forming apparatus 20 is logged into the device management system 30, they can perform various operations on the device management system 30 via the image forming apparatus 20.

[0197] If the device management unit 35a determines in S343 that the device ID of the image forming apparatus 20 is not included in the device IDs that are indicated as available in the group management information 34c for the group ID shown in user management information 34d, which is associated with the tenant ID of tenant A to which the image forming apparatus 20 belongs, i.e., tenant A, and the username included in the login instruction, then it notifies the system communication unit 28a of the image forming apparatus 20 that the login is not permitted (S346).

[0198] When the system communication unit 28a of the image forming apparatus 20 receives the notification in S346, it displays "Login denied" on the display unit 22 (S347).

[0199] If authentication in S342 fails, the device management unit 35a notifies the system communication unit 28a of the image forming apparatus 20 that login is not permitted (S348).

[0200] When the system communication unit 28a of the image forming apparatus 20 receives the notification in S348, it displays "Login denied" on the display unit 22 (S349).

[0201] As explained above, when the device management system 30 receives a sign-up email, if the value of at least one specific item that should be included in the sign-up email among the items that need to be entered for guest account sign-up is not included in the sign-up email under certain conditions (YES in S268), it replies with an email containing the URL of the sign-up page (S270), so that the user can access the URL of the sign-up page and generate a guest account via the sign-up page.

[0202] When the device management system 30 replies with an email containing the URL of the signup page, it notifies the user of specific items that are not included in the signup email but whose values ​​meet certain conditions (S253, S255, S257, S261, S264, and S270), thereby allowing the user to be aware of specific items that are not included in the signup email but whose values ​​meet certain conditions.

[0203] When the device management system 30 receives a sign-up email, if the value of at least one specific item is not included in the sign-up email in a state that satisfies a specific condition, it generates a sign-up page (S251, S258, S265, and S269) in which the value of the specific item included in the sign-up email in a state that satisfies the specific condition is entered into the field, i.e., the text box, of the specific item included in the sign-up email in a state that satisfies the specific condition, and leaves the text box of the specific item not included in the sign-up email in a state that satisfies the specific condition empty. It then replies with an email containing the URL of the generated sign-up page (S270), thereby facilitating the user's value input work on the sign-up page.

[0204] When the device management system 30 receives a sign-up email, if the values ​​of all specific items in the sign-up email meet certain conditions (NO in S268), it replies with an email containing a URL to the password registration page (S213), thereby facilitating the user's guest account sign-up process.

[0205] Guest accounts are for temporary use. Therefore, some users may not be particularly concerned with values ​​such as usernames. When the device management system 30 receives a sign-up email, if the value of at least one specific item is not included in the sign-up email in a state that meets certain conditions (YES in S259 or YES in S262), it automatically sets the value of the specific item that is not included in the sign-up email in a state that meets certain conditions (S266-S267), thereby simplifying the process of signing up for a guest account by users.

[0206] When the device management system 30 receives a sign-up email, it identifies the group to which the guest account belongs based on the domain of the sign-up email (S272), thereby facilitating the user's sign-up process for the guest account. [Explanation of Symbols]

[0207] 30. Device Management Systems (Guest Account Generation Systems, Information Processing Devices, Computers) 34a Device management program (guest account generation program) 35a Device Management Unit (Guest Account Generation Unit) 410 Sign-up Page 411, 412, 413, 414, 415, 416 Text boxes (fields) 421, 422 Main text (body of the email) 430 Password Registration Page

Claims

1. It includes a guest account generation unit that generates a guest account as a temporary user account, The guest account generation system is characterized in that, when the guest account generation unit receives a signup email as an email for signing up for the guest account, if the value of at least one specific item that should be included in the signup email among the items that need to be entered for signing up for the guest account is not included in the signup email in a state that satisfies certain conditions, the unit replies with an email containing the URL of the signup page as a web page for signing up for the guest account.

2. The guest account generation system according to claim 1, characterized in that when the guest account generation unit replies with an email containing the URL of the sign-up page, it notifies the guest of the specific items that are not included in the sign-up email, provided that the values ​​satisfy the specific conditions.

3. The aforementioned signup page includes fields for which values ​​for the aforementioned specific items are entered, The guest account generation system according to claim 1, characterized in that, when the guest account generation unit receives the signup email, if the value of at least one of the specified items is not included in the signup email in a state that satisfies the specified conditions, it inputs the value of the specified item included in the signup email in a state that satisfies the specified conditions into the field of the specified item included in the signup email in a state that satisfies the specified conditions, generates a signup page in which the field of the specified item not included in the signup email in a state that satisfies the specified conditions is left blank, and replies with an email containing the URL of the generated signup page.

4. The guest account generation system according to claim 1, characterized in that when the guest account generation unit receives the signup email, and the values ​​of all the specified items are included in the signup email in a state that satisfies the specified conditions, it replies with an email containing a URL for a password registration page, which is a web page for registering the password for the guest account.

5. The guest account generation system according to claim 1, characterized in that when the guest account generation unit receives the sign-up email, if the value of at least one of the specific items is not included in the sign-up email in a state that satisfies the specific conditions, it automatically sets the value of the specific item that is not included in the sign-up email in a state that satisfies the specific conditions.

6. The guest account generation system according to claim 1, characterized in that when the guest account generation unit receives the signup email, it identifies the group to which the guest account belongs based on the domain of the signup email.

7. It includes a guest account generation unit that generates a guest account as a temporary user account, The information processing device is characterized in that, when the guest account generation unit receives a signup email as an email for signing up for the guest account, if the value of at least one specific item that should be included in the signup email among the items that need to be entered for signing up for the guest account is not included in the signup email in a state that satisfies certain conditions, the unit replies with an email containing the URL of the signup page as a web page for signing up for the guest account.

8. A computer implements a guest account generation unit that generates guest accounts as temporary user accounts. The guest account generation program is characterized in that, when the guest account generation unit receives a signup email as an email for signing up for the guest account, if the value of at least one specific item that should be included in the signup email among the items that need to be entered for signing up for the guest account is not included in the signup email in a manner that satisfies certain conditions, the guest account generation unit replies with an email containing the URL of the signup page as a web page for signing up for the guest account.

Images