Scanner for displaying an authentication screen when authentication failed

A scanner may register one or more profile information to a memory, in a case where an operation for selecting specific profile information from among the one or more profile information registered to the memory is performed, send a first authentication request including first authentication information included in the specific profile information to the server, in a case where an authentication by the first authentication information fails in response to sending the first authentication request to the server, display an authentication information input screen, in a case where second authentication information is inputted in the authentication information input screen, send a second authentication request including the second authentication information to the server, and in a case where an authentication by the second authentication information is successful in response to sending the second authentication request to the server, send scan data to the server.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority to Japanese Patent Application No. 2018-196925 filed on Oct. 18, 2018, the contents of which are hereby incorporated by reference into the present application.

TECHNICAL FIELD

The disclosure herein discloses a technique related to a scanner configured to send scan data to a server.

DESCRIPTION OF RELATED ART

An MFP (abbreviation for Multifunction Peripheral) is known that is capable of sending image data with a folder in a file server set as a destination. Destination information indicating the destination of the image data is registered in the MFP. The destination information includes a folder path and authentication information (user name and password). In a case where the registered destination information is designated, the MFP accesses the folder by using the designated destination information, and sends, to the file server, image data obtained by reading an image on a document.

SUMMARY

In the above technique, there is no assumption that access to the server by using the registered destination information will fail. The present teachings provide a technique that is capable of storing scan data in a server even if access to the server by using profile information selected by a user fails.

A scanner disclosed herein may comprise: a scan executing unit; a processor; and a storage storing computer-readable instructions, wherein the computer-readable instructions, when executed by the processor, cause the scanner to: register one or more profile information to a memory, each of the one or more profile information including authentication information for a server capable of communicating with the scanner to authenticate a user; cause the scan executing unit to scan a document; in a case where an operation for selecting specific profile information from among the one or more profile information registered to the memory is performed on an operation unit, send a first authentication request including first authentication information included in the specific profile information to the server; in a case where an authentication by the first authentication information fails in response to sending the first authentication request to the server, cause a display unit to display an authentication information input screen for inputting authentication information different from the first authentication information; in a case where second authentication information is inputted in the authentication information input screen, send a second authentication request including the second authentication information to the server; and in a case where an authentication by the second authentication information is successful in response to sending the second authentication request to the server, send scan data obtained by the scan executing unit scanning the document to the server so as to store the scan data in the server.

Moreover, a scanner further disclosed herein may comprise: a scan executing unit; a processor; and a storage storing computer-readable instructions, wherein the computer-readable instructions, when executed by the processor, cause the scanner to: register one or more profile information to a memory, each of the one or more profile information including folder information indicating a folder in a server capable of communicating with the scanner; cause the scan executing unit to scan a document; in a case where an operation for selecting specific profile information from among the one or more profile information registered to the memory is performed on an operation unit, send a first access request including first folder information included in the specific profile information to the server; in a case where an access to a first folder indicated by the first folder information fails in response to sending the first access request to the server, cause a display unit to display a folder information input screen for inputting folder information different from the first folder information; in a case where second folder information is inputted in the folder information input screen, send a second access request including the second folder information to the server; and in a case where an access to a second folder indicated by the second folder information is successful in response to sending the second access request to the server, send scan data obtained by the scan executing unit scanning the document to the server so as to store the scan data in the second folder.

A computer program for implementing the above scanner and a non-transitory computer-readable medium storing the computer program for the scanner are also novel and useful. Moreover, a method carried out by scanner is also novel and useful.

EMBODIMENTS

As shown inFIG. 1, a communication system2comprises a scanner10, a server100, and a terminal device200. The devices10,100,200belong to a same LAN (abbreviation for Local Area Network)4, and are capable of mutual communication via the LAN4. The terminal device200is a portable terminal device such as a desktop PC (abbreviation for Personal Computer), laptop PC, tablet PC, or the like.

The scanner10is a peripheral device capable of executing a scan function (that is, a peripheral device of the terminal device200, etc.). The scanner10comprises a display unit12, an operation unit14, a network interface16, a scan executing unit18, and a controller20. The display unit12is a display for displaying various information. The display unit12may function as a so-called touch panel (that is, operation unit). The operation unit14comprises a plurality of keys. A user can input various instructions to the scanner10by operating the operation unit14. The scan executing unit18comprises scan mechanism such as a CCD (abbreviation for Charge Coupled Device) image sensor, CIS (Contact Image Sensor), etc. Hereinbelow, interface is termed “I/F”.

The network I/F16is an I/F for executing wired communication, and is connected with the LAN4. In a variant, the network I/F16may be an I/F for executing wireless communication and, in this case, the LAN4is a so-called wireless LAN.

