Image processing device and authentication processing method

The image processing device addresses email transmission interruptions by switching to an alternative OAuth-compatible account when the primary token expires, ensuring continuous email transmission and reducing re-authentication requirements.

JP2024160805APending Publication Date: 2024-11-15SHARP KK
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2023076194
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-02
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

The expiration of OAuth tokens used for email transmission authentication results in the inability to send emails until re-authentication is executed, causing potential delays and failures, especially in automated processes like fax forwarding, and can lead to token exhaustion due to multiple device usage.

Method used

An image processing device that stores an alternative account compatible with OAuth authentication, allowing seamless switching to this account when the primary account's token expires, ensuring continuous email transmission without requiring immediate re-authentication.

Benefits of technology

Enables uninterrupted email transmission by switching to an alternative account when the primary account's token expires, preventing email sending failures and reducing the need for immediate re-authentication, thus maintaining operational continuity and security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024160805000001_ABST
    Figure 2024160805000001_ABST
Patent Text Reader

Abstract

To provide an image processing device and the like capable of avoiding the situation in which mail sending becomes impossible until re-authentication processing is executed for the account due to passing expiration date of a token.SOLUTION: An image processing device comprises a storage part to store an account for a service provision device and a control part to control authentication processing for the service provision device based on the account. The control part stores the new account stores as a second account that is an alternative account of the first account in the storage part when the control part determines that the new account and a first account stored in the storage part correspond to the same authentication system at the time of accepting the new account.SELECTED DRAWING: Figure 2
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to an image processing device and the like. [Background technology]

[0002] Recently, the OAuth authentication method, which is more secure than the conventional authentication method using a user ID and password, is becoming mainstream as an authentication method for sending emails.

[0003] The tokens used for OAuth authentication have an expiration date to ensure security. If the token expires, re-authentication with authorization from the administrator who owns the account is required, and email cannot be sent during that time.

[0004] For example, Patent Document 1 describes a mechanism for prompting a re-authorization process for OAuth authentication when a token's validity period has expired. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2020-170913 A Summary of the Invention [Problem to be solved by the invention]

[0006] The present disclosure aims to provide an image processing device and the like that can avoid a situation in which, due to a token's expiration date, email transmission becomes impossible until a re-authentication process is performed for the account. [Means for solving the problem]

[0007] In order to solve the above problem, the image processing device of the present disclosure includes a memory unit that stores an account for a service providing device, and a control unit that controls authentication processing for the service providing device based on the account, and when the control unit accepts input of a new account, if it determines that the new account and a first account stored in the memory unit correspond to the same authentication method, it stores the new account in the memory unit as a second account that is an alternative account to the first account.

[0008] In addition, the authentication processing method according to the present disclosure is characterized in that an account for a service providing device is stored in a storage device as a first account, and when input of a new account is accepted, if it is determined that the new account and the first account correspond to the same authentication method, the new account is stored in the storage device as a second account that is an alternative account for the first account, and authentication processing for the service providing device is performed based on the account stored in the storage device. Effect of the Invention

[0009] According to the present disclosure, it is possible to provide an image processing device or the like that can avoid a situation in which email transmission becomes impossible due to the expiration of a token until a re-authentication process is performed for the account. [Brief description of the drawings]

[0010] [Figure 1] 2 is a diagram illustrating a connection configuration between a multifunction peripheral, a cloud, and a mail delivery server. [Diagram 2] FIG. 2 is a functional configuration diagram of the multifunction peripheral. [Diagram 3] FIG. 13 is a diagram illustrating an account management table. [Figure 4] 4 is a flowchart illustrating a process flow according to the first embodiment. [Diagram 5] 4 is a sequence illustrating a command flow according to the first embodiment. [Figure 6] 4 is a sequence illustrating a command flow according to the first embodiment. [Figure 7] 4 is a flowchart illustrating a process flow according to the first embodiment. [Figure 8] FIG. 4 is a diagram illustrating an operation example according to the first embodiment. [Figure 9] FIG. 4 is a diagram illustrating an operation example according to the first embodiment. [Figure 10] FIG. 4 is a diagram illustrating an operation example according to the first embodiment. [Figure 11] 10 is a flowchart illustrating a process flow according to the second embodiment. [Figure 12] FIG. 11 is a diagram illustrating an operation example according to the second embodiment. [Figure 13] FIG. 11 is a diagram illustrating an operation example according to the second embodiment. [Figure 14] 13 is a flowchart illustrating a process flow according to the third embodiment. [Figure 15] FIG. 13 is a diagram illustrating an operation example according to the third embodiment. [Figure 16] FIG. 13 is a diagram illustrating an operation example according to the third embodiment. [Figure 17] FIG. 13 is a diagram illustrating an operation example according to the third embodiment. [Figure 18] 13 is a flowchart illustrating a process flow according to the fourth embodiment. [Figure 19] FIG. 13 is a diagram illustrating an account management table. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. Note that the following embodiments are merely examples for explaining the present disclosure, and the technical content of the description described in the claims is not limited to the following description.

[0012] When sending an e-mail from an image processing device, an account set up in advance by an administrator of the image processing device is used to perform authentication processing for e-mail delivery services, authentication services, etc. If the account used is an account that supports the OAuth authentication method, re-authentication processing by the administrator is required if the token expiration date has passed, even if the administrator performed authentication processing at the time of setting.

[0013] In addition, since the re-authentication process is often performed by the account owner (administrator), other users cannot send emails until the re-authentication process is completed. In particular, if an email sending failure occurs when the operation screen of the image processing device is not being operated, such as in the case of automatic forwarding of received faxes, the job may continue to fail for a long time without the failure being recognized.

[0014] Furthermore, in OAuth authentication, there may be a limit on the number of tokens that can be acquired for each account. If an account is used in many devices, the possibility of email transmission failing increases when the number of acquired tokens reaches the upper limit.

