Electronic apparatus, log-in program, and information processing system

Abstract

To provide an electronic apparatus, a log-in program, and an information processing system with which it is possible to shorten the time needed for log-in to succeed, when a tenant as a login destination is not specified.SOLUTION: An image processing device includes the user ID of a user and the tenant ID of a tenant in association in successful log-in information (S143) when a log-in by a user to a tenant provided by a device collaboration system is successful ("successful" in S141), and executes log-in processing to the tenant associated with the user ID of the user in the successful log-in information (S132-S135 and S137-S138) when the tenant as a login destination is not specified and log-in by the user is specified and when the user ID of the user is included in the successful log-in information (Yes in S131).SELECTED DRAWING: Figure 8

Description

[Technical field]

[0001] The present invention relates to an electronic device for logging in to a tenant provided by a tenant providing system, a login program, and an information processing system. [Background technology]

[0002] 2. Description of the Related Art Conventionally, there has been known an information processing system including an electronic device and a tenant providing system that provides services to a plurality of tenants (see, for example, Patent Documents 1 and 2). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2020-154447 A [Patent Document 2] Patent Publication No. 2021-043902 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in conventional information processing systems, when a user is instructed to log in without specifying the tenant to log in to, it is conceivable that the login process would be performed in turn for each of multiple tenants until the login is successful, but there is a problem in that it may take a long time for the user of the electronic device to successfully log in to a tenant.

[0005] Therefore, an object of the present invention is to provide an electronic device, a login program, and an information processing system that can reduce the time required for successful login when the tenant to which the login is to be made is not specified. [Means for solving the problem]

[0006] The electronic device of the present invention is characterized in that, when a user successfully logs in to a tenant provided by a tenant providing system that provides multiple tenants, identification information of the user who successfully logged in to the tenant and identification information of the tenant into which the user successfully logged in are associated and included in specific information, and when a user is instructed to log in without specifying the tenant to log in to, if identification information of the user to be logged in is not included in the specific information, the electronic device executes a login process for each of the multiple tenants in turn until the login is successful, and when a user is instructed to log in without specifying the tenant to log in to, if identification information of the user to be logged in to is included in the specific information, the electronic device executes a login process for the tenant that is associated in the specific information with the identification information of the user to be logged in to.

[0007] With this configuration, when a user is instructed to log in without specifying a tenant to log in to, if the user has previously successfully logged in to a tenant, the electronic device of the present invention performs login processing on the tenant to which the user has previously successfully logged in, thereby reducing the time required for successful login when a tenant to log in to is not specified.

[0008] When a user is instructed to log in without specifying the tenant to which the login is to be made, and the specific information does not include identification information of the user to be logged in, the electronic device of the present invention may perform a login process for each of the multiple tenants in order of the number of users associated with them in the specific information until the login is successful.

[0009] With this configuration, when a user is instructed to log in without specifying a tenant to log in to, and when the identification information of this user is not included in the specific information, the electronic device of the present invention executes login processing for each of a plurality of tenants in descending order of the number of users associated with the specific information until login is successful, so that login processing can be preferentially executed for tenants in which the user is likely to be registered. Therefore, the electronic device of the present invention can reduce the time required for login to be successful when a tenant to log in to is not specified.

[0010] The electronic device of the present invention may, when a user successfully logs in to the tenant, include in the specific information identification information of the user who successfully logged in to the tenant, identification information of the tenant where the user successfully logged in, and the number of times the user successfully logged in to the tenant, in association with each other; and when a user is instructed to log in without specifying the tenant to log in to, when the identification information of the user to be logged in is included in the specific information in association with identification information of multiple tenants, perform a login process for each of the multiple tenants associated in the specific information with the identification information of the user to be logged in, in order of the number of times associated in the specific information that is greatest.

[0011] With this configuration, in the electronic device of the present invention, when a user successfully logs in to a tenant, the electronic device includes in the specific information the identification information of the user, the identification information of the tenant, and the number of times the user has successfully logged in to the tenant in association with each other, and in the case where a login by a user is instructed without specifying a tenant to log in to, when the identification information of the user is included in the specific information in association with the identification information of multiple tenants, the electronic device executes a login process for each of the multiple tenants associated with the identification information of the user in the specific information in descending order of the number of times associated in the specific information, so that the electronic device can prioritize the login process for the tenant with the highest frequency of login. Therefore, the electronic device of the present invention can reduce the time required for a login to be successful when a tenant to log in to is not specified.

[0012] The electronic device of the present invention, when a user successfully logs in to the tenant, may include in the specific information identification information of the user who successfully logged in to the tenant, identification information of the tenant where the user successfully logged in, and the number of times the user successfully logged in to the tenant, in association with each other, and when the tenant to which the user is to log in is specified and a user is instructed to log in, may arrange the tenants in order of the number of times that the identification information of the user to be logged in and the identification information of the tenant are associated in the specific information, and display them as options for specifying the login destination.

[0013] With this configuration, when a user successfully logs in to a tenant, the electronic device of the present invention associates the user's identification information, the tenant's identification information, and the number of times the user has successfully logged in to the tenant in the specific information, and when a login destination tenant is specified and a user is instructed to log in, the electronic device arranges the tenants in order of the number of times the user's identification information and tenant identification information are associated in the specific information, and displays them as options for specifying a login destination, so that tenants with a high login frequency can be preferentially displayed at the top of the options for specifying a login destination. Therefore, the electronic device of the present invention can improve convenience.

[0014] The login program of the present invention is characterized in that, when a user successfully logs in to a tenant provided by a tenant providing system that provides multiple tenants, an operation of associating identification information of the user who has successfully logged in to the tenant with identification information of the tenant into which the user has successfully logged in and including them in specific information; an operation of executing a login process for each of the multiple tenants in turn until the login is successful, when a user is instructed to log in without specifying the tenant to which the login is to be made and identification information of the user who is the target of the login is not included in the specific information; and an operation of executing a login process for the tenant that is associated in the specific information with the identification information of the user who is the target of the login, when a user is instructed to log in without specifying the tenant to which the login is to be made and identification information of the user who is the target of the login is included in the specific information.

[0015] With this configuration, when an electronic device executing the login program of the present invention is instructed to log in by a user without specifying a tenant to log in to, and the user has previously successfully logged in to a tenant, the electronic device executes the login process for the tenant to which the user has previously successfully logged in, thereby reducing the time required for successful login when a tenant to log in to is not specified.