The controller20comprises a CPU22and a memory24. The CPU22executes various processes in accordance with a program30stored in the memory24. The memory24is configured by a volatile memory, a non-volatile memory, or the like. Further, the memory24stores a profile table32.

The profile table32is a table for storing a plurality of items of profile information. The profile information indicates a profile for storing, in the server100, scan data obtained by executing the scan function. The profile information includes a profile name, scan setting information for executing the scan function (e.g., data format, resolution, number of colors), a folder path indicating a folder in the server100, and authentication information (that is, user name and password) for authenticating the user of the server100. The profile information is registered in the profile table32by the user of the scanner10.

For each of the plurality of items of profile information, the profile table32stores the profile information and a success flag in association with one another. The success flag indicates one of following values: “ON”, indicating that there is a history of successful access to the server by using the corresponding profile information, and “OFF”, indicating that there is no history of successful access to the server by using the corresponding profile information. Access to the server by using the profile information being successful means that authentication of the user by using the authentication information in the profile information succeeds, and also that access to the folder included in the folder path in the profile information succeeds.

The server100is a server for storing scan data received from the scanner10. In a case where scan data is received from the scanner10, the server100executes authentication of the user, and determination of whether the user has authority to access the folder. The server100stores a user table132used for authentication of the user, and an authority table134used for determination of whether the user has the authority to access.

The user table132is a table for registering authentication information. The authentication information includes user name(s) (e.g. “user1”), and password(s) (e.g. “xxxx”). The authentication information is registered in the user table132by an administrator of the server100. The password may be changed after registration by the administrator or the user of the scanner10.

The authority table134is a table for registering user name(s) of user(s) having authority to access a folder in the server100. For each of a plurality of folders in the server100, the authority table134stores a folder name of that folder (e.g. “folder1”), and a list of user name(s) of the user(s) having authority to access that folder (e.g. “user1, user2”) in association with one another. The folder name is registered in the authority table134when the corresponding folder is created. The list of user name(s) is registered in the authority table134by the administrator of the server100. The list of user name(s) in the authority table134may be changed after registration by the administrator.

A process for registering the profile information in the profile table32in the scanner10will be described with reference toFIG. 2.

In T10, a predetermined operation for accessing the scanner10is executed on the terminal device200by the user. The predetermined operation includes, for example, a login operation for logging into the scanner10by authenticating the user who has authority to register the profile information. Upon receiving the predetermined operation in T10, the terminal device200sends a registration screen request to the scanner10in T12. The registration screen request is a command requesting registration screen data representing a registration screen for registering the profile information.

Upon receiving the registration screen request from the terminal device200in T12, the scanner10sends the registration screen data to the terminal device200in T14.

Upon receiving the registration screen data from the scanner10in T14, the terminal device200displays a registration screen SC1represented by the registration screen data in T16. The registration screen SC1includes an input field for inputting the profile information including the profile name, the scan setting information, the folder path, and the authentication information (that is, the user name and the password).

In T18, the user inputs, to the input field in the registration screen SC1, profile information PI1including a profile name “profile1”, scan setting information (e.g. data format “PDF”, resolution “200 dpi”), a folder path “server1/folder1”, and authentication information (i.e. user name “user1” and password “xxxx”). The folder path “server1/folder1” is configured by a host name “server1” of the server100, and a folder name “folder1”.

Upon receiving the input of the profile information PI1in T18, the terminal device200displays an instruction screen SC2in T20. For example, the registration screen SC1includes a registration button (not shown). Then, in a case where the registration button is selected by the user after the input of the profile information PI1, the terminal device200displays the instruction screen SC2. The instruction screen SC2is a screen for instructing on whether the scanner10is to test access to the server by using the authentication information and the folder path in the inputted profile. The instruction screen SC2includes a YES button for receiving an instruction to test access to the server, and a NO button for receiving an instruction not to test access to the server.

In case A1, the user selects the YES button in the instruction screen SC2in T22. Thereby, in T24the terminal device200sends, to the scanner10, a test request for causing the scanner10to test access to the server, and the profile information PI1inputted in the registration screen SC1.

Upon receiving the test request and the profile information PI1from the terminal device200in T24, the scanner10sends in T26, to the server100, an authentication request including the authentication information (that is, the user name “user1” and the password “xxxx”) included in the profile information PI1. The authentication request is a request for causing the server100to execute authentication of the user by using the authentication information. The authentication is, for example, basic authentication, digest authentication, Kerberos authentication, or the like.