[0015] In the present disclosure, the following embodiments provide an image processing device or the like that can avoid a situation in which e-mail transmission becomes impossible due to a token expiration date passing until a re-authentication process is performed for the account.

[0016] [1 First embodiment] [1.1 Overall structure] FIG. 1 is a diagram for explaining an example of a connection configuration between a multifunction peripheral 10 as an image processing device according to the first embodiment, a cloud 30 as a service providing device, and a mail delivery server 50. As shown in FIG.

[0017] The multifunction device 10 according to the first embodiment is an image processing device capable of performing printing, copying, faxing (internet faxing), email transmission, etc. in a single housing. Note that, in the first embodiment, the multifunction device 10 will be described as one form of an image processing device, but there are no particular limitations as long as it is configured to perform authentication processing using an account compatible with OAuth authentication, and the image processing device may be a copier, printer, fax, or other device.

[0018] The multifunction device 10 is connected to the cloud 30 and the mail delivery server 50 via a network NW. The multifunction device 10 is configured to be able to communicate with the cloud 30 and the mail delivery server 50 based on communication protocols such as IP (Internet Protocol), TCP (Transmission Control Protocol), HTTP (Hypertext Transfer Protocol), and SMTP (Simple Mail Transfer Protocol). The network NW represents a network line such as a LAN (Local Area Network), a WAN (Wide Area Network), or the Internet. The number of multifunction devices 10 connected to the network NW is not limited to the example shown in FIG. 1, and multiple multifunction devices 10 may be connected to the network NW.

[0019] The cloud 30 includes an authorization server (not shown) that performs resource usage authorization by implementing, for example, an authorization code flow based on the OAuth2.0 authentication method. The cloud 30 is not limited in device configuration as long as it is configured to generate an authorization code, an access token as authorization information, a refresh token as update request information, etc. in response to authentication (authorization), and for example, the authorization server that processes the authorization code flow and the resource server that provides resources may be configured separately, or it may be configured as a single device that has both an authentication function and a resource providing function.

[0020] The mail delivery server 50 delivers mail in accordance with the SMTP protocol and the POP (Post Office Protocol) protocol. The mail delivery server 50 can send mail to a specific destination and deliver received mail in response to a mail sending request from the cloud 30 (resource server) via an API (Application Programming Interface). The mail delivery server 50 may be configured as a resource server of the cloud 30.

[0021] [1.2 Functional configuration] [1.2.1 About the multifunction device 10] Next, the functional configuration of the multifunction device 10 according to the first embodiment will be described with reference to Fig. 2. The multifunction device 10 includes a control unit 11, a display unit 13, an operation input unit 15, a communication unit 17, an image processing unit 19, an image input unit 21, and a storage unit 23.

[0022] The control unit 11 controls the entire multifunction device 10. The control unit 11 is configured, for example, with one or more arithmetic units (CPUs (Central Processing Units) and the like). The control unit 11 realizes its functions by reading and executing various programs stored in the storage unit 23.

[0023] The display unit 13 displays various information to the user, etc. The display unit 13 can be configured, for example, with an LCD (Liquid Crystal Display), an organic EL (Electro-luminescence) display, etc. Under the control of the control unit 11, the display unit 13 displays a screen based on screen information for viewing generated by a browser program 234 described later.

[0024] The operation input unit 15 accepts information input by a user or the like. The operation input unit 15 can be configured with various input devices such as operation keys such as hard keys and software keys, and buttons. The operation input unit 15 can be configured as a touch panel that allows input via the display unit 13. In this case, the operation input unit 15 can function as a UI (User Interface) via a web browser screen or an application screen displayed on the display unit 13. As an input method for the touch panel, for example, a general method such as a resistive film method, an infrared method, an electromagnetic induction method, or a capacitance method can be adopted.

[0025] The control unit 11 functions as an OS (Operating System) by reading out a control program 231 described later, and the UI driven under the control of the OS may be referred to as a UI / OS 110 in the first embodiment.

[0026] The communication unit 17 includes a wired / wireless interface or both for communicating with other devices (cloud 30, mail distribution server 50) via a network (NW) such as a LAN, a WAN, the Internet, a telephone line, a fax line, etc. The communication unit 17 may also include an interface related to (short-distance) wireless communication technology such as Bluetooth (registered trademark), NFC (Near field communication), Wi-Fi (registered trademark), ZigBee (registered trademark), Irda, wireless USB, etc.

[0027] The image processing unit 19 includes an image forming unit that forms an image based on image data on a recording medium such as paper. The image forming unit feeds paper from a paper feed tray (not shown), forms an image based on image data on the paper, and then discharges the paper to a paper discharge unit (not shown). The image forming unit can be configured, for example, by a laser printer using an electrophotographic method. In this case, the image forming unit forms an image using toner supplied from a toner cartridge (not shown) corresponding to a toner color (for example, cyan, magenta, yellow, black). The image processing unit 19 may also include a form in which the image data input from the image input unit 21 is subjected to, for example, shading correction, density correction, etc., to generate output image data to be attached to an e-mail.

[0028] The image input unit 21 generates image data by scanning an original. The image input unit 21 can be configured as a scanner device having an image sensor such as a CCD (Charge Coupled Device) or a CID (Contact Image Sensor), an automatic document feeder (ADF), or a flatbed for placing and reading an original. There is no particular limitation on the configuration of the image input unit 21 as long as it is configured to generate image data by reading a reflected light image from an original image with an image sensor. The image input unit 21 can also be configured as an interface capable of acquiring image data stored in a portable storage medium such as a USB (Universal Serial Bus) memory, or image data transmitted from an external terminal device (not shown), for example.

[0029] The storage unit 23 stores various programs and various data necessary for the operation of the multifunction device 10. The storage unit 23 can be configured with a storage device such as a random access memory (RAM), a hard disk drive (HDD), a solid state drive (SSD), or a read only memory (ROM).