[0016] The information processing system of the present invention comprises an electronic device and a tenant providing system that provides a plurality of tenants, and when a user successfully logs in to a tenant provided by the tenant providing system, the electronic device corresponds identification information of the user who successfully logged in to the tenant with identification information of the tenant into which the user successfully logged in and includes them in specific information, and when a user is instructed to log in without specifying the tenant to which the user is to log in, if identification information of the user to be logged in is not included in the specific information, the electronic device executes a login process for each of the plurality of tenants in turn until the login is successful, and when a user is instructed to log in without specifying the tenant to which the user is to log in, if identification information of the user to be logged in is included in the specific information, the electronic device executes a login process for the tenant that is associated in the specific information with the identification information of the user to be logged in.

[0017] With this configuration, in the information processing system of the present invention, when a user is instructed to log in from an electronic device without specifying a tenant to log in to, if the user has previously successfully logged in to a tenant from this electronic device, the electronic device executes login processing for the tenant that the user has previously successfully logged in to from this electronic device, thereby reducing the time required for successful login when the tenant to log in to is not specified. Effect of the Invention

[0018] The electronic device, the login program, and the information processing system of the present invention can reduce the time required for successful login when the tenant to which the login is to be made is not specified. [Brief description of the drawings]

[0019] [Figure 1] 1 is a block diagram of an image processing system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a block diagram of an example of the device cooperation system shown in FIG. 1 when configured by one computer. [Diagram 3] 3 is a diagram showing an example of application management information shown in FIG. 2. [Figure 4] 2 is a block diagram of an example of the image processing device shown in FIG. 1 when configured as an MFP. [Diagram 5] 5 is a diagram illustrating an example of tenant information illustrated in FIG. 4. [Figure 6] FIG. 5 is a diagram showing an example of successful login information shown in FIG. [Figure 7] 5 is a flowchart showing a part of the operation of the image processing device shown in FIG. 4 when an application program is started. [Figure 8] 8 is a continuation of the flowchart shown in FIG. 7. [Figure 9] 8 is a continuation of the flowchart shown in FIG. 7 and is different from the flowchart shown in FIG. [Figure 10] 10 is a continuation of the flowchart shown in FIG. 9. [Figure 11] 5 is a diagram showing an example of a login screen displayed on a display unit shown in FIG. 4. FIG. [Figure 12] 3 is a flowchart of an operation of the device cooperation system shown in FIG. 2 when a login request is received from the image processing device. [Figure 13] 5 is a diagram illustrating an example of successful-login tenant information generated by the image processing apparatus illustrated in FIG. 4. FIG. [Figure 14]5 is a diagram showing an example of the successful login information shown in FIG. 4 in a case where a record including a combination of ID card information and a tenant ID and a record including a combination of a user ID and a tenant ID are generated together. FIG. [Figure 15] 11 is a flowchart showing a modification of part of the operations shown in FIGS. 7 to 10. [Figure 16] 16 is a flowchart showing a partial modification of the operations shown in FIGS. 7 to 10 that differs from the portion shown in FIG. [Figure 17] 5 is a diagram illustrating an example of tenant information for login processing generated by the image processing apparatus illustrated in FIG. 4. FIG. [Figure 18] 17 is a flowchart showing a modification of a part of the operations shown in FIGS. 7 to 10 that is different from the parts shown in FIGS. 15 and 16. FIG. [Figure 19] 5 is a flowchart of the operation of the image processing device shown in FIG. 4 in the case where the order of tenant IDs displayed as options in a combo box on the login screen is changed. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0020] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0021] First, a configuration of an image processing system as an information processing system according to the present embodiment will be described.

[0022] FIG. 1 is a block diagram of an image processing system 10 according to the present embodiment.

[0023] As shown in FIG. 1, the image processing system 10 includes a device linking system 20 that links with the image processing device. The device linking system 20 can realize, by linking with the image processing device, cloud printing, which is a function of downloading a print job stored on a cloud to the image processing device and having the image processing device execute the downloaded print job, and cloud scanning, which is a function of uploading scan data read from a document by the image processing device to the cloud. The device linking system 20 may be configured with one computer such as a PC (Personal Computer), or may be configured with multiple computers. The device linking system 20 may be realized on the cloud. The device linking system 20 provides multiple tenants as sites, and constitutes a tenant providing system of the present invention. The device linking system 20 generates a tenant for each organization to which a user other than the administrator of the image processing device belongs.

[0024] The image processing system 10 includes an image processing device 30 as an electronic device. The image processing system 10 may include at least one other image processing device in addition to the image processing device 30. The image processing device may be configured, for example, by an MFP (Multifunction Peripheral), a dedicated printer device, a dedicated scanner device, or the like.

[0025] The device linking system 20 and the image processing device are capable of communicating with each other via a network 11 such as the Internet.

[0026] FIG. 2 is a block diagram of an example of a device collaboration system 20 configured by one computer.

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

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

[0029] The storage unit 24 stores application management information 24b for managing application programs of the image forming apparatus.

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

[0031] 3, the application management information 24b includes identification information of an application program (hereinafter referred to as "application ID"), identification information of a tenant (hereinafter referred to as "tenant ID"), a user ID as identification information of a user, a password of the user, and information of an ID card of the user (hereinafter referred to as "ID card information"). The ID card information is also identification information of a user, like the user ID.

[0032] A plurality of tenants can be set for each application program.

[0033] An administrator of an image processing device can be associated with multiple tenants for each application program, whereas a user other than the administrator of the image processing device can be associated with only one tenant for each application program.

[0034] Only one of the password and ID card information may be included for a user ID.

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

[0036] The control unit 25 executes the device cooperation program 24a to realize a device cooperation unit 25a that cooperates with the image processing device.

[0037] FIG. 4 is a block diagram of an example of the image processing device 30 when configured as an MFP.

[0038] As shown in FIG. 4, the image processing device 30 includes an operation unit 31 which is an operation device such as buttons through which various operations are input, a display unit 32 which is a display device such as an LCD that displays various information, an ID card reader 33 for reading ID card information from an ID card, a printer 34 which is a printing device that prints images on a recording medium such as paper, a scanner 35 which is a reading device that reads images from a document, a communication unit 36 ​​which is a communication device that communicates with an external device via a network such as a LAN or the Internet, or directly by wire or wirelessly without using a network, a fax communication unit 37 which is a fax device that communicates by fax with an external facsimile machine (not shown) via a communication line such as a public telephone line, a memory unit 38 which is a non-volatile memory device such as a semiconductor memory or HDD that stores various information, and a control unit 39 which controls the entire image processing device 30.