Upon receiving the authentication request from the scanner10in T26, the server100executes authentication of the user in T28by using the user name “user1” and the password “xxxx” included in the authentication request. Specifically, the server100specifies, from the user table132, the password associated with the user name “user1” included in the authentication request. Then, the server100determines whether the specified password is identical to the password “xxxx” included in the authentication request. In the present case, the server100determines that the specified password “xxxx” is identical to the password “xxxx” included in the authentication request. As a result, in T28the server100determines that authentication of the user has been successful. In T30, the server100sends, to the scanner10, an authentication success notification for notifying that authentication of the user has been successful. In a case where it is determined that the specified password is not identical to the password “xxxx” included in the authentication request, the server100determines that the authentication of the user has failed. In this case, the server100sends, to the scanner10, an authentication fail notification for notifying that the authentication of the user has failed. The authentication fail notification does not include information indicating a cause why the user authentication has failed (e.g. information indicating that the user name in the authentication request is not included in the user table132, information indicating that the specified password is not identical to the password included in the authentication request).

Upon receiving the authentication success notification from the server100in T30, the scanner10sends in T32, to the server100, an access request including the folder path “server1/folder1” included in the profile information PI1. The access request is a request for causing the server100to determine whether the user has the authority to access the folder indicated by the folder path.

Upon receiving the access request from the scanner10in T32, the server100determines in T34whether the user has the authority to access the folder indicated by the folder path. Specifically, the server100specifies, from the authority table134, a list of user name(s) associated with the folder name included in the folder path. Then, the server100determines whether the user name “user1” included in the profile information PI1is included in the specified list. In the present case, the server100determines that the user name “user1” included in the profile information PI1is included in the specified list. As a result, in T34the server100determines that access to the folder “folder1” has been successful. In T36, the server100sends, to the scanner10, an access success notification for notifying the scanner10that access to the folder “folder1” has been successful. In a case where it is determined that the user name “user1” included in the profile information PI1is not included in the specified list, the server100determines that access to the folder “folder1” has failed. In this case, the server100sends, to the scanner10, an access fail notification for notifying the scanner10that access to the folder “folder1” has failed.

Upon receiving the access success notification from the server100in T36, the scanner10registers the profile information PI1in the profile table32in T38. Further, the scanner10determines that there is a history of successful access to the server by using the profile information PI1, and stores the success flag “ON” in association with the profile information PI1in the profile table32. In T39, the scanner10sends a result notification to the terminal device200indicating that access to the server by using the profile information PI1has been successful. Contrary to this, in a case where the authentication fail notification or the access fail notification is received from the server100, the scanner10sends, to the terminal device200, a result notification indicating that access to the server by using the profile information PI1has failed without registering the profile information PI1.

Further, in case A2, the user selects the NO button in the instruction screen SC2in T42. Thereby, the terminal device200sends the profile information PI1inputted in the registration screen SC1to the scanner10in T44. It should be noted that, in the present case, the terminal device200does not send a test request to the scanner10.

Upon receiving the profile information PI1from the terminal device200in T44, the scanner10registers the profile information PI1in the profile table32in T48. In the present case, due to the test request not being received from the terminal device200, T26to T36of case A1are not executed. As a result, the scanner10determines that there is no history of successful access to the server by using the profile information PI1, and stores the success flag “OFF” in the profile table32in association with the profile information PI1.

Further, it is also possible to change the profile information registered in the profile table32of the scanner10by operating the terminal device200as inFIG. 2. For example, upon receiving a predetermined operation, the terminal device200sends a profile list request to the scanner10, and receives, from the scanner10, a list of profile names of the profile information registered in the profile table32. The terminal device200displays the list of profile names and, when one profile name is selected from the list of profile names, sends a change screen request including the authentication information to the scanner10. The change screen request is a command for requesting authentication of the user by using the authentication information, and for requesting sending of change screen data representing a change screen for changing the profile information corresponding to the selected profile name. In a case where authentication of the user in response to the sending of the change screen request is successful, the terminal device200receives the change screen data from the scanner10, and displays the change screen. The change screen includes a change field for changing respective information in the profile information corresponding to the selected profile name. For example, in a case where new authentication information is inputted to the change field in the change screen, the terminal device200sends the inputted new authentication information to the scanner10. Upon receiving the inputted new authentication information from the terminal device200, the scanner10registers the inputted new authentication information in the profile table32instead of the authentication information associated with the selected profile name in the profile table32. Thereby, the authentication information is changed.

Contents of processes executed by the scanner10in a case where the registered profile information is selected will be described with reference toFIG. 3. The scanner10is capable of using various data communication methods (e.g. a method in which scan data is sent to a server, a method in which an e-mail having scan data attached thereto is sent). Upon accepting an operation for executing the scan function, the scanner10causes the display unit12to display a method selection screen SC10for selecting one data communication method from among the various data communication methods. In a case where a To Server button indicating the method of sending the scan data to the server is selected in the method selection screen SC10, the scanner10causes the display unit12to display a profile selection screen SC12for selecting one item of profile information from among the registered profile information. The processes ofFIG. 3are executed with the selection of one item of profile information (hereinbelow termed “specific profile information”) in the profile selection screen SC12as a trigger thereof.