[0030] In the first embodiment, the storage unit 23 stores a control program 231, an authentication program 232, an application program 233, a browser program 234, and an account management program 235, and reserves an account storage area 236.

[0031] The control program 231 is a program that is read by the control unit 11 when performing overall control of the multifunction device 10. The control unit 11 that has read the control program 231 functions as an OS, and controls the driving of the display unit 13, the operation input unit 15, the communication unit 17, the image processing unit 19, and the image input unit 21, thereby setting, executing, post-processing, etc., of each job such as printing, copying, faxing, and email transmission.

[0032] The authentication program 232 is a program that the control unit 11 reads out when performing authentication processing with the cloud 30. The control unit 11 that reads out the authentication program 232 performs authentication processing for the cloud 30 via a web browser described later. The control unit 11 that reads out the authentication program 232 can perform, in addition to an authentication method that requires prior authorization such as OAuth authentication, a conventional authentication processing (e.g., SMTP authentication processing, POP authentication processing) that performs authentication using a combination of a user name (user ID) and a password, and login authentication for the multifunction device 10. The control unit 11 that reads out the authentication program 232 also verifies, as authentication processing, whether or not an access token serving as authorization information for using a mail delivery service provided by the cloud 30 (mail delivery server 50) serving as a service providing device can be updated based on a refresh token serving as update request information associated with an account (hereinafter, referred to as update validity). In the present disclosure, the control unit 11 verifies the update validity of the access token based on the expiration date provided in the refresh token.

[0033] The application program 233 is an application capable of implementing functions such as printing, copying, faxing, and e-mail transmission by being read by the control unit 11. The application program 233 may be an integrated management application that manages settings and management of the multifunction device 10, or may be an individual application (e.g., a scan transmission application) using the integrated management application as a platform. The control unit 11 that reads the application program 233 can use functions provided by other programs such as the authentication program 232 via an API. The application program 233 and the authentication program 232 can cooperate to obtain / update / transfer authentication information and access tokens between the cloud 30. In the description here, the application program 233 and the authentication program 232 are described as being configured separately, but it is also possible to provide the function of the authentication program 232 in the application program 233. In the following description, the mode in which the control unit 11 that reads the application program 233 operates for the purpose of the user will be simply referred to as an application.

[0034] The browser program 234 is a program that the control unit 11 reads out when generating screen information for viewing by rendering inputted content. The control unit 11 that reads out the browser program 234 functions as a Web browser, and can receive inputs and requests from the user through the displayed Web browser screen, and can display notifications from applications to the user.

[0035] The account management program 235 is a program that the control unit 11 reads out when managing accounts set according to a provider. When the control unit 11 reads out the account management program 235, for example, upon receiving an input of a new account via a setting screen (not shown), the control unit 11 determines whether or not the authentication method of the new account corresponds to the OAuth authentication method. If the control unit 11 determines that the authentication method of the new account corresponds to the OAuth authentication method, the control unit 11 stores the new account as a second account as a substitute account for the first account already stored in the account storage area 236. If the control unit 11 determines that the authentication method of the new account does not correspond to the OAuth authentication method, the control unit 11 stores the new account in the account storage area 236 as an account of another authentication method.

[0036] The account storage area 236 is a storage area for storing accounts. The account storage area 236 stores accounts as an account management table, as exemplified in Fig. 3, under the control of the control unit 11 that has read out the account management program 235. The account storage area 236 can also be provided in an external storage device or the like that is connected to the network NW other than the multifunction device 10.

[0037] Here, a configuration example of an account management table according to the first embodiment will be described with reference to Fig. 3. Note that the configuration example of the account management table illustrated in Fig. 3 is merely an example, and management of accounts according to the present disclosure is not limited to the example in Fig. 3. For example, the account management table may include items other than the management items illustrated in Fig. 3, and the management format is not limited to a table format and may be a database.

[0038] The account management table 2361 includes, as management items, an ID, a user name, a provider, an account in use, an authentication method, an account type, and a token expiration date.

[0039] The ID is an identifier for uniquely identifying the managed account. The user name indicates the name of the owner of the account. The provider indicates the name of the authentication destination (cloud 30). The account used indicates the account name used in the authentication process. The authentication method indicates the authentication method corresponding to the account. The account type indicates the type of account corresponding to the OAuth authentication method. The token expiration date indicates the expiration date of the token issued by the cloud 30 corresponding to the account. Here, the token according to the present disclosure is intended to be a refresh token (update request information) for updating an access token (authorization information) for using the resource (mail delivery server 50) of the cloud 30. The expiration date according to the present disclosure indicates a certain period during which the token issued by the cloud 30 is valid, and may be expressed by a date or time, or may be expressed by a period from the date of issue by the cloud 30 to a specific date. In addition to these management items, the account management table 2361 may include, for example, a password associated with the usage account, a token (itself), an authorization code, and a contact point (email address, etc.) of the account owner as management items.

[0040] For example, the account associated with ID "01" represents an account owned by the user name "admin". The account associated with ID "01" authenticates the provider "aabbcc", and the account used in this case is "admin@aabbcc.jp". The account associated with ID "01" supports the OAuth authentication method (authentication method "OAuth authentication method"), and the type of the account is a "first account". The first account is an account used as a main account in authentication processing related to email transmission, and is an account that has been stored in the account storage area 236. In addition, the expiration date of the token for the account associated with ID "01" is "2023 / 5 / 10". If the token expiration date has passed, authentication processing using the account will fail.