[0039] The storage unit 38 can store an application program 38a for linking with the device linking system 20. The storage unit 38 can store at least one application program for linking with the device linking system 20 other than the application program 38a. The application program may be installed in the image processing device 30 during the manufacturing stage of the image processing device 30, or may be additionally installed in the image processing device 30 from an external storage medium such as a USB memory, or may be additionally installed in the image processing device 30 from a network. The application program constitutes a login program for executing a login process for a tenant provided by the device linking system 20.

[0040] The storage unit 38 stores tenant information 38b indicating a tenant, which is a site created for each organization to which a user other than the administrator of the image processing device belongs, among sites provided by the device linking system 20. The storage unit 38 can store at least one piece of tenant information similar to the tenant information 38b, in addition to the tenant information 38b. The storage unit 38 stores the tenant information for each application program of the image forming device. For example, the tenant information 38b is tenant information for the application program 38a.

[0041] FIG. 5 is a diagram showing an example of the tenant information 38b.

[0042] As shown in FIG. 5, the tenant information 38b is information in a table format that includes, for each tenant, a tenant ID and a uniform resource locator (URL) for connecting to the tenant.

[0043] Each tenant ID can be included in only one piece of tenant information.

[0044] The tenant information may be held in an application program associated with the tenant information itself.

[0045] As shown in Fig. 4, the storage unit 38 stores information 38c about users and tenants who have successfully logged in to a tenant from an application program of the image forming device (hereinafter referred to as "successful login information"). The storage unit 38 can store at least one piece of successful login information similar to successful login information 38c other than successful login information 38c. The storage unit 38 stores successful login information for each application program of the image forming device. For example, successful login information 38c is successful login information for application program 38a.

[0046] FIG. 6 is a diagram showing an example of the successful login information 38c.

[0047] As shown in Figure 6, successful login information 38c includes, for each combination of the user ID or ID card information and the tenant ID, the user ID or ID card information used by a user who successfully logged in to a tenant from an application program, the tenant ID of the tenant who successfully logged in from an application program, and the number of successful attempts to log in to the application program.

[0048] From the viewpoint of security, it is preferable that successful login information 38c does not hold the user's password.

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

[0050] The control unit 39 executes the application program to realize a system cooperation unit that cooperates with the device cooperation system 20. For example, the control unit 39 executes the application program 38a to realize a system cooperation unit 39a that cooperates with the device cooperation system 20.

[0051] The image processing device 30 may be installed, for example, in a shared office where multiple companies have access. When the image processing device 30 is installed in a shared office, the administrator of the shared office may be the administrator of the image processing device 30. When the image processing device 30 is installed in a shared office, a user of the shared office may be a user other than the administrator of the image processing device 30.

[0052] Next, the operation of the image processing system 10 will be described.

[0053] A user of the image processing device 30 can instruct the image processing device 30 to start the application program 38a via the operation unit 31. When the start of the application program 38a is instructed, the control unit 39 executes the operations shown in Figs. 7 to 10.

[0054] Fig. 7 is a flowchart of part of the operation of the image processing device 30 when the application program 38a is started. Fig. 8 is a flowchart continuing from the flowchart shown in Fig. 7. Fig. 9 is a flowchart continuing from the flowchart shown in Fig. 7, which is different from the flowchart shown in Fig. 8. Fig. 10 is a flowchart continuing from the flowchart shown in Fig. 9.

[0055] As shown in FIGS. 7 to 10, the system linking unit 39a displays on the display unit 32 a login screen 40 (see FIG. 11) for allowing the user to execute login (S101).

[0056] FIG. 11 is a diagram showing an example of the login screen 40. As shown in FIG.

[0057] As shown in FIG. 11, the login screen 40 includes a combo box 41 for selecting the tenant to connect to, a text box 42 for entering a user ID, a text box 43 for entering a password, and a login button 44 for executing the login.

[0058] It is also possible that no tenant is selected in the combo box 41. The options displayed in the combo box 41 are the tenant IDs shown in the tenant information 38b for the application program 38a, and are displayed in the order shown in the tenant information 38b.

[0059] The login button 44 is grayed out and cannot be operated unless values ​​are entered in both the text box 42 and the text box 43 .

[0060] As shown in FIGS. 7 to 10, when the process of S101 ends, the system cooperation unit 39a judges whether or not the login button 44 has been pressed (S102).

[0061] When the system cooperation unit 39a determines in S102 that the login button 44 has been pressed, it determines whether or not a tenant was selected in the combo box 41 at the time the login button 44 was pressed (S103).

[0062] When the system cooperation unit 39a determines in S103 that a tenant was selected by the combo box 41 at the time when the login button 44 was pressed, the system cooperation unit 39a executes a login process for the tenant selected by the combo box 41 at the time when the login button 44 was pressed (S104). Specifically, the system cooperation unit 39a accesses the device cooperation system 20 by using a URL associated in the tenant information 38b with the tenant ID of the tenant selected by the combo box 41 at the time when the login button 44 was pressed (hereinafter referred to as the "selected tenant ID"), and then transmits to the device cooperation system 20 a login request including a combination of the application ID of the application program 38a, the selected tenant ID, the user ID input in the text box 42 at the time when the login button 44 was pressed (hereinafter referred to as the "input user ID"), and the password input in the text box 43 at the time when the login button 44 was pressed.

[0063] FIG. 12 is a flowchart showing the operation of the device link system 20 when a login request is received from the image processing device 30. As shown in FIG.

[0064] When the device cooperation unit 25a of the device cooperation system 20 receives a login request from the image processing device 30, the device cooperation unit 25a executes the operation shown in FIG.

[0065] As shown in FIG. 12, the device cooperation unit 25a determines whether or not the login request received from the image processing device 30 includes a user ID (S191).

[0066] When the device collaboration unit 25a determines in S191 that the login request received from the image processing device 30 includes a user ID, it determines whether the combination of the user ID and password included in the login request received from the image processing device 30 is included in the application management information 24b in correspondence with the combination of the application ID and tenant ID included in the login request received from the image processing device 30 (S192).

[0067] When the device collaboration unit 25a determines in S191 that the login request received from the image processing device 30 does not include a user ID, it determines whether the ID card information included in the login request received from the image processing device 30 is included in the application management information 24b in correspondence with the combination of the application ID and tenant ID included in the login request received from the image processing device 30 (S193).