In S10, the CPU22of the scanner10causes the display unit12to display a confirm screen SC14(seeFIG. 6) for causing the user to confirm contents of the specific profile information. The confirm screen SC14includes character strings indicating contents of respective information in the specific profile information (e.g. the profile name, the scan setting information, the folder path, the user name), and a Scan button for receiving an instruction to execute the scan function. It should be noted that the confirm screen SC14is capable of receiving an instruction for changing the scan setting information in the specific profile information.

In S12, the CPU22monitors selection of the Scan button in the confirm screen SC14. In a case where the Scan button in the confirm screen SC14is selected (YES in S12), in S14the CPU22sends an authentication request including the authentication information in the specific profile information to the server100via the network I/F16. Thereby, the server100executes authentication of the user by using the authentication information in the specific profile information (see T26to T30ofFIG. 2).

In S16, the CPU22determines whether authentication of the user by using the authentication information in the specific profile information has been successful. Specifically, the CPU22determines that the authentication of the user has been successful in the case of receiving an authentication success notification from the server100, and determines that the authentication of the user has failed in the case of receiving an authentication fail notification from the server100. In the case of determining that the authentication of the user has been successful (YES in S16), the CPU22executes a first access process in S40. Contents of the first access process will be described later with reference toFIG. 4. When the process of S40ends, the processes ofFIG. 3end.

Further, in the case of determining that the authentication of the user has failed (NO in S16), in S20the CPU22specifies the success flag associated with the specific profile information from the profile table32. Then, the CPU22determines whether the specified success flag indicates “ON”. In case of determining that the specified success flag indicates “OFF” (NO in S20), the CPU22skips S22to S28, described later, and proceeds to S30. On the other hand, in case of determining that the specified success flag indicates “ON” (YES in S20), the CPU22proceeds to S22.

In S22, the CPU22causes the display unit12to display a password input screen SC16(seeFIG. 6). The password input screen SC16is a screen for inputting the password. For example, in a case where the password registered in the user table132of the server100is changed after the specific profile information has been registered in the profile table32of the scanner10, the server100fails to authenticate the user by using the authentication information in the specific profile information. For example, the server100periodically requests the user to change the password in order to prevent a decrease in security. The user changes the password in the user table132of the server100in response to the request from the server100. However, thereafter the user may forget to change the password in the profile table32of the scanner10. In such a situation, the password in the user table132is changed after the registration of the specific profile information, and the authentication of the user by using the authentication information in the specific profile information fails. A changed password different from the password in the specific profile information is inputted in the password input screen SC16. Thereby, it is possible to cause the server100to authenticate the user by using the changed password.

In S24, the CPU22sends an authentication request including the user name in the specific profile information and the password inputted in the password input screen SC16to the server100via the network I/F16. S26is similar to S16. In case of determining that authentication of the user has been successful (YES in S26), the CPU22executes a second access process in S50. Contents of the second access process will be described later with reference toFIG. 5. When the process of S50ends, the processes ofFIG. 3end.

Further, in case of determining that the authentication of the user has failed (NO in S26), in S28the CPU22determines whether an authentication request including the password inputted in the password input screen SC16has been sent a predetermined number of times (e.g. three times) or more. In case of determining that the authentication request including the password inputted in the password input screen SC16has not been sent the predetermined number of times or more (NO in S28), the CPU22returns to S22, and causes the display unit12to display the password input screen SC16again.

Further, in case of determining that the authentication request including the password inputted in the password input screen SC16has been sent the predetermined number of times or more (YES in S28), in S30the CPU22causes the display unit12to display an authentication failure screen SC20(seeFIG. 6). The authentication failure screen SC20is a screen for notifying that authentication by means of the authentication information has failed. The authentication failure screen SC20includes a message for prompting the user to change the authentication information by using the terminal device200. Thereby, the user can operate the terminal device200to change the authentication information in the profile information registered in the profile table32. When S30ends, the processes ofFIG. 3end.

The contents of the first access process will be described with reference toFIG. 4. In S60, the CPU22sends an access request including the folder path in the specific profile information to the server100via the network I/F16. Thereby, the server100determines whether the user has the authority to access the folder indicated by the folder path in the specific profile information (see T32to T36ofFIG. 2).

In S62, the CPU22determines whether access to the folder indicated by the folder path in the specific profile information has been successful. Specifically, the CPU22determines that access to the folder has been successful in the case of receiving an access success notification from the server100, and determines that access to the folder has failed in the case of receiving an access fail notification from the server100. In case of determining that access to the folder has been successful (YES in S62), the CPU22proceeds to S64. In S64, the CPU22causes the scan executing unit18to scan a document, creating scan data. Then, the CPU22sends the created scan data to the server100via the network I/F16with the folder path in the specific profile information as the destination. Thereby, the created scan data is stored in the folder indicated by the folder path in the specific profile information.