[0041] The account associated with ID "02" represents an account owned by the user name "admin". The account associated with ID "02" is authenticated by the provider "aabbcc", and the account used at this time is "admin2@aabbcc.jp". The account associated with ID "02" supports the OAuth authentication method (authentication method "OAuth authentication method"), and the type of the account is "second account". The second account is stored in the account storage area 236 as an alternative account for the first account already stored in the account storage area 236 when the control unit 11 determines that the authentication method of the account accepted as a new account supports the OAuth authentication method. When the expiration date "2023 / 5 / 10" of the token associated with the first account has passed, the control unit 11 performs authentication processing using the second account that is an alternative account for the first account. In addition, the authentication process using an account in this disclosure is a concept that encompasses authentication and authorization processes that comply with the OAuth authentication method, and includes, for example, authentication processes for the cloud 30 using the account used (account name) and password, authorization processes using an access token, and token update request processes for an access token based on a refresh token.

[0042] On the other hand, the account associated with ID "03" represents an account owned by the user name "user01". The account associated with ID "03" authenticates to the provider "gghhii", and the account used in this case is "user@gghhii.jp". The account associated with ID "03" does not support the OAuth authentication method (authentication method: "SMTP authentication method"), and the account does not belong to either the "first account" or "second account" account type (account type: "-").

[0043] [1.2.2 About Cloud30] The cloud 30 according to the first embodiment can use a known configuration as long as it includes an authorization server that performs resource usage authorization by implementing an authorization code flow based on the OAuth authentication method. Therefore, a description of the functional configuration of the cloud 30 will be omitted.

[0044] [1.2.3 About mail delivery server 50] The mail delivery server 50 of the first embodiment can use a known configuration as long as it is capable of sending mail to a specific destination and delivering received mail in response to a mail sending request from the cloud 30 (resource server) via an API. Therefore, a description of the functional configuration of the mail delivery server 50 will be omitted.

[0045] [1.3 Processing flow] Next, a process flow according to the first embodiment will be described. Fig. 4 is a flowchart for explaining a process for setting (storing) an account accepted as a new account as a second account when the authentication method of the account corresponds to the OAuth authentication method. The process explained in the flowchart of Fig. 4 is a process executed by the control unit 11 by reading out the account management program 235 and the like. Also, in Fig. 4, the process for setting (storing) an account corresponding to the OAuth authentication method as a first account will be explained first.

[0046] First, the control unit 11 accepts the setting of an account corresponding to the OAuth authentication method by an administrator of the multifunction device 10 (for example, the account owner indicated by the user name "admin" of the ID "01" illustrated in the account management table 2361 of FIG. 3). The control unit 11 sets the accepted account as a first account related to the authentication process for sending email. When the control unit 11 accepts the setting of the first account, it stores the account in the account management table 2361 (step S10).

[0047] Next, the control unit 11 judges whether or not a new account input has been accepted (step S12). If the control unit 11 judges that the input of a new account has been accepted, the control unit 11 judges whether or not the authentication method of the account corresponds to the OAuth authentication method (step S12; Yes->step S14). If the control unit 11 judges that the input of a new account has not been accepted, the control unit 11 waits until the input of the account is accepted (step S12; No).

[0048] When the control unit 11 determines that the authentication method of the new account corresponds to the OAuth authentication method, it sets the new account as a second account that is an alternative account to the first account, and ends the process (step S14; Yes → step S16). At this time, the control unit 11 performs authentication processing for the cloud 30 using the second account.

[0049] On the other hand, if the control unit 11 determines that the authentication method of the accepted account does not support the OAuth authentication method, it sets the accepted account as an account for another authentication method and terminates the process (step S14; No → step S18).

[0050] Next, a command sequence between the user, the UI / OS 110, the application, and the cloud 30 when a transmission error occurs due to the expiration of the token and the user (administrator) performs re-authentication will be described with reference to Fig. 5. In the following, the authentication process will be described with a focus on the token update request process.

[0051] First, when a user inputs an instruction to send an email (S100), the UI / OS 110 sends a token update execution request command to the application (S102).

[0052] The application transmits a token update request command to the cloud 30 (S104). The cloud 30 that has received the token update request command verifies the expiration date of the token. If the token expiration date has passed, the cloud 30 performs an error determination (error determination). Then, the cloud 30 returns an error due to the expiration of the token to the application (S106). On the other hand, if the token expiration date has not passed, the application issues an updated token (access token, refresh token) and transmits a token response command to the application. The application that has received the token response command passes the token to the UI / OS 110. The UI / OS 110 transmits an email transmission request command including the acquired token to the cloud 30 (resource server). The cloud 30 (resource server) confirms the validity of the received token and transmits an email transmission request to the email delivery server 50. Then, when the email transmission is successful, the cloud 30 (resource server) transmits a transmission success response command to the UI / OS 110. The UI / OS 110 notifies the user that the email transmission is completed.

[0053] The application that receives the error return from the cloud 30 returns the error to the UI / OS 110 (S108). The UI / OS 110 notifies the user of the transmission error and the need for authentication (re-authentication required) associated with the transmission error (S110).

[0054] Next, a case where the administrator as a user re-authenticates after a transmission error will be described.

[0055] The UI / OS 110 receives a re-authentication request instruction from the administrator (S112). Upon receiving the re-authentication request instruction, the UI / OS 110 transmits an authentication processing request command to the application (S114). The application that receives the authentication processing request command transmits the authentication processing request command to the cloud 30 (S116).

[0056] The cloud 30 that has received the authentication process request command transmits an authentication screen response command to the application (S118). The authentication screen response command can include content related to an authentication screen for accepting input of authentication information (login information) for the administrator, and a URL (Uniform Resource Locator) indicating the storage location of the content.

[0057] When the application receives the authentication screen response command, it transmits the authentication screen response command to the UI / OS 110 (S120). The command transmitted from the application to the UI / OS 110 can include location information such as content and a URL related to the authentication screen received from the cloud 30, as well as an instruction to display the authentication screen via a Web browser.

[0058] The UI / OS 110, which has received the authentication screen response command from the application, displays an authentication screen for the administrator (S122).

[0059] The UI / OS 110 accepts input of login information by the administrator (S124). When the UI / OS 110 accepts the input of the login information, it transmits a login execution request command to the application (S126). When the application receives the login execution request from the UI / OS 110, it transmits a login request command to the cloud 30 (S128).