[0068] When the device collaboration unit 25a determines in S192 that the combination of the user ID and password included in the login request received from the image processing device 30 is included in the application management information 24b in correspondence with the combination of the application ID and tenant ID included in the login request received from the image processing device 30, or determines in S193 that the ID card information included in the login request received from the image processing device 30 is included in the application management information 24b in correspondence with the combination of the application ID and tenant ID included in the login request received from the image processing device 30, the device collaboration unit 25a notifies the image processing device 30 that the login was successful (S194) and terminates the operation shown in FIG. 12.

[0069] When the device collaboration unit 25a determines in S192 that the combination of the user ID and password included in the login request received from the image processing device 30 is not included in the application management information 24b in correspondence with the combination of the application ID and tenant ID included in the login request received from the image processing device 30, or determines in S193 that the ID card information included in the login request received from the image processing device 30 is not included in the application management information 24b in correspondence with the combination of the application ID and tenant ID included in the login request received from the image processing device 30, the device collaboration unit 25a notifies the image processing device 30 of a login failure (S195) and terminates the operation shown in FIG. 12.

[0070] As shown in FIGS. 7 to 10, when the process of S104 ends, the system cooperation unit 39a determines whether the device cooperation system 20 has notified the system cooperation unit 39a of the success or failure of the login (S105).

[0071] When the system cooperation unit 39a determines in S105 that the successful login has been notified by the device cooperation system 20, it determines whether or not a record including a combination of the input user ID and the selected tenant ID exists in the successful login information 38c (S106).

[0072] When the system cooperation unit 39a determines in S106 that a record including the combination of the input user ID and the selected tenant ID does not exist in the successful login information 38c, the system cooperation unit 39a generates a record including the combination of the input user ID and the selected tenant ID in the successful login information 38c (S107).

[0073] When the process of S107 ends, the system cooperation unit 39a sets the value of the number of successful logins to the application program in the record generated immediately before to 1 (S108).

[0074] When the process of S108 ends, the system cooperation unit 39a displays on the display unit 32 a message indicating that login to the application program 38a has been successful (S109), and ends the operations shown in Figures 7 to 10. Therefore, the logged-in user can use the function of cooperation with the device cooperation system 20 via the application program 38a.

[0075] When the system collaboration unit 39a determines in S106 that a record including the combination of the input user ID and the selected tenant ID exists in the successful login information 38c, it adds 1 to the value of the number of successful logins to the application program in this record (S110) and executes the processing of S109.

[0076] When the system cooperation unit 39a determines in S105 that the login failure has been notified from the device cooperation system 20, it displays on the display unit 32 a message indicating that the login to the application program 38a has failed (S111), and ends the operations shown in Figures 7 to 10. Therefore, the user cannot use the function of cooperation with the device cooperation system 20 via the application program 38a.

[0077] If the system cooperation unit 39a determines in S103 that no tenant was selected in the combo box 41 at the time the login button 44 was pressed, it determines whether or not a record including the input user ID exists in the successful login information 38c (S131).

[0078] When the system collaboration unit 39a determines in S131 that a record including the input user ID exists in the successful login information 38c, it generates successful login tenant information 38d (see Figure 13) by extracting only the tenant ID from the record including the input user ID in the successful login information 38c (S132).

[0079] FIG. 13 is a diagram illustrating an example of the login successful tenant information 38d.

[0080] As shown in FIG. 13, the login successful tenant information 38d includes only the tenant ID.

[0081] As shown in FIGS. 7 to 10, when the process of S132 ends, the system cooperation unit 39a targets the first tenant in the login successful tenant information 38d (S133).

[0082] When the process of S133 ends, the system collaboration unit 39a executes a login process for the current target tenant (S134). Specifically, the system collaboration unit 39a accesses the device collaboration system 20 by using a URL associated with the tenant ID of the current target tenant in the tenant information 38b, and then transmits to the device collaboration system 20 a login request including a combination of the application ID of the application program 38a, the tenant ID of the current target tenant, the input user ID, and the password that was input in the text box 43 at the time when the login button 44 was pressed.

[0083] When the device cooperation unit 25a of the device cooperation system 20 receives a login request from the image processing device 30, the device cooperation unit 25a executes the operation shown in FIG.

[0084] When the process of S134 ends, the system cooperation unit 39a determines whether the device cooperation system 20 has notified the system cooperation unit 39a of the success or failure of the login (S135).

[0085] When the system collaboration unit 39a determines in S135 that the login has been successful that it has been notified by the device collaboration system 20, it adds 1 to the value of the number of successful logins to the application program in the record that includes the combination of the input user ID and the tenant ID of the current target tenant, which is included in the successful login information 38c (S136), and executes the processing of S109.

[0086] When the system collaboration unit 39a determines in S135 that the device collaboration system 20 has notified it of a login failure, it determines whether or not there is a tenant in the successful login tenant information 38d that has not yet been targeted in the current processing of Figures 7 to 10 (S137).

[0087] If the system collaboration unit 39a determines in S137 that there is a tenant in the successful login tenant information 38d that has not yet been targeted in the current processing of Figures 7 to 10, it sets the next tenant after the currently targeted tenant in the successful login tenant information 38d as the new target (S138) and executes the processing of S134.

[0088] If the system collaboration unit 39a determines in S131 that a record including the input user ID does not exist in the successful login information 38c, or determines in S137 that there is no tenant in the successful login tenant information 38d that has not yet been targeted in the current processing of Figures 7 to 10, the system collaboration unit 39a targets the first tenant in the tenant information 38b for the application program 38a (S139).

[0089] When the process of S139 ends, the system collaboration unit 39a executes a login process for the current target tenant (S140). Specifically, the system collaboration unit 39a accesses the device collaboration system 20 by using a URL associated with the tenant ID of the current target tenant in the tenant information 38b, and then transmits to the device collaboration system 20 a login request including a combination of the application ID of the application program 38a, the tenant ID of the current target tenant, the input user ID, and the password that was input in the text box 43 at the time when the login button 44 was pressed.

[0090] When the device cooperation unit 25a of the device cooperation system 20 receives a login request from the image processing device 30, the device cooperation unit 25a executes the operation shown in FIG.

[0091] When the process of S140 ends, the system cooperation unit 39a determines whether the device cooperation system 20 has notified the system cooperation unit 39a of the success or failure of the login (S141).