In S66, the CPU22causes the display unit12to display a completion screen SC18(seeFIG. 6) indicating that the storage of the scan data is completed. When S66ends, the processes ofFIG. 4end.

Further, in case of determining that access to the folder has failed (NO in S62), the CPU22proceeds to S70. In S70, the CPU22causes the display unit12to display an access failure screen SC22(seeFIG. 6). The access failure screen SC22is a screen for notifying that access to the folder indicated by the folder path has failed. The access failure screen SC22includes a message prompting the user to change the folder path by using the terminal device200. Thereby, the user can operate the terminal device200to change the folder path in the profile information registered in the profile table32. When S70ends, the processes ofFIG. 4end.

The contents of the second access process will be described with reference toFIG. 5. S80to S86, S90are similar to S60to S66, S70ofFIG. 4. In S88, the CPU22changes the password associated with the profile name in the specific profile information in the profile table32to the password inputted in the password input screen SC16. When S88or S90ends, the processes ofFIG. 5end.

Specific cases realized by the processes ofFIG. 3toFIG. 5will be described with reference toFIG. 6. In each case described later, the profile information PI1is selected as the specific profile information.

In case B1, in the processes ofFIG. 2, the NO button in the instruction screen SC2is selected in the case where the profile information PI1is registered (case A2ofFIG. 2). As a result, in the profile table32, the success flag “OFF” is stored in association with the profile information PI1(T48). Further, in the present case, it is assumed that the profile information PI1includes authentication information different from the correct authentication information (that is, the user name “user1”, the password “xxxx”).

In case B1, when the Scan button is selected in the confirm screen SC14, the scanner10sends an authentication request including the authentication information in the profile information PI1to the server100(S14ofFIG. 3). Due to the authentication information in the profile information PI1being different from the correct authentication information, the scanner10determines that the authentication of the user by using the authentication information in the profile information PI1has failed (NO in S16ofFIG. 3). Then, the scanner10determines that the success flag associated with the profile information PI1indicates “OFF” (NO in S20). As a result, the scanner10displays the authentication failure screen SC20. The success flag “OFF” means that there is no history of successful access to the server by using the authentication information in the profile information PI1. Therefore, failure to authenticate the user by using the authentication information in the profile information PI1may mean that not only the password in the authentication information in the profile information PI1, but also the user name is incorrect. In such a case, the scanner10displays the authentication failure screen SC20without displaying an input screen including an input field for inputting the authentication information (that is, the user name, the password). Thereby, the user can be prompted to operate the terminal device200in order to change the authentication information in the profile information PI1.

In case B2, in the processes ofFIG. 2, the YES button in the instruction screen SC2is selected in the case where the profile information PI1is registered (case A1ofFIG. 2). As a result, the success flag “ON” is stored in association with the profile information PI1in the profile table32(T38). Further, in the present case, after the profile information PI1has been registered, the password corresponding to the user name “user1” in the user table132of the server100is changed from the password “xxxx” to a password “zzzz”.

In case B2, due to the password “xxxx” in the profile information PI1being different from the changed password “zzzz”, the scanner10determines that the authentication of the user by using the authentication information in the profile information PI1has failed (NO in S16ofFIG. 3). Then, the scanner10determines that the success flag associated with the profile information PI1indicates “ON” (YES in S20). As a result, the scanner10displays the password input screen SC16(S22ofFIG. 3). Here, the password input screen SC16does not include an input field for inputting the user name but includes a password input field for inputting a password. The success flag “ON” means that there is a history of successful access to the server by using the authentication information in the profile information PI1. Therefore, the failure to authenticate the user by using the authentication information in the profile information PI1means that there is a high possibility that the password in the user table132may have been changed after the registration of the profile information PI1. That is, this means that there is a high possibility that the user name could be correct and the password could be different in the authentication information in the profile information PI1. In the present case, the scanner10can display the password input screen SC16including an appropriate input field that is suitable for the situation in which the password has been changed.

Case B3is a continuation of case B2. In the present case, due to the user inputting an incorrect instruction in the operation unit14of the scanner10, or the like, a password different from the changed password “zzzz” is inputted in the password input screen SC16. As a result, the scanner10determines that the authentication of the user has failed (NO in S26ofFIG. 3). Then, the scanner10again displays the password input screen SC16(S22which went to NO in S28). In the present case, the user twice inputs a password different from the changed password “zzzz” in the password input screen SC16that is displayed again. As a result, the scanner10determines that the authentication of the user has failed, and determines that the authentication request has been sent three times or more, which is the predetermined number of times (YES in S28). Then, the scanner10displays the authentication failure screen SC20. Thereby, the user can be notified of a method of operating the terminal device200which is a method other than operation of the operation unit14in the scanner10, as a method for changing the password in the profile information PI1. For example, when the terminal device200is operated to change the password in the profile information PI1, a login operation for logging in to the scanner10is executed on the terminal device200. Therefore, in the case where the authentication request has been sent the predetermined number of times or more, by notifying the user of a method including the login operation, it is possible to prevent the password in the profile information PI1from being changed by a user who does not have the authority to log in to the scanner10.