[0060] The cloud 30 performs login authentication by verifying the received login information. If the login authentication is successful (authentication OK), the cloud 30 sends an authorization screen response command to the application (S130). The authorization screen response command can include content related to an authorization screen for accepting input regarding whether or not the resource can be used, and a URL indicating the storage location of the content.

[0061] When the application receives the authorization screen response command, it transmits the authorization screen response command to the UI / OS 110 (S132). The command transmitted from the application to the UI / OS 110 can include location information such as the content and URL related to the authorization screen received from the cloud 30, as well as an instruction to display the authorization screen via a Web browser.

[0062] The UI / OS 110, which has received the authorization screen response command from the application, displays the authorization screen for the administrator.

[0063] Next, resending of an email after the administrator has been successfully re-authenticated will be described.

[0064] The UI / OS 110 accepts an instruction input from the administrator to resend the email (S136). When the UI / OS 110 accepts the instruction input to resend the email, it sends a token acquisition execution request command to the application (S138). When the application receives the token acquisition execution request command from the UI / OS 110, it sends a token acquisition request command including an authorization code to the cloud 30 (S140).

[0065] The cloud 30 issues a token based on the authorization code (authentication OK), and transmits a token response command to the application (S142). The application that receives the token response command passes the token to the UI / OS 110 (S144).

[0066] The UI / OS 110 sends an email transmission request command including the acquired token to the cloud 30 (resource server) (S146). The cloud 30 (resource server) checks the validity of the received token and sends an email transmission request to the email delivery server 50. Then, if the email transmission is successful, the cloud 30 (resource server) sends a transmission success response command to the UI / OS 110 (S148). The UI / OS 110 notifies the user that the email transmission has been completed (S150).

[0067] Next, a command sequence between the user, UI / OS 110, application, and cloud 30 when a transmission error occurs due to the expiration of a token and an email is resent using a second account will be described with reference to Fig. 6. Note that the command sequences from S100 to S108 and S142 to S150 are the same as those described with reference to Fig. 5, and therefore will not be described here.

[0068] The UI / OS 110, which has received an error return from the application, switches the account to the second account and transmits a token update execution request command to the application (S200). The application transmits a token update request command to the cloud 30 (S202). The cloud 30, which has received the token update request command, verifies the expiration date of the token. At this time, if the token related to the second account is within the expiration date, the cloud 30 determines whether the authentication is successful (authentication OK). Then, the cloud 30 issues a token and transmits a token response command to the application (S142). The application, which has received the token response command, passes the token to the UI / OS 110 (S144). On the other hand, if the token related to the second account has expired, the cloud 30 determines whether an error has occurred (error determination). Then, the cloud 30 returns an error due to the expiration of the token to the application. The application, which has received the error return from the cloud 30, returns an error to the UI / OS 110. The UI / OS 110 notifies the user of the transmission error and the need for re-authentication associated with the transmission error (re-authentication required).

[0069] The UI / OS 110 notifies the user that the account has been switched (S204). Meanwhile, the UI / OS 110 sends an email transmission request command to the cloud 30 (resource server) together with the acquired token (S146). The cloud 30 (resource server) checks the validity of the received token and sends an email transmission request to the email delivery server 50. Then, when the email transmission is successful, the cloud 30 (resource server) sends a transmission success response command to the UI / OS 110 (S148).

[0070] The UI / OS 110 notifies the user that the mail transmission has been completed (S150).

[0071] FIG. 7 is a flowchart illustrating the process executed by the UI / OS 110 when an error is returned from an application in S108 of FIG.

[0072] The UI / OS 110 determines whether or not a transmission error has been returned (step S20). If it is determined that a transmission error has been returned, the UI / OS 110 analyzes the contents of the received transmission error and determines whether or not the transmission error is caused by the expiration of the token (step S20; Yes->step S22). If the UI / OS 110 determines that a transmission error has not been returned, it waits until the transmission error is returned (step S20; No).

[0073] If the analysis of the transmission error determines that the transmission error is due to the expiration of the token's validity period, the UI / OS 110 switches the account to the second account (step S22; Yes → step S24). On the other hand, if the analysis of the transmission error determines that the transmission error is not due to the expiration of the token's validity period, the UI / OS 110 determines that the transmission error is due to, for example, a simple failure in account authentication, and ends the process without switching the account to the second account (step S22; No → "End").

[0074] After switching the account to the second account, the UI / OS 110 transmits a token update execution request command to the application and ends the process (step S26).

[0075] If switching to the second account is performed in all cases when a transmission error occurs, email transmission will be performed even in cases where security is undesirable, such as account authentication failure. For this reason, in the first embodiment, switching to the second account is performed based on certain conditions, such as the expiration of a token. With this configuration, it is possible to prevent email from being sent unnecessarily in cases where security is undesirable, such as when a transmission error occurs.

[0076] [1.4 Example of operation] Next, an operation example of the first embodiment will be described. Figures 8 and 9 are diagrams for explaining one configuration example of the SMTP setting screen W10. Figure 8 is a diagram for explaining the setting operation of a first account, and Figure 9 is a diagram for explaining the setting operation of a second account. The operation example explained in Figures 8 and 9 is an operation example corresponding to the processing exemplified in Figure 4.

[0077] The SMTP setting screen W10 illustrated in FIG. 8 and FIG. 9 includes an SMTP setting area R10 and an authentication method setting area R12.

[0078] The SMTP setting area R10 includes, as setting items, a primary server, a secondary server, a port number, a timeout, a sender name, a sender address, and a check box for enabling SSL / TLS.

[0079] The primary server and secondary server are input boxes for specifying the mail delivery server 50, and accept input of the name (domain name) of the mail delivery server 50, IP address information, etc. If no secondary server is set, the input boxes may be left blank.