[0092] When the system collaboration unit 39a determines in S141 that the device collaboration system 20 has notified it that the login is successful, it determines whether or not a record including a combination of the input user ID and the tenant ID of the current target tenant is included in the successful login information 38c (S142).

[0093] If the system collaboration unit 39a determines in S142 that a record including a combination of the input user ID and the tenant ID of the current target tenant is not included in the successful login information 38c, it generates a record including a combination of the input user ID and the tenant ID of the current target tenant in the successful login information 38c (S143) and executes the processing of S108.

[0094] When the system cooperation unit 39a determines in S142 that a record including a combination of the input user ID and the tenant ID of the current target tenant is included in the successful login information 38c, the system cooperation unit 39a executes the process of S136.

[0095] When the system collaboration unit 39a determines in S141 that a login failure has been notified by the device collaboration system 20, it determines whether or not there is a tenant in the tenant information 38b for the application program 38a that has not yet been targeted in the current processing of Figures 7 to 10 (S144).

[0096] If the system collaboration unit 39a determines in S144 that there is a tenant in the tenant information 38b for the application program 38a that has not yet been targeted in the current processing of Figures 7 to 10, it sets the next tenant after the currently targeted tenant in the tenant information 38b for the application program 38a as the new target (S145) and executes the processing of S140.

[0097] When the system cooperation unit 39a determines in S144 that there is no tenant in the tenant information 38b for the application program 38a that has not yet been targeted in the current processing of FIGS. 7 to 10, the system cooperation unit 39a executes the processing of S111.

[0098] If the system cooperation unit 39a determines in S102 that the login button 44 has not been pressed, it determines whether or not the ID card information has been read by the ID card reader 33 (S161).

[0099] If the system cooperation unit 39a determines in S161 that the ID card information has not been read by the ID card reader 33, it executes the process of S102.

[0100] When the system cooperation unit 39a determines in S161 that the ID card information has been read by the ID card reader 33, it determines whether or not a tenant was selected by the combo box 41 at the time the ID card information was read by the ID card reader 33 (S162).

[0101] When the system collaboration unit 39a determines in S162 that a tenant was selected by the combo box 41 at the time when the ID card information was read by the ID card reader 33, it executes a login process for the tenant selected by the combo box 41 at the time when the ID card information was read by the ID card reader 33 (S163). Specifically, the system collaboration unit 39a accesses the device collaboration system 20 by using a URL associated with the selected tenant ID in the tenant information 38b, and then transmits a login request including a combination of the application ID of the application program 38a, the selected tenant ID, and the ID card information read by the ID card reader 33 (hereinafter referred to as "input ID card information") to the device collaboration system 20.

[0102] When the device cooperation unit 25a of the device cooperation system 20 receives a login request from the image processing device 30, the device cooperation unit 25a executes the operation shown in FIG.

[0103] When the process of S163 ends, the system cooperation unit 39a determines whether the device cooperation system 20 has notified the system cooperation unit 39a of the success or failure of the login (S164).

[0104] When the system cooperation unit 39a determines in S164 that the successful login has been notified by the device cooperation system 20, it determines whether or not a record including a combination of the input ID card information and the selected tenant ID exists in the successful login information 38c (S165).

[0105] If the system collaboration unit 39a determines in S165 that a record including the combination of the input ID card information and the selected tenant ID does not exist in the successful login information 38c, it generates a record including the combination of the input ID card information and the selected tenant ID in the successful login information 38c (S166) and executes the processing of S108.

[0106] When the system collaboration unit 39a determines in S165 that a record including a combination of the input ID card information and the selected tenant ID exists in the successful login information 38c, it adds 1 to the value of the number of successful logins to the application program in this record (S167) and executes the processing of S109.

[0107] When the system cooperation unit 39a determines in S164 that the login failure has been notified from the device cooperation system 20, the system cooperation unit 39a executes the process of S111.

[0108] If the system collaboration unit 39a determines in S162 that no tenant was selected using the combo box 41 at the time the ID card information was read by the ID card reader 33, it determines whether or not a record including the input ID card information exists in the successful login information 38c (S168).

[0109] When the system collaboration unit 39a determines in S168 that a record including the input ID card information exists in the successful login information 38c, it generates successful login tenant information 38d (see Figure 13) by extracting only the tenant ID from the record including the input ID card information in the successful login information 38c (S169).

[0110] When the process of S169 ends, the system cooperation unit 39a targets the first tenant in the login success tenant information 38d (S170).

[0111] When the process of S170 ends, the system collaboration unit 39a executes a login process for the current target tenant (S171). Specifically, the system collaboration unit 39a accesses the device collaboration system 20 by using a URL associated with the tenant ID of the current target tenant in the tenant information 38b, and then transmits a login request including a combination of the application ID of the application program 38a, the tenant ID of the current target tenant, and the input ID card information to the device collaboration system 20.

[0112] When the device cooperation unit 25a of the device cooperation system 20 receives a login request from the image processing device 30, the device cooperation unit 25a executes the operation shown in FIG.

[0113] When the process of S171 ends, the system cooperation unit 39a determines whether the device cooperation system 20 has notified the system cooperation unit 39a of the success or failure of the login (S172).

[0114] When the system collaboration unit 39a determines in S172 that the login has been successful from the device collaboration system 20, it adds 1 to the value of the number of successful logins to the application program in the record containing the combination of the input ID card information and the tenant ID of the current target tenant, which is included in the successful login information 38c (S173), and executes the processing of S109.

[0115] When the system collaboration unit 39a determines in S172 that the device collaboration system 20 has notified it of a login failure, it determines whether or not there is a tenant in the successful login tenant information 38d that has not yet been targeted in the current processing of Figures 7 to 10 (S174).

[0116] If the system collaboration unit 39a determines in S174 that there is a tenant in the successful login tenant information 38d that has not yet been targeted in the current processing of Figures 7 to 10, it sets the next tenant after the currently targeted tenant in the successful login tenant information 38d as the new target (S175) and executes the processing of S171.

[0117] If the system collaboration unit 39a determines in S168 that a record including the input ID card information does not exist in the successful login information 38c, or determines in S174 that there is no tenant in the successful login tenant information 38d that has not yet been targeted in the current processing of Figures 7 to 10, the system collaboration unit 39a targets the first tenant in the tenant information 38b for the application program 38a (S176).