Case B4is a continuation of case B2. In the present case, the changed password “zzzz” is inputted in the password input screen SC16. As a result, the scanner10determines that the authentication of the user has been successful (YES in S26ofFIG. 3). The scanner10sends an access request including the folder path “server1/folder1” in the profile information PI1to the server100(S80ofFIG. 5). Due to the user name “user1” in the profile information PI1being stored in association with the folder name “folder1” in the authority table134(seeFIG. 1), the scanner10determines that access to the folder has been successful (YES in S82). As a result, the scanner10sends the scan data to the server100(S84), and displays the completion screen SC18(S86).

In the present case, the scanner10displays the password input screen SC16in the case where an authentication by the profile information PI1fails. Thereby, the user can input the password “zzzz” that is different from the password “xxxx”. For this reason, the scanner10can send an authentication request including the password “zzzz” to the server and, in a case where an authentication by the authentication information including the user name “user1” and the password “zzzz” is successful, the scanner10can store the scan data in the server100.

Further, in the present case, the scanner10displays the password input screen SC16in the case where the authentication by the profile information PI1fails. That is, the user does not need to operate the terminal device200, which is different from the scanner10, in order to change the password in the profile information PI1. Therefore, convenience for the user is improved. In the present embodiment, the user can operate the terminal device200to change the profile information. For example, the keys in the operation unit14of the scanner10are smaller than the keys in the operation unit of the terminal device200and, further, the display unit12of the scanner10is smaller than the display unit of the terminal device200. Therefore, the user finds it more troublesome to operate the scanner10than to operate the terminal device200. For this reason, taking operability for the user into consideration, it is preferable to have the user operate the terminal device200in the case where the authentication by the profile information PI1fails. However, in this case, if the authentication by the profile information PI1fails after the user has operated the scanner10and selected the profile information, the user must shift from the scanner10to the terminal device200, operate the terminal device200to input the password, then again shift from the terminal device200back to the scanner10, and operate the scanner10and select the profile information. Although operability for the user is not reduced, convenience for the user is reduced. By contrast, in the present case, the user does not need to shift between the terminal device200and the scanner10, and therefore convenience for the user is improved.

Further, in the present case, in the case where the authentication by the profile information PI1fails, the scanner10displays the password input screen SC16without displaying a screen for accepting an operation for selecting profile information different from the profile information PI1from among the registered one or more profile information. That is, the user can store the scan data in the server100even without performing an operation for selecting profile information different from the profile information PI1.

In case B5, after the profile information PI1has been registered, the user name “user1” is deleted from the list of user names associated with the folder name “folder1” in the authority table134of the server100. In the present case, the scanner10determines that authentication of the user by using the authentication information in the profile information PI1has been successful (YES in S16ofFIG. 3). The scanner10sends an access request including the folder path “server1/folder1” in the profile information PI1to the server100(S60ofFIG. 4). Since the user name “user1” in the profile information PI1is not being stored in association with the folder name “folder1” in the authority table134, the scanner10determines that access to the folder has failed (NO in S62ofFIG. 4). Then, the scanner10displays the access failure screen SC22. For example, a comparative example is assumed in which, in the case where it is determined that access to the folder has failed, a screen including an input field for inputting a folder path is displayed. As described above, the keys in the operation unit14of the scanner10are smaller than the keys in the operation unit of the terminal device200. Further, in the terminal device200, the user can operate an operation unit such as a mouse, etc. to copy a folder path and input it in the input field. For this reason, in the configuration of the comparative example, the user finds it more troublesome to operate the scanner10than to operate the terminal device200. By contrast, in the present case, the scanner10displays the access failure screen SC22without displaying a screen including an input field. Thereby, the user can be notified, as a method for changing the folder path in the profile information PI1, of a method of operating the terminal device200, which is a method other than operation of the operation unit14in the scanner10. In a variant, the configuration of the comparative example described above may be adopted. Further, as above, at the time of operating the terminal device200to change the password in the profile information PI1, the login operation for logging into the scanner10is performed on the terminal device200. Therefore, in the case where access to the folder has failed, by notifying the user of a method including the login operation, it is possible to prevent the folder path in the profile information PI1from being changed by the user who does not have the authority to login to the scanner10.