[0080] The port number accepts input of the port number of the mail delivery server 50. The timeout accepts input of the length of time to maintain an idle state until a connection timeout occurs. The sender name accepts input of the name of the mail sender, and the sender address accepts input of the mail address of the mail sender. The enable SSL / TLS checkbox is a checkbox that accepts designation of whether or not to encrypt data when sending and receiving data over the Internet.

[0081] The authentication method setting region R12 includes an authentication method selection pull-down menu PM10, a provider input box Bx10, and an account name input box Bx12.

[0082] The authentication method selection pull-down menu PM10 is a pull-down menu that accepts the selection of an authentication method. Fig. 8 and Fig. 9 show a configuration in which any one of "no authentication", "SMTP authentication", and "OAuth authentication" can be selected as a selectable authentication method, and are examples in which the OAuth authentication method is selected as the authentication method.

[0083] The provider input box Bx10 is an input box that accepts input of the name of the provider (cloud 30) to be authenticated. Fig. 8 and Fig. 9 show an example in which "aabbcc" is input as the provider.

[0084] The account name input box Bx12 is an input box that accepts input of an account name for the provider to be authenticated. Fig. 8 shows an example in which "admin@aabbcc.jp" is input as the account name related to the first account. Fig. 9 shows an example in which "admin2@aabbcc.jp" is input as the account name related to the second account.

[0085] The settings entered via the SMTP setting screen W10 illustrated in FIGS. 8 and 9 are stored in the account management table 2361 illustrated in FIG.

[0086] Fig. 10 is a diagram for explaining a display configuration example of the account switching notification screen, which shows an example in which a message screen M10 is superimposed on a job execution screen W20 of a scan transmission application.

[0087] The message screen M10 is an example of a message screen notifying the user that the token for the account name "admin@aabbcc.jp" (first account) has expired and the account has been switched to a second account, displaying "The token has expired. The account has been switched to the second account." When placing restrictions on scan transmission (email transmission) using the second account (for example, when switching to the second account is restricted only when the token has expired, or when e-mail transmission using the second account is restricted to a re-authentication request for the account owner (administrator) (second embodiment)), it is also possible to add a message to alert the user, such as "The functionality of e-mail transmission using the second account may be restricted."

[0088] As described above, according to the first embodiment, even if the token for a first account has expired, the first account can be switched to a substitute account for the first account to send an email, thereby avoiding a situation in which email sending is disabled due to the expiration of the token until re-authentication processing is performed for the first account. Also, according to the first embodiment, it is possible to prevent the second account from being unnecessarily used for email sending such as scan sending, and to restrict email sending to destinations that are undesirable from a security standpoint.

[0089] [2 Second embodiment] The second embodiment is a form in which a notification is sent to the account owner of the first account, based on the switched second account, to prompt re-authentication.

[0090] [2.1 Functional configuration] The functional configurations of the multifunction device, cloud, and mail delivery server according to the second embodiment can be the same as the functional configurations of the multifunction device 10, cloud 30, and mail delivery server 50 according to the first embodiment. Therefore, the description here is omitted.

[0091] [2.2 Processing flow] 11 is a flowchart illustrating the flow of processing according to the second embodiment. In FIG. 11, processing will be described as a continuation of the processing described in steps S20 to S26 in FIG.

[0092] The UI / OS 110 notifies the account owner to prompt the account owner to perform re-authentication processing for the first account (step S30).

[0093] Next, the UI / OS 110 determines whether or not a re-authentication process is performed by the account owner and the re-authentication is successful (step S32). If it is determined that the re-authentication is successful, the UI / OS 110 switches the account related to the email transmission from the second account to the first account and ends the process (step S32; Yes → step S34). However, if it is determined that the re-authentication is not successful, the UI / OS 110 waits until the re-authentication is successful (step S32; No).

[0094] [2.3 Example of operation] Fig. 12 is a diagram for explaining a display configuration example of a notification screen notifying the account owner that a notification prompting re-authentication has been sent to the account owner. Fig. 12 is an example in which a message screen M12 is superimposed on a job execution screen W20 of a scan transmission application.

[0095] Message screen M12 is an example of a message screen that notifies the user that the token for the account name “admin@aabbcc.jp” (first account) has expired and prompts the user to re-authenticate the account, with the following notification: “The token has expired. A notification has been sent to the account owner. Please wait a moment until re-authentication is complete.”

[0096] Fig. 13 is a diagram for explaining an example of the configuration of an email sending screen W30 that notifies the account owner (administrator) that the token expiration date for the account name "admin@aabbcc.jp" (first account) has passed and prompts the account owner to re-authenticate the account. Fig. 13 is an example of an email sending screen with the notification "The token expiration date has passed. Please re-authenticate with the provider "aabbcc."" Note that the email sending screen W30 may include a link destination L10 to an authentication screen to facilitate the re-authentication process by the account owner.

[0097] As described above, according to the second embodiment, a notification urging re-authentication can be sent to the account owner of the first account based on the switched second account, so that the account owner of the first account can easily understand that re-authentication with the account is necessary. Furthermore, in the second embodiment, after sending an email based on switching to the second account, if re-authentication with the first account is successful, the account related to the email sending can be switched to the first account. With this configuration, it is also possible to obtain an effect that if re-authentication with the first account is successful, the user does not need to manually switch accounts.

[0098] [3 Third embodiment] In the case where the token of the first account has expired and re-authentication is required, and an attempt is made to send an e-mail based on the second account described in the first and second embodiments, if the token associated with the second account has expired, the e-mail cannot be sent and a transmission error may occur. In order to avoid such a situation, in the third embodiment, when the provider associated with the already-set first account and the provider associated with the account desired to be set as the second account are the same provider, the setting of the account as the second account is restricted, thereby making it possible to reduce the possibility of a failure to obtain a token for both the first account and the second account due to, for example, a server failure or a token reset.