[0118] When the process of S176 ends, the system collaboration unit 39a executes a login process for the current target tenant (S177). Specifically, the system collaboration unit 39a accesses the device collaboration system 20 by using a URL associated with the tenant ID of the current target tenant in the tenant information 38b, and then transmits a login request including a combination of the application ID of the application program 38a, the tenant ID of the current target tenant, and the input ID card information to the device collaboration system 20.

[0119] When the device cooperation unit 25a of the device cooperation system 20 receives a login request from the image processing device 30, the device cooperation unit 25a executes the operation shown in FIG.

[0120] When the process of S177 ends, the system cooperation unit 39a determines whether the device cooperation system 20 has notified the system cooperation unit 39a of the success or failure of the login (S178).

[0121] When the system collaboration unit 39a determines in S178 that the login has been successful and has been notified by the device collaboration system 20, it determines whether a record including a combination of the input ID card information and the tenant ID of the current target tenant exists in the successful login information 38c (S179).

[0122] If the system collaboration unit 39a determines in S179 that a record including a combination of the input ID card information and the tenant ID of the current target tenant does not exist in the successful login information 38c, it generates a record including a combination of the input ID card information and the tenant ID of the current target tenant in the successful login information 38c (S180) and executes the processing of S108.

[0123] When the system cooperation unit 39a determines in S179 that a record including a combination of the input ID card information and the tenant ID of the current target tenant exists in the successful login information 38c, the system cooperation unit 39a executes the process of S173.

[0124] When the system collaboration unit 39a determines in S178 that the device collaboration system 20 has notified it of a login failure, it determines whether or not there is a tenant in the tenant information 38b for the application program 38a that has not yet been targeted in the current processing of Figures 7 to 10 (S181).

[0125] If the system collaboration unit 39a determines in S181 that there is a tenant in the tenant information 38b for the application program 38a that has not yet been targeted in the current processing of Figures 7 to 10, it sets the next tenant after the currently targeted tenant in the tenant information 38b for the application program 38a as the new target (S182) and executes the processing of S177.

[0126] When the system cooperation unit 39a determines in S181 that there is no tenant in the tenant information 38b for the application program 38a that has not yet been targeted in the current processing of FIGS. 7 to 10, the system cooperation unit 39a executes the processing of S111.

[0127] The above describes the operation of the image processing device 30 when the application program 38a is started. However, the operation of the image processing device 30 when an application program other than the application program 38a is started is also similar.

[0128] As described above, when the user successfully logs in to a tenant (S105, S141, S164 or S178: "Success"), the image processing device 30 associates the user ID or ID card information of the user with the tenant ID of the tenant and includes them in the successful login information 38c (S107, S143, S166 or S180). When the tenant to which the user logs in is not specified (NO in S103 or S162) and a login is instructed by the user (YES in S102 or S161), and the user ID or ID card information of the user is not included in the successful login information 38c (NO in S131 or S168), the image processing device 30 searches for each of the multiple tenants until the login is successful. The login process is executed in order ("S139 to S141 and S144 to S145" or "S176 to S178 and S181 to S182"), and when a login by a user is instructed (YES in S102 or S161) without specifying a tenant to log in to (NO in S103 or S162), if the user ID or ID card information of this user is included in the successful login information 38c (YES in S131 or S168), the login process is executed for the tenant associated with the user ID or ID card information of this user in the successful login information 38c ("S132 to S135 and S137 to S138" or "S169 to S172 and S174 to S175"). With this configuration, when a user is instructed to log in without specifying a tenant to log in to, if the user has previously successfully logged in to a tenant, the image processing device 30 executes the login process for the tenant to which the user has previously successfully logged in. This reduces the time required for successful login when a tenant to log in to is not specified.

[0129] In the above, in the process of S166, the system cooperation unit 39a generates a record including a combination of the ID card information and the tenant ID separately from a record including a combination of the user ID and the tenant ID. However, the system cooperation unit 39a may generate a record including a combination of the ID card information and the tenant ID together with a record including a combination of the user ID and the tenant ID.

[0130] FIG. 14 is a diagram showing an example of successful login information 38c in a case where a record including a combination of ID card information and a tenant ID and a record including a combination of a user ID and a tenant ID are generated together.

[0131] In successful login information 38c shown in Fig. 6, a record including a user ID "U001001001" and a record including ID card information "C0123456789" exist separately. Here, the user ID "U001001001" and the ID card information "C0123456789" are information of the same user, as shown in Fig. 3. In successful login information 38c shown in Fig. 14, a record including a user ID "U001001001" and a record including ID card information "C0123456789" exist as the same record.

[0132] When the system collaboration unit 39a generates a record including a combination of ID card information and a tenant ID together with a record including a combination of a user ID and a tenant ID, the system collaboration unit 39a may execute the processes of S201 to S203 shown in FIG. 15 instead of the process of S166.

[0133] FIG. 15 is a flowchart showing a modification of part of the operations shown in FIGS.

[0134] As a premise for the operation shown in FIG. 15, when the device collaboration unit 25a of the device collaboration system 20 determines in S193 that the ID card information included in the login request received from the image processing device 30 is included in the app management information 24b in correspondence with the combination of the app ID and tenant ID included in the login request received from the image processing device 30, when notifying the image processing device 30 of the success of the login in S194, the device collaboration unit 25a includes in the notification of the success of the login the user ID that is associated in the app management information 24b with the combination of the app ID, tenant ID and ID card information included in the login request received from the image processing device 30.

[0135] As shown in FIG. 15, when the system collaboration unit 39a determines in S165 that a record including a combination of the input ID card information and the selected tenant ID does not exist in the successful login information 38c, it determines whether a record including a combination of the user ID included in the notification of successful login from the device collaboration system 20 (hereinafter referred to as the "notified user ID") and the selected tenant ID exists in the successful login information 38c (S201).

[0136] When the system cooperation unit 39a determines in S201 that a record including a combination of the notified user ID and the selected tenant ID exists in the successful login information 38c, it adds the input ID card information to this record (S202) and executes the process of S167.

[0137] If the system collaboration unit 39a determines in S201 that a record including the combination of the notified user ID and the selected tenant ID does not exist in the successful login information 38c, it generates a record including the combination of the notified user ID, the input ID card information, and the selected tenant ID in the successful login information 38c (S203) and executes the processing of S108.

[0138] Although the process of S166 has been described above, the process of S180 is similar.