The scanner10, the server100, the terminal device200are an example of “a scanner”, “a server”, “a terminal device”, respectively. The display unit12, the operation unit14, the scan executing unit18, the memory24are an example of “a display unit”, “an operation unit”, “a scan executing unit”, “a memory”, respectively. The profile information in the profile table32is an example of “one or more profile information”. The authentication request of S14ofFIG. 3and the authentication request of S24ofFIG. 3are an example of “a first authentication request”, “a second authentication request”, respectively. The password input screen SC16ofFIG. 6and the password input field in the password input screen SC16ofFIG. 6are an example of “an authentication information input screen”, “a password input field”, respectively. Selection of the YES button in the instruction screen SC2in T22ofFIG. 2is an example of “a predetermined instruction”. The success flag “ON” is an example of “predetermined information”. The authentication failure screen SC20displayed in S30which went to NO in S20ofFIG. 3is an example of “a first authentication failure screen”. The authentication failure screen SC20displayed in S30which went to YES in S28ofFIG. 3is an example of “a second authentication failure screen”. The folder path is an example of “folder information”. The access request in S60ofFIG. 4is an example of “a first access request”. The access failure screen SC22ofFIG. 6is an example of “an access failure screen”.

T38or T48ofFIG. 2is an example of “register one or more profile information”. S14, S22, S24ofFIG. 3are an example of “send a first authentication request”, “cause a display unit to display an authentication information input screen”, “send a second authentication request”, respectively. S84ofFIG. 5is an example of “cause the scan executing unit to scan a document and send scan data”.

Second Embodiment

The present embodiment is similar to the first embodiment except for a point that the contents of the first access process and the second access process are different. Hereinbelow, the contents of the first access process and the second access process of the present embodiment will be described.

In the first access process of the present embodiment, in case of determining that access to the folder has failed (NO in S62ofFIG. 4), the CPU22executes an input screen process in S72. When the process of S72ends, the first access process ends. Further, in the second access process of the present embodiment, in case of determining that access to the folder has failed (NO in S82ofFIG. 5), the CPU22executes an input screen process in S92. When the process of S92ends, the second access process ends. Contents of the input screen process will be described later with reference toFIG. 7.

The contents of the input screen process will be described with reference toFIG. 7. In S102, the CPU22causes the display unit12to display a folder input screen SC24. The folder input screen SC24is a screen for inputting a folder path. For example, there may be a case where, after the specific profile information has been registered, the user name in the specific profile information is deleted from the list of user name(s) associated with the folder name in the specific profile information in the authority table134of the server100, or a case where server down is occurring temporarily. In these cases, access to the folder indicated by the folder path in the specific profile information fails. A folder path different from the folder path in the specific profile information can be input in the folder input screen SC24. Thereby, it is possible to cause the server to execute determination as to whether or not the user has the authority to access the folder indicated by the inputted folder path.

S104is similar to S60ofFIG. 4except for a point that the folder path inputted in the folder input screen SC24is included in the access request. S106is similar to S62ofFIG. 4. In case of determining that access to the folder has been successful (YES in S106), the CPU22proceeds to S124, S126. S124, S126are similar to S64, S66ofFIG. 4. When S126ends, the processes ofFIG. 7end.

Further, in case of determining that access to the folder has failed (NO in S106), in S108the CPU22determines whether the access request including the folder path inputted in the folder input screen SC24has been sent a predetermined number of times (e.g. three times) or more. In case of determining that the access request including the folder path inputted in the folder input screen SC24has not been sent the predetermined number of times (NO in S108), the CPU22returns to S102, and causes the display unit12to display the folder input screen SC24again.

Further, in case of determining that the access request including the password inputted in the folder input screen SC24has been sent the predetermined number of times or more (YES in S108), the CPU22proceeds to S110. S110is similar to S70ofFIG. 4. When S110ends, the processes ofFIG. 7end.

According to the present embodiment, in the case where access to the folder indicated by the folder path in the specific profile information fails (S62ofFIG. 4), the scanner10displays the folder input screen SC24(S72ofFIG. 4, S102ofFIG. 7). Thereby, the user can input a folder path different from the folder path in the specific profile information. For this reason, the scanner10can send, to the server100, a folder request including the folder path inputted in the folder input screen SC24and, in a case where access to the folder indicated by the inputted folder path is successful (YES in S106), the scanner10can cause the scan data to be stored in the folder indicated by the inputted folder path (S124).