[0099] [3.1 Functional configuration] The functional configurations of the multifunction device, cloud, and mail delivery server according to the third embodiment can be the same as the functional configurations of the multifunction device 10, cloud 30, and mail delivery server 50 according to the first embodiment. Therefore, the description here is omitted.

[0100] [3.2 Processing flow] The flow of the process according to the third embodiment can be realized by replacing Fig. 4 with the flowchart in Fig. 14. Therefore, the same processes are denoted by the same reference numerals and the description thereof will be omitted.

[0101] When the control unit 11 determines that the authentication method of the accepted account corresponds to the OAuth authentication method, it determines whether or not the provider of the accepted account is the same as the provider related to the first account (step S40). When the control unit 11 determines that the provider of the accepted account is the same as the provider related to the first account, it ends the process without setting the account as a second account (step S40; Yes→"End"). At this time, it may notify the user to prompt the user to set up via a provider different from the provider related to the first account.

[0102] On the other hand, if the control unit 11 determines that the provider associated with the accepted account is not the same as the provider associated with the first account, it sets the account as the second account and terminates the processing (step S40; No → step S16 → “End”).

[0103] [3.3 Example of operation] FIG. 15 shows an example in which a message screen M14, displaying that setting as a second account is not possible, is superimposed on the SMTP setting screen W10.

[0104] Message screen M14 is an example of a message screen notifying the user that the account desired to be set as the second account (account name "admin2@aabbcc.jp", provider name "aabbcc") is the same as the provider (name) "aabbcc" associated with the first account and therefore cannot be set as the second account, stating "As the provider is the same as the first account, it cannot be set as the second account. Please select a different provider." In this case, the administrator can set the entered account as the second account by selecting a provider other than the provider "aabbcc" associated with the first account.

[0105] Fig. 16 is a diagram for explaining an aspect in which selection of the same provider as the first account is restricted as the second account. Fig. 16 is an example of an aspect in which the same provider as the first account (provider name "aabbcc") is displayed in gray out form in the pull-down menu PM12 that accepts the selection of a provider, restricting the selection of the provider. In this way, when setting a second account, it is also possible to perform control such that selection of the same provider as the provider related to the first account is not permitted.

[0106] As described above, according to the third embodiment, by restricting the setting of an account as a second account so that the provider associated with an already-set first account and the provider associated with an account desired to be set as a second account are not the same provider, it is possible to reduce the possibility of a failure to obtain a token for both the first account and the second account due to a server failure, token reset, etc., resulting from the provider associated with the first account and the provider associated with the second account being the same provider.

[0107] For example, when the second account is set at a timing when there is a predetermined period (e.g., three months) between the expiration date of the first account and the expiration date of the second account, it is possible to accept the selection of the same provider as the first account as the second account. In this case, as illustrated in the message screen M16 of Fig. 17, for example, by displaying a message screen such as "There is a gap of more than three months between the expiration date of the first account and the expiration date of the second account. Although it is possible to set it with the same provider as the first account, we recommend that you select a different provider. ... Recommended provider: ddeeff", it is desirable to encourage the selection of a provider different from the provider of the first account as the second account and to draw attention to the situation.

[0108] The provider determination process for the above-mentioned accounts can also be performed on the cloud 30 side. In this case, if it is determined in the authentication process for the second account that the provider for the first account and the provider for the second account are the same provider, the cloud 30 may either reject the authentication for the second account or notify the control unit 11 of the multifunction device 10 of a notification urging the user to change to a different provider.

[0109] [4 Fourth embodiment] The fourth embodiment is a form that can check the expiration date of a token related to a first account and the expiration date of a token related to a second account, and prompt for re-authentication at an appropriate date and time so that the expiration dates of the tokens related to these accounts do not expire at the same time.

[0110] [4.1 Functional configuration] The functional configurations of the multifunction device, cloud, and mail delivery server according to the fourth embodiment can be the same as those of the multifunction device 10, cloud 30, and mail delivery server according to the first embodiment, and therefore will not be described here.

[0111] [4.2 Processing flow] Fig. 18 is a flowchart illustrating the flow of processing according to the fourth embodiment. Note that the processing described in the flowchart of Fig. 14 is executed by the control unit 11 reading out the account management program 235 and the like.

[0112] After setting the second account, the control unit 11 reads the expiration date of the token related to the second account and the expiration date of the token related to the first account from the account management table 2361 (step S50→step S52). Then, the control unit 11 determines the date and time for sending a notification prompting re-authentication based on the expiration date of the token read out in step S52 (step S54).

[0113] In addition, before setting up the second account, it is also possible to read the expiration date of the token associated with the first account and control the timing of setting up the second account so that the expiration date of the token associated with the second account is more than a predetermined time away.

[0114] The control unit 11 updates the account management table 2361 by reflecting the notification date and time determined in step S54 in the account management table 2361 (step S56).

[0115] The control unit 11 judges whether the date and time measured by a timing means (not shown) has reached the notification date and time of the notification prompting re-authentication (step S58). If it is judged that the measured date and time has reached the notification date and time of the notification prompting re-authentication, the control unit 11 notifies the account owner (administrator) or the like of the notification prompting re-authentication, and ends the process (step S58; Yes->step S60). Note that if it is judged that the measured date and time has not reached the notification date and time of the notification prompting re-authentication, the control unit 11 continues measuring the time by a timing means (not shown) until the notification date and time is reached (step S58; No).

[0116] Here, the account management table 2363 updated in the update process in step S56 in Fig. 18 will be described with reference to Fig. 19. The account management table 2363 illustrated in Fig. 17 includes a re-authentication notification date and time as a management item in addition to the management items managed in the account management table 2361 illustrated in Fig. 3. Here, for example, the token issue date of both accounts related to ID "01" and ID "02" is "May 10, 2023" and the expiration date is "November 10, 2023" (the validity period is six months from the token issue date).