[0139] In the above, in the processes of S139 to S145, the system cooperation unit 39a executes the login process for the tenants in the tenant information 38b in the order in which the tenants are arranged in the tenant information 38b. However, the system cooperation unit 39a may execute the login process for the tenants in the tenant information 38b in the order in which the number of users associated with the tenants is large. For example, the system cooperation unit 39a may execute the processes of S231 to S235 shown in FIG. 16 instead of the processes of S139, S144, and S145.

[0140] FIG. 16 is a flowchart showing a partial modification of the operations shown in FIGS. 7 to 10, which differs from the portion shown in FIG.

[0141] As shown in Fig. 16, when the system cooperation unit 39a determines in S131 that a record including the input user ID does not exist in the successful login information 38c, or determines in S137 that there is no tenant in the successful login tenant information 38d that has not yet been targeted in the current processing of Figs. 7 to 10, the system cooperation unit 39a generates tenant information for login processing 38e (see Fig. 17) indicating the execution order of the login processing based on the tenant information 38b for the application program 38a (S231). Specifically, the system cooperation unit 39a generates tenant information for login processing 38e by copying the tenant IDs of the tenant information 38b without changing the order in the tenant information 38b.

[0142] FIG. 17 is a diagram showing an example of the login process tenant information 38e.

[0143] As shown in FIG. 17, the login processing tenant information 38e includes only the tenant ID.

[0144] As shown in FIG. 16, when the process of S231 ends, the system cooperation unit 39a rearranges the tenants in the login process tenant information 38e in descending order of the number of records in the successful login information 38c (S232).

[0145] When the process of S232 ends, the system cooperation unit 39a targets the first tenant in the login process tenant information 38e (S233).

[0146] When the process of S233 ends, the system cooperation unit 39a executes a login process for the currently targeted tenant (S140).

[0147] When the device cooperation unit 25a of the device cooperation system 20 receives a login request from the image processing device 30, the device cooperation unit 25a executes the operation shown in FIG.

[0148] When the process of S140 ends, the system cooperation unit 39a determines whether the device cooperation system 20 has notified the system cooperation unit 39a of the success or failure of the login (S141).

[0149] When the system cooperation unit 39a determines in S141 that the failure of the login has been notified from the device cooperation system 20, the system cooperation unit 39a determines whether or not there is a tenant that has not yet been targeted in the login processing tenant information 38e (S234).

[0150] If the system collaboration unit 39a determines in S234 that there is a tenant that has not yet been targeted in the tenant information 38e for login processing, it sets the next tenant after the currently targeted tenant in the tenant information 38e for login processing as the new target (S235) and executes the processing of S140.

[0151] When the system cooperation unit 39a determines in S234 that there is no tenant that has not yet been targeted in the login processing tenant information 38e, the system cooperation unit 39a executes the process of S111.

[0152] When a login by a user is instructed (YES in S102) without specifying a destination tenant (NO in S103) and the user ID of the user is not included in successful login information 38c (NO in S131), the image processing device 30 executes login processing for each of a plurality of tenants in descending order of the number of users associated in successful login information 38c (S231 to S233, S140 to S141, and S234 to S235) until login is successful, so that login processing can be preferentially executed for a tenant in which the user is likely to be registered. Therefore, the image processing device 30 can reduce the time required for successful login when a destination tenant is not specified.

[0153] Although the processing of S139 to S145 has been described above, the same applies to the processing of S176 to S182.

[0154] In the above, in the processes of S132 to S138, the system cooperation unit 39a executes the login process for the tenants in the login successful tenant information 38d in the order of the tenants in the login successful tenant information 38d. Therefore, the system cooperation unit 39a may arrange the tenants in the login successful tenant information 38d in the order of the number of past logins. For example, the system cooperation unit 39a may execute the processes of S261 to S262 shown in FIG. 18 between the process of S132 and the process of S133.

[0155] FIG. 18 is a flow chart showing a modification of a part of the operations shown in FIGS. 7 to 10 that is different from the parts shown in FIGS.

[0156] As shown in FIG. 18, when the processing of S132 is completed, the system collaboration unit 39a obtains, for each tenant ID, the number of successful logins to an application program that is associated in the successful login information 38c with the combination of the tenant ID of the tenant in the successful login tenant information 38d and the input user ID (S261).

[0157] When the process of S261 ends, the system cooperation unit 39a rearranges the order of the tenants in the login successful tenant information 38d in descending order of the number of times acquired in S261 (S262).

[0158] When the process of S262 ends, the system cooperation unit 39a targets the first tenant in the tenant information 38b (S133).

[0159] When the user has successfully logged in to a tenant ("Success" in S105, S135, S141, S164, S172 or S178), the image processing device 30 associates the user ID of the user, the tenant ID of the tenant, and the number of times the user has successfully logged in to the tenant with each other, and includes them in the successful login information 38c ("S107 to S108", S110, S136, S143, S166, S167, S173 or S180). When the user has not specified a tenant to log in to (NO in S103) and is instructed to log in ("Success"), the image processing device 30 includes the user ID of the user, the tenant ID of the tenant, and the number of times the user has successfully logged in to the tenant, in the successful login information 38c ("S107 to S108", S110, S136, S143, S166, S167, S173 or S180). When the user ID of this user is associated with the tenant IDs of multiple tenants and included in successful login information 38c (YES in S131), login processing is performed for each of the multiple tenants associated with the user ID of this user in successful login information 38c in descending order of the number of times associated in successful login information 38c (S132, S261 to S262, S133 to S135, and S137 to S138), so that login processing can be preferentially performed for tenants with a high frequency of logins. Therefore, the image processing device 30 can reduce the time required for successful login when a tenant to which the login is to be made is not specified.

[0160] Although the processing of S132 to S138 has been described above, the same applies to the processing of S169 to S175.

[0161] In the above, the system collaboration unit 39a displays the tenant IDs displayed as options in the combo box 41 on the login screen 40 in the order shown in the tenant information 38b. However, the system collaboration unit 39a may arrange the tenant IDs displayed as options in the combo box 41 on the login screen 40 in descending order of the number of past logins. For example, the system collaboration unit 39a may execute the operation shown in FIG.

[0162] FIG. 19 is a flowchart showing the operation of the image processing device 30 when changing the order of tenant IDs displayed as options in the combo box 41 on the login screen 40. As shown in FIG.

[0163] While the login screen 40 is displayed on the display unit 32, the system cooperation unit 39a executes the operation shown in FIG.