Further, according to the present embodiment, in case of determining that access to the folder indicated by the inputted folder path has been successful (YES in S106), the scanner10executes the processes of S124, S126, and ends the input screen process. That is, the scanner10ends the input screen process without changing the folder path associated with the profile name in the specific profile information in the profile table32to the folder path inputted in the folder input screen SC24. For example, a comparative example is assumed in which the folder path in the profile table32is changed to the inputted folder path in the case where it is determined that access to the folder indicated by the inputted folder path has been successful. For example, a case is assumed in which specific profile information is selected by a user different from the user indicated by the user name in the specific profile information. In this case, when access to the folder indicated by the folder path in the specific profile information fails, the different user can input a folder path in the folder input screen SC24. As a result, the folder path in the profile table32can be changed to a folder path inputted by the different user. By contrast, in the present embodiment, the folder path in the profile table32is not changed to the inputted folder path. Thereby, it is possible to prevent the folder path in the profile table32from being changed to a folder path inputted by a different user.

The access request of S60ofFIG. 4is an example of “a first access request”. The folder input screen SC24ofFIG. 7is an example of “a folder information input screen”. The access request of S104ofFIG. 7is an example of “a second access request”.

S60ofFIG. 4is an example of “send a first access request”. S102, S104ofFIG. 7are an example of “cause a display unit to display a folder information input screen”, “send a second access request”, respectively. S124ofFIG. 7is an example of “cause the scan executing unit to scan a document and send scan data”.

Specific examples of the present invention are described above in detail, but these examples are merely illustrative and place no limitation on the scope of the patent claims. The technology described in the claims also encompasses various changes and modifications to the specific examples described above. Some of variants of the above embodiments are listed below.

(Variant 1) “A scanner” may not be the scanner10, but may be, for example, a multifunction peripheral capable of executing a scan function.

(Variant 2) “Profile information” may not include the scan setting information. “Profile information” may need to include at least the authentication information.

(Variant 3) The process of S88ofFIG. 5may not be executed. In this variant, “change the first authentication information” may be omitted.

(Variant 4) The profile table32may not store the success flag. In that case, the process of S20ofFIG. 3may not be executed. In this variant, “store predetermined information” may be omitted. Further, in this variant, in S22the scanner10may further display an authentication information input screen including an input field for inputting a user name, and a password input field. Thereby, when the profile information PI1is registered in case A2ofFIG. 2, it is possible to input correct authentication information in a case where the authentication information in the profile information PI1is incorrect. In this variant, “an authentication information input screen” may include an input field for inputting a user name different from the first user name included in the first authentication information.

(Variant 5) The process of S28ofFIG. 3may not be executed. In this variant, “cause the display unit to display the authentication information input screen again”, “send a fourth authentication request”, “cause the display unit to display a second authentication failure screen” may be omitted.

(Variant 6) “Profile information” may not include a folder path. In that case, instead of the processes of S40, S50ofFIG. 3, a process similar to S64ofFIG. 4may be executed. In this variant, “profile information” may not have to include folder information, and “send a first access request”, “cause the display unit to display an access failure screen” may be omitted.

(Variant 7) In the second embodiment, S20to S28, S50ofFIG. 3may not be executed. In this variant, the “scanner” may simply need to comprise “register one or more profile information”, “cause the scan executing unit to scan a document”, “send a first access request”, “cause a display unit to display a folder information input screen”, “send a second access request”, and “send scan data”.

(Variant 8) In the second embodiment, in a case where it is determined that access to the folder indicated by the folder path inputted in the folder input screen SC24has been successful, the scanner10may change the folder path in the profile table32to the inputted folder path.

(Variant 9) “An operation unit”, “a display unit” may be disposed in a terminal device (e.g. the terminal device200) capable of communicating with the scanner10. In this case, for example, the terminal device200accesses the scanner10in response to an operation of the user, and displays a list of profile name(s) in the profile table32. Then, in a case where one profile name in the list of profile name(s) is selected, the terminal device200causes the scanner10to send an authentication request by using the authentication information in the specific profile information corresponding to the selected profile name. Then, in a case where authentication using the authentication information in the specific profile information fails, the terminal device200receives screen data representing a password input screen from the scanner10, and displays the password input screen. In the present case, the user does not need to operate a device other than the terminal device200in the case where authentication using the authentication information in the specific profile information fails. Convenience for a user is improved.

(Variant 10) The processes ofFIG. 2may not be executed. For example, the profile information may be registered in the profile table32by operating the operation unit of the scanner10. In this variant, “receive the specific profile information” may be omitted.

(Variant 11) “A predetermined instruction” is not restricted to selection of the YES button of T22ofFIG. 2, but may be, for example, selection of the profile information PI1in the profile selection screen SC12after case A2ofFIG. 2. In this case, if the access to server by using the profile information PI1is successful (YES in S16ofFIG. 3, YES in S62ofFIG. 4), the scanner10may store the success flag “ON” in the profile table32in association with the profile information PI1.

(Variant 12) In each of the above embodiments, the respective processes ofFIG. 2 to 7are implemented by the CPU22of the scanner10executing the program30(that is, software). Instead of this, one or more of the processes may be implemented by hardware such as a logic circuit.