[0117] Here, for example, if the re-authentication notification date and time is not determined and the re-recognition notification is not executed, the tokens for both accounts with ID “01” and ID “02” will expire on November 10, 2023.

[0118] However, as shown in the example of FIG. 17, the re-authentication notification date and time for notifying the token related to either the account of ID "01" or ID "02" (the token related to ID "01" in FIG. 17) of the prompting of re-authentication can be set to, for example, three months (August 10, 2023) from the token issue date (May 10, 2023) and notified, thereby preventing the tokens related to both accounts of ID "01" and ID "02" from expiring at the same time (on the same day). Note that in the example of FIG. 17, the re-authentication notification date and time is set for the token related to either the account of ID "01" or ID "02", but it is of course possible to set different re-authentication notification dates and times for the tokens related to both accounts of ID "01" and ID "02".

[0119] As described above, according to the fourth embodiment, by setting a re-authentication notification date and time to prompt re-authentication for either or both of the token related to the first account and the token related to the second account, it is possible to prevent the expiration dates of the token related to the first account and the token related to the second account from expiring at the same time.

[0120] [5 Variations] In OAuth authentication, there may be a limit on the number of tokens that can be acquired for each account. In a case where an account is used in many devices, the possibility of email transmission failing increases when the number of acquired tokens reaches the upper limit. In such a case, it is possible to prevent the occurrence of transmission errors by allowing a second account or multiple more accounts to be set for the multifunction device 10 and rotating the accounts related to email transmission.

[0121] The present disclosure is applicable to a token-based authentication method such as GNAP (Grant Negotiation and Authorization Protocol) as an authentication method other than OAuth authentication. The present disclosure is not limited to the above-described embodiments, and various modifications are possible. In other words, the technical scope of the present disclosure also includes embodiments obtained by combining technical means that are appropriately modified within the scope of the gist of the present disclosure.

[0122] Although the above-described embodiments are described separately for convenience of explanation, they may be combined and executed within a technically feasible range.

[0123] In addition, the programs that run on each device in the embodiments are programs that control the CPU and the like (programs that make a computer function) so as to realize the functions of the above-mentioned embodiments. Information handled by these devices is temporarily stored in a temporary storage device (e.g., RAM) during processing, and is then stored in various storage devices such as ROMs (Read Only Memories) and HDDs, and is read, modified, and written by the CPU as necessary.

[0124] Here, the recording medium for storing the program may be any of semiconductor media (e.g., ROM, non-volatile memory cards, etc.), optical recording media / magneto-optical recording media (e.g., DVD (Digital Versatile Disc), MO (Magneto Optical Disc), MD (Mini Disc), CD (Compact Disc), BD (Blu-ray (registered trademark) Disc, etc.)), magnetic recording media (e.g., magnetic tape, flexible disk, etc.), etc. Furthermore, not only are the functions of the above-mentioned embodiments realized by executing the loaded program, but the functions of the present disclosure may also be realized by processing in cooperation with an operating system or other application programs, etc., based on instructions from the program.

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

[0126] Also, each functional block or feature of the device used in the above-mentioned embodiment can be implemented and executed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. The electric circuit designed to realize the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or trongistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or a conventional processor, controller, microcontroller, or state machine. The electric circuit described above may be composed of a digital circuit or an analog circuit. Also, when an integrated circuit technology that replaces the current integrated circuit appears due to the progress of semiconductor technology, one or more aspects of the present disclosure can use a new integrated circuit according to the technology. [Explanation of symbols]

[0127] 10 Multifunction device 11 Control section 13 Display section 15 Operation input section 17 Communications Department 19 Image processing section 21 Image input unit 23 Memory section 231 Control Program 232 Certification Program 233 Application Program 234 Browser Program 235 Account Management Program 236 Account Storage 110 UI / OS 30. Cloud 50 Mail delivery server

Claims

1. a storage unit that stores an account for the service providing device; a control unit that controls an authentication process for the service providing device based on the account, The control unit is An image processing device characterized in that, when input of a new account is accepted, if it is determined that the new account and a first account stored in the memory unit correspond to the same authentication method, the image processing device stores the new account in the memory unit as a second account that is an alternative account to the first account.

2. The control unit is 2. The image processing apparatus according to claim 1, wherein, if the authentication process using the first account is unsuccessful, the authentication process for the service providing apparatus is performed using the second account.

3. The authentication process includes: The image processing device according to claim 2, further comprising a step of verifying the validity of an update of authorization information for using a service provided by the service providing device based on update request information associated with the first account, the update request information having an expiration date.

4. The control unit is 4. The image processing device according to claim 3, further comprising: a step of performing authentication processing with the service providing device using the update request information related to the second account only when the expiration date of the update request information related to the first account has passed.

5. The control unit is 3. The image processing apparatus according to claim 2, further comprising: a notification that prompts the owner of the first account to perform re-authentication processing using the first account.

6. The control unit is 6. The image processing device according to claim 5, wherein authentication processing for the service providing device using the second account is limited to a case where a notification is given to prompt re-authentication processing using the first account.

7. The control unit is 2 . The image processing device according to claim 1 , wherein when the new account and the first account are accounts for different service providing devices, the new account is stored in the storage unit as the second account.

8. The control unit is 4. The image processing device according to claim 3, further comprising: a processor that checks the expiration date of the update request information and notifies the owner of the first account or the owner of the second account of a request to update the authorization information before the expiration date expires.

9. storing an account for the service providing device as a first account in a storage device; when receiving an input of a new account, if it is determined that the new account and the first account correspond to the same authentication method, storing the new account in the storage device as a second account that is an alternative account for the first account; An authentication processing method for performing authentication processing for the service providing device based on the account stored in the storage device.

Citation Information

Patent Citations

  • Authentication device and program

    JP2018147216A

  • Account management device, account management method and account management program

    JP2021108134A

  • Image processing apparatus, method, and program

    JP2020170913A