[0164] As shown in FIG. 19, the system cooperation unit 39a judges whether the user ID in the text box 42 has been changed or not until it is determined that the user ID in the text box 42 has been changed (S301).

[0165] When the system collaboration unit 39a determines in S301 that the user ID in the text box 42 has been changed, it determines whether or not a tenant ID associated with the user ID entered in the text box 42 exists in the successful login information 38c (S302).

[0166] If the system collaboration unit 39a determines in S302 that there is no tenant ID associated with the user ID entered in the text box 42 in the successful login information 38c, it displays the tenant IDs shown in the tenant information 38b as options in the combo box 41 in the order shown in the tenant information 38b (S303), and executes the processing of S301.

[0167] When the system cooperation unit 39a determines in S302 that there is a tenant ID associated in the successful login information 38c with the user ID input in the text box 42, the system cooperation unit 39a generates tenant information for options indicating the order of the tenant IDs displayed as options in the combo box 41 based on the tenant information 38b (S304). Specifically, the system cooperation unit 39a generates the tenant information for options by copying the tenant IDs in the tenant information 38b without changing the order in the tenant information 38b.

[0168] When the processing of S304 is completed, the system collaboration unit 39a obtains, for each tenant ID, the number of successful logins to the application program that are associated with the user ID entered in the text box 42 in the successful login information 38c (S305).

[0169] When the process of S305 ends, the system cooperation unit 39a rearranges the tenants in the option tenant information in descending order of the number of times acquired in S305 (S306).

[0170] When the processing of S306 is completed, the system collaboration unit 39a displays the tenant IDs indicated in the tenant information for options as options in the combo box 41 in the order indicated in the tenant information for options (S307), and executes the processing of S301.

[0171] When the user has successfully logged in to a tenant ("Success" in S105, S135, S141, S164, S172 or S178), the image processing device 30 includes the user ID or ID card information of the user, the tenant ID of the tenant, and the number of successful login attempts by the user to the tenant in association with each other in the successful login information 38c ("S107 to S108", S110, S136, S143, S166, S167, S173 or S180), and the tenant to which the login is to be made is When a user is designated (YES in S103 or S162) and instructed to log in (YES in S102 or S161), the tenants are arranged in order of the number of times that the user ID or ID card information of the user and the tenant ID of the tenant are associated in successful login information 38c (S304 to S306) and displayed as options for specifying a login destination (S307), so that tenants with a high login frequency can be preferentially displayed at the top as options for specifying a login destination. Therefore, the image processing device 30 can improve convenience.

[0172] In the above, the login screen 40 includes a combo box 41 for selecting a destination tenant. However, the login screen 40 may include a widget other than a combo box as a widget for selecting a destination tenant. For example, the login screen 40 may include a list box or a drop-down list as a widget for selecting a destination tenant. Regardless of which widget is included as a widget for selecting a destination tenant, the login screen 40 needs to be configured to allow the user to not select a destination tenant. [Explanation of symbols]

[0173] 10 Image processing system (information processing system) 20 Device linkage system (tenant-provided system) 30 Image processing device (electronic device) 38a Application program (login program) 38c Successful login information (specific information)

Claims

1. When a user successfully logs in to a tenant provided by a tenant providing system that provides a plurality of tenants, identification information of the user who successfully logs in to the tenant is associated with identification information of the tenant to which the user successfully logs in and included in specific information; When a login is instructed by a user without specifying the tenant as a login destination, and when identification information of the user to be logged in is not included in the specific information, a login process is executed for each of the plurality of tenants in order until the login is successful; An electronic device characterized in that, when a user is instructed to log in without specifying the tenant to which the login is to be made, and when identification information of the user to be logged in is included in the specific information, a login process is performed for the tenant that is associated in the specific information with the identification information of the user to be logged in.

2. The electronic device according to claim 1, characterized in that when a user is instructed to log in without specifying the tenant to which the login is to be made, and identification information of the user to be logged in is not included in the specific information, the electronic device executes a login process for each of the multiple tenants in order of the number of users associated with the specific information, until the login is successful.

3. when the user successfully logs in to the tenant, identification information of the user who successfully logs in to the tenant, identification information of the tenant to which the user successfully logs in, and the number of times the user successfully logs in to the tenant are included in the specific information in association with each other; The electronic device according to claim 1, characterized in that when a user is instructed to log in without specifying the tenant to which the login is to be made, and identification information of the user to be logged in is associated with identification information of multiple tenants and included in the specific information, a login process is performed for each of the multiple tenants associated in the specific information with the identification information of the user to be logged in, in order of the number of times associated in the specific information.

4. when the user successfully logs in to the tenant, identification information of the user who successfully logs in to the tenant, identification information of the tenant to which the user successfully logs in, and the number of times the user successfully logs in to the tenant are included in the specific information in association with each other; The electronic device according to claim 1, characterized in that, when the tenant to which the login is to be made is specified and a login is instructed by a user, the tenants are arranged in order of the number of times that the identification information of the user to be logged in and the identification information of the tenant are associated in the specific information, and are displayed as options for specifying the login destination.

5. an operation of, when a user successfully logs in to a tenant provided by a tenant providing system that provides a plurality of tenants, associating identification information of the user who has successfully logged in to the tenant with identification information of the tenant to which the user has successfully logged in, and including the associated identification information in specific information; an operation of executing a login process for each of the plurality of tenants in order until the login is successful when a login is instructed by a user without specifying the tenant as a login destination and when identification information of the user to be logged in is not included in the specific information; When a login by a user is instructed without specifying the tenant as a login destination, and when identification information of a user who is a target of the login is included in the specific information, an operation of executing a login process for the tenant that is associated with the identification information of the user who is a target of the login in the specific information; A login program that causes an electronic device to realize the above.

6. Electronic devices, A tenant provision system that provides multiple tenants; Equipped with The electronic device includes: when a user successfully logs in to the tenant provided by the tenant providing system, identifying information of the user who successfully logs in to the tenant is associated with identifying information of the tenant to which the user successfully logs in and included in specific information; When a login is instructed by a user without specifying the tenant as a login destination, and when identification information of the user to be logged in is not included in the specific information, a login process is executed for each of the plurality of tenants in order until the login is successful; An information processing system characterized in that, when a user is instructed to log in without specifying the tenant to which the login is to be made, and when identification information of the user to be logged in is included in the specific information, a login process is performed for the tenant that is associated in the specific information with the identification information of the user to be logged in.

Images