Patent Application
20240333858
The present disclosure relates to a processing device and the like.
There is known a technology for cloning a device having the same device setting as that of a different device by importing the device setting exported from the different device as import data, or restoring a device setting by importing a device setting exported from a device itself (hereinafter, may be referred to as device cloning).
For example, in the case of a multifunction peripheral having a configuration as a processing device, exported data includes authentication information for a (cloud) service or the like such as a mail transmission service, in addition to setting information for executing a job in each mode such as copy, print, scan, fax, or mail transmission/reception, history information, user information of a user who uses the multifunction peripheral, and the like. Then, the export data is reflected as import data in a target multifunction peripheral, and thus the existing device setting held by the multifunction peripheral, inclusive of the authentication information, can be collectively rewritten.
Regarding import of a device setting including authentication information, it is known that when an information processing device uses a cloud service that requires OAuth 2.0 (hereinafter simply referred to as OAuth authentication) as an authentication method and an export file exported from another information processing device using the same cloud service is imported to the information processing device, data read from the export file is stored with a token included therein, and authentication is performed using the token when the same cloud service is used.
An object of the present disclosure is to provide a processing device and the like that can appropriately manage authentication information in importing the import data including the authentication information.
To solve the above problem, a processing device according to the present disclosure includes an authenticator that can apply first authentication information and authenticate to a service using second authentication information, a storage that stores a device setting including the first authentication information and the second authentication information, and one or more controllers that can verify import data imported to a device and reflect the import data on the device setting stored in the storage. The one or more controllers compare third authentication information with the first authentication information when determining that the import data includes the third authentication information as a result of verification of the import data, maintain the second authentication information when determining that the third authentication information and the first authentication information are the same authentication information, and reflect the third authentication information instead of the first authentication information on the device setting and delete the second authentication information from the storage when determining that the third authentication information and the first authentication information are not the same authentication information.
Moreover, an image processing device according to the present disclosure includes a processing device including an authenticator that can apply first authentication information and authenticate to a service using second authentication information, a storage that stores a device setting including the first authentication information and the second authentication information, and one or more controllers that can verify import data imported to a device and reflect the import data on the device setting stored in the storage, the one or more controllers comparing third authentication information with the first authentication information when determining that the import data includes the third authentication information as a result of verification of the import data, maintaining the second authentication information when determining that the third authentication information and the first authentication information are the same authentication information, and reflecting the third authentication information instead of the first authentication information on the device setting and deleting the second authentication information from the storage when determining that the third authentication information and the first authentication information are not the same authentication information, and an image processor that performs transmission processing of an image based on an authentication result in the service.
Furthermore, a processing method of import data according to the present disclosure includes storing a device setting including first authentication information and second authentication information in a storage device, verifying import data imported to a device, comparing third authentication information with the first authentication information when determining that the import data includes the third authentication information as a result of verification of the import data, maintaining the second authentication information when determining that the third authentication information and the first authentication information are the same authentication information, and reflecting the third authentication information instead of the first authentication information on the device setting and deleting the second authentication information from the storage device when determining that the third authentication information and the first authentication information are not the same authentication information.
According to the present disclosure, it is possible to provide a processing device and the like capable of appropriately managing authentication information in import of import data including the authentication information.
Embodiments according to the present disclosure will be described below with reference to the drawings. Note that the following embodiments are examples for explaining the present disclosure, and the technical content of the explanation described in the claims is not limited to the following description.
In a multifunction peripheral, execution of a mail transmission/reception job requires authentication to a mail server such as a simple mail transfer protocol (SMTP) server. In recent years, as a more secure authentication method, for example, an authentication method such as OAuth authentication that requires authorization in advance is becoming mainstream.
The OAuth authentication is a technology in which authorization of permission to use a resource is performed on an authentication service, and authentication with, for example, a mail server is performed using a token obtained to be a result of the authorization.
Here, when an authentication method of authentication information included in import data based on device cloning is an OAuth authentication method and authentication information (token) related to OAuth authentication is rewritten, re-authorization processing for an OAuth authentication service by a user having permission (administrator user) is required. In this case, a mail transmission/reception job via a mail server cannot be executed until the re-authorization is obtained from the OAuth authentication service, which causes a decrease in productivity. On the other hand, a configuration in which the authentication information (token) can be also used among a plurality of devices without the re-authorization from the OAuth authentication service is ethically not preferable.
According to the present disclosure, when authentication information related to OAuth authentication is imported to a device that supports an OAuth authentication method, rewriting of existing first authentication information is omitted and a token serving as second authentication information is maintained in a case where the imported authentication information is the same as the first authentication information serving as an existing device setting of the import destination, and the first authentication information is rewritten with the imported authentication information and the token serving as the existing device setting is deleted in a case where the imported authentication information is different from the existing first authentication information. Thus, according to the following embodiments, it is possible to achieve a processing device and the like capable of appropriately reflecting the authentication information related to the OAuth authentication in the device setting of the import destination without incorrectly reusing the token.
The multifunction peripheral 10 according to the first embodiment is an image processing device that can execute a job in each mode such as copy, print, scan, fax, or mail transmission/reception in one housing. Note that, in the present disclosure, the multifunction peripheral 10 will be described as one mode of the image processing device. However, the mode of the image processing device is not particularly limited as long as the processing device according to the present disclosure is mounted at the image processing device and the image processing device has an image processing function. The image processing device may be an image processing device other than the multifunction peripheral 10, such as a copier, a printer, or a fax. The multifunction peripheral 10 is an image processing device capable of reflecting export data exported from the multifunction peripheral 30 as import data in the device setting of the multifunction peripheral 10.
The multifunction peripheral 10 is connected to the multifunction peripheral 30, the authentication service 50, and the mail server 70 via a network NW1. The multifunction peripheral 10 is configured to communicate with the multifunction peripheral 30, the authentication service 50, and the mail server 70 using a communication protocol such as a hypertext transfer protocol (HTTP). Note that the network NW1 is not particularly limited as long as the network NW1 is a network line such as a local area network (LAN), a wide area network (WAN), the Internet, a telephone line, or a fax line. Note that the multifunction peripheral 10 can transmit and receive a mail via the mail server 70 based on a token acquired from the authentication service 50.
The multifunction peripheral 30 is an image processing device having the same or substantially the same device configuration and functional configuration as those of the multifunction peripheral 10. The multifunction peripheral 30 can export authentication information for the authentication service 50 as first device setting information, in addition to setting information for executing a job in each mode such as copy, print, scan, fax, or mail transmission/reception, history information, user information of a user who uses the multifunction peripheral, and the like. Note that, in the following description, it is assumed that the multifunction peripheral 30 is configured to support the OAuth authentication method as an authentication method and export first device setting information including authentication information related to the OAuth authentication.
The authentication service 50 can be configured as an authentication server that authorizes use of a resource by, for example, performing an authorization code flow based on OAuth 2.0 authentication. The configuration of the authentication service 50 is not limited as long as the authentication service 50 is configured to generate an authorization code, a token, and the like in accordance with the success or failure of authorization.
The mail server 70 is a server that supports the SMTP authentication method or the OAuth authentication method as an authentication method and that is capable of providing a service related to mail transmission/reception in accordance with the success or failure of an authentication result based on acquired authentication information such as a username (user ID), a password, or a token.
A functional configuration of the multifunction peripheral 10 according to the first embodiment will be described.
The controller 11 controls the entire multifunction peripheral 10. The controller 11 is configured of, for example, one or multiple arithmetic devices (central processing units (CPUs) or the like). The controller 11 implements a function thereof by reading and executing various programs stored in a storage 19.
The display 13 displays various types of information for a user or the like. The display 13 can be constituted by, for example, a liquid crystal display (LCD), an organic electro-luminescence (EL) display, or the like.
The operation inputter 15 receives an input of information by the user or the like. The operation inputter 15 can be constituted by, for example, various input devices such as operation keys (for example, hardware keys and software keys) and buttons. The operation inputter 15 can be configured as a touch panel that enables input via the display 13. In this case, as an input method for the touch panel, for example, a general method such as a resistance film method, an infrared beam method, an electromagnetic induction method, or an electrostatic capacitance method can be employed.
A communicator 17 includes, for example, one or both of wired and wireless interfaces for communicating with other devices (e.g., the multifunction peripheral 30, the authentication service 50, and the mail server 70) via the network NW1 such as a LAN, a WAN, the Internet, a telephone line, or a fax line. In addition, the communicator 17 may include an interface related to a (short-range) wireless communication technology such as Bluetooth (trade name), near-field communication (NFC), Wi-Fi (trade name), ZigBee (trade name), IrDA, or a wireless USB.
The storage 19 stores various programs and various types of data necessary for the operation of the multifunction peripheral 10. The storage 19 may be constituted by, for example, 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).
In the present embodiment, the storage 19 stores a control program 191, an authentication program 192, an import data verification program 193, and a device setting management program 194 and includes a device setting storage area 195.
The control program 191 is a program read by the controller 11 when the controller 11 performs centralized control of the multifunction peripheral 10. The controller 11 that has read the control program 191 controls driving of the display 13, the operation inputter 15, the communicator 17, and the like to perform the function of the processing device 1 according to the present disclosure, and further controls driving of the image processor 21 and the image inputter 23 to perform setting, execution, post-processing, and the like of each job such as copy, print, scan, fax, or mail transmission/reception.
The authentication program 192 is a program read by the controller 11 when the controller 11 performs authentication processing between the multifunction peripheral 10 and the authentication service 50. The controller 11 that has read the authentication program 192 functions as an authenticator and can perform authentication processing (SMTP authentication method, POP authentication method, or the like) of performing authentication based on a combination of a username (user ID) and a password, in addition to an authentication method such as the OAuth 2.0 authentication.
The import data verification program 193 is a program read by the controller 11 when the controller 11 imports, as import data, export data exported from the multifunction peripheral 30 or the like. The controller 11 that has read the import data verification program 193 verifies the import data and determines whether or not the import data can be reflected in the device setting stored in the device setting storage area 195. The verification processing of the import data by the controller 11 that has read the import data verification program 193 will be described below.
The device setting management program 194 is a program read by the controller 11 when the controller 11 manages the device setting of the multifunction peripheral 10 such as setting information for executing a job in each mode such as copy, print, scan, fax, or mail transmission/reception, history information, user information of a user who uses the multifunction peripheral, and authentication information for the authentication service 50. Based on the verification result of the import data, the controller 11 that has read the device setting management program 194 manages the device setting by, for example, rewriting, updating, or deleting the existing device setting managed in the device setting storage area 195.
The device setting storage area 195 is a storage area for storing the device setting of the multifunction peripheral 10. The device setting storage area 195 includes an authentication information storage area 1951 for storing, as a device setting, authentication information for the authentication service 50 and the mail server 70. When the OAuth authentication method is set as the authentication method of the multifunction peripheral 10, the authentication information storage area 1951 stores the authentication method (OAuth authentication), an account name, a server information (the server ID of the mail server 70), and the like as first authentication information, and a token as second authentication information. That is, the multifunction peripheral 10 can apply the first authentication information such as the account name and the server information and perform authentication to the authentication service using the token as the second authentication information. When the SMTP authentication method is set as the authentication method, the authentication information storage area 1951 stores the authentication method (SMTP authentication), an account name, a password, server information (the server address of the mail server 70), and the like as authentication information. Note that the authentication information storage area 1951 may store authentication information and the like related to login authentication of the multifunction peripheral 10.
The image processor 21 forms an image based on image data on a sheet or the like serving as a recording medium. The image processor 21 feeds a sheet from a feed tray (not illustrated), forms an image on the sheet based on image data, and then discharges the sheet to a paper discharger (not illustrated). The image processor 21 can be constituted by, for example, a laser printer using an electrophotographic system. In this case, the image processor 21 performs image formation using toners supplied from toner cartridges (not illustrated) corresponding to toner colors (for example, cyan, magenta, yellow, and black). The image processor 21 may perform, for example, shading correction or density correction on image data input from the image inputter 23 to generate output image data for image transmission.
The image inputter 23 generates image data by scanning a document. The image inputter 23 can be configured as a scanner device that is provided with an image sensor such as a charge coupled device (CCD) or a contact image sensor (CIS), and that includes an automatic document feeder (ADF), a flatbed on which a document is placed to be read, and the like. The configuration of the image inputter 23 is not particularly limited as long as the image inputter 23 can generate image data by reading a reflected light image from an original image using the image sensor. Note that the image inputter 23 can be configured as an interface that can acquire image data stored in a portable storage medium such as a universal serial bus (USB) memory and image data transmitted from an external terminal device (not illustrated).
The storage 39 of the multifunction peripheral 30 stores a control program 391, an authentication program 392, an export program 393, and a device setting management program 394 and includes a device setting storage area 395.
The export program 393 is a program read by the controller 31 of the multifunction peripheral 30 when the device setting of the multifunction peripheral 30 stored in the device setting storage area 395 is exported as export data. The controller 31 of the multifunction peripheral 30 reads authentication information according to the following (1) to (3) from the device setting storage area 395 (authentication information storage area 3951) based on the authentication method set for the multifunction peripheral 30, in addition to setting information for executing a job in each mode such as copy, print, scan, fax, or mail transmission/reception, history information, user information of a user who uses the multifunction peripheral, and exports the authentication information in an extensible markup language (XML) format, for example. Note that, in the present embodiment, the setting value of the device setting is expressed by a tag represented in the XML format as described below. In the present embodiment, although the set of tags exported in the XML format is common, the setting value of each device setting expressed by the tag can be read as a specific setting value, no setting value, or a blank for a setting item not used in accordance with each authentication method.
Here, SMTP setting items in a multifunction peripheral that supports the OAuth authentication method (SMTP setting in a model that supports the OAuth) and SMTP setting items in a multifunction peripheral that does not support the OAuth authentication method (SMTP setting in a model that does not support the OAuth) will be described with reference to
The existing authentication method (authentication) is a setting item for setting whether or not the SMTP authentication as the existing authentication method is valid. When the SMTP authentication is “valid” as the existing authentication method, the setting value is set to [true]. On the other hand, when the SMTP authentication is “invalid”, that is, when the existing authentication method is “no authentication”, the setting value is set to [false].
The new authentication method (security) is a setting item (new tag) provided in the SMTP setting of the multifunction peripheral that supports the OAuth authentication method, and a setting value of any of “no authentication [none]”, “SMTP authentication [auth]”, and “OAuth authentication [oauth]” is set based on the authentication setting of the multifunction peripheral.
The account name (username) is a setting item for setting [user account name].
The provider information (provider) is a setting item (tag) provided in the SMTP setting in the multifunction peripheral that supports the OAuth authentication method and is a setting item for setting [the ID of the OAuth authentication server to be used].
Others: SMTP setting used at the time of the OAuth authentication represents SMTP setting items used at the time of the OAuth authentication and include setting items such as a port number (port) and a server address (primary-address).
Others: SMTP setting not used at the time of the OAuth authentication represents SMTP setting items not used at the time of the OAuth authentication and include setting items such as a password and a POP before SMTP setting (pop-before-smtp).
The authentication service 50 can have a known configuration capable of implementing an authorization code flow based on the OAuth authentication method. Thus, the functional configuration of the authentication service 50 is not described herein. In addition, the mail server 70 supports the OAuth authentication method or the SMTP authentication method and can have a known configuration capable of providing a service related to mail transmission/reception according to the success or failure of an authentication result based on acquired authentication information such as a username (user ID), a password, or a token. Thus, the functional configuration of the mail server 70 is not described herein.
Next, a processing flow according to the present embodiment will be described. First, normal import processing in the multifunction peripheral 10 will be described with reference to a flowchart of
Note that, in the present disclosure, a tag (device setting) represented in the XML format is expressed in the following manner, for example.
In the present disclosure, the setting value (value) of the device setting expressed by each tag may be referred to as data when there is no need to distinguish therebetween.
First, the controller 11 reads export data exported from the multifunction peripheral 30 as import data (step S10).
Next, the controller 11 detects a tag from the read import data (step S13).
The controller 11 determines whether or not the read tag is a known tag (step S15). Here, the known tag is a tag that the controller 11 that has read the import data verification program 193 holds for verification of the import data. When the tag detected from the import data matches the held tag, the controller 11 can determine that the tag is the known tag.
If it is determined that the read tag is the known tag, the controller 11 reads data of the tag (Yes in step S15 and proceeding to step S17). Next, the controller 11 reflects the read data in the device setting (step S19).
The controller 11 determines whether or not the import data has been completely read (step S21). If it is determined that the import data has been completely read, the controller 11 ends the processing (Yes in step S21 and proceeding to the end). On the other hand, if it is determined that the import data has not been completely read, the controller 11 returns the processing to step S13 (No in step S21 and proceeding to step S13).
Meanwhile, if it is determined in step S15 that the read tag is not the known tag, the controller 11 skips reading the import data until the next tag (No in step S15 and proceeding to step S23). Then, the controller 11 determines whether or not the import data has been completely read (step S21). If it is determined that the import data has been completely read, the controller 11 ends the processing (Yes in step S21 and proceeding to the end). On the other hand, if it is determined that the import data has not been completely read, the controller 11 returns the processing to step S13 (No in step S21 and proceeding to step S13).
Next, processing of importing export data exported from the multifunction peripheral 30 that supports the OAuth authentication method will be described with reference to a flowchart of
If it is determined in step S15 that the read tag is the known tag, the controller 11 determines whether or not the import data is an existing SMTP setting tag (Yes in step S15 and proceeding to step S25). If it is determined that the import data is not the existing SMTP setting tag, the controller 11 determines whether or not the import data is a new OAuth setting tag (No in step S25 and proceeding to step S27).
If it is determined that the import data is the new OAuth setting tag, the controller 11 holds the data (OAuth data) read as the OAuth setting (Yes in step S27 and proceeding to step S29). Then, the controller 11 imports the held OAuth data (step S30).
After importing the OAuth data, the controller 11 determines whether or not the import data has been completely read (step S21). If it is determined that the import data has been completely read, the controller 11 ends the processing (Yes in step S21 and proceeding to the end). On the other hand, if it is determined that the import data has not been completely read, the controller 11 returns the processing to step S13 (No in step S21 and proceeding to step S13).
On the other hand, if it is determined that the import data is not the new OAuth setting tag, the controller 11 executes processing from step S17 to step S21 (No in step S27 and proceeding to step S17, step S19, and step S21).
Here, if it is determined in step S25 that the import data is the existing SMTP setting tag, that is, if it is determined that the import data includes the SMTP authentication information as the fourth authentication information, which is not information for the OAuth authentication method, the controller 11 determines whether or not the data (OAuth data) read as the OAuth setting is held (Yes in step S25 and proceeding to step S32).
If it is determined that the OAuth data is held, the controller 11 determines whether or not the import data has been completely read (Yes in step S32 and proceeding to step S21). If it is determined that the import data has been completely read, the controller 11 ends the processing (Yes in step S21 and proceeding to the end). On the other hand, if it is determined that the import data has not been completely read, the controller 11 returns the processing to step S13 (No in step S21 and proceeding to step S13).
On the other hand, if it is determined that the OAuth data is not held, the controller 11 reads data of the existing SMTP setting tag (No in step S32 and proceeding to step S34). Then, the controller 11 reflects the data read in step S34 in the device setting (step S36). After reflecting the read data, the controller 11 determines whether or not the import data has been completely read (step S21). If it is determined that the import data has been completely read, the controller 11 ends the processing (Yes in step S21 and proceeding to the end). On the other hand, if it is determined that the import data has not been completely read, the controller 11 returns the processing to step S13 (No in step S21 and proceeding to step S13).
Next, processing of importing the OAuth data in step S30 of
When the OAuth data import processing starts, the controller 11 determines whether or not the OAuth setting is included in the read data (step S301). If it is determined that the OAuth setting is included in the read data, the controller 11 determines whether or not the authentication method, the account name, and the server information included in the read data match the authentication method, the account name, and the server information of the device setting held by the multifunction peripheral 10 (Yes in step S301 and proceeding to step S303).
If it is determined that the authentication method, the account name, and the server information included in the read data match the authentication method, the account name, and the server information of the device setting held by the multifunction peripheral 10, the controller 11 eliminates the matching data from the read data (Yes in step S303 and proceeding to step S305). Then, the controller 11 reflects the OAuth data in the device setting of the multifunction peripheral 10 (step S307) and ends the processing.
On the other hand, if it is determined that the authentication method, the account name, and the server information included in the read data do not match the authentication method, the account, and the server information of the device setting held by the multifunction peripheral 10, the controller 11 deletes the held token serving as the second authentication information (No in step S303 and proceeding to step S309). Then, the controller 11 reflects the OAuth data in the device setting of the multifunction peripheral 10 (step 307) and ends the processing.
Next, a specific configuration example of the export data according to the present disclosure will be described with reference to
The <authentication></authentication> tag indicated by a frame E10 is a tag indicating whether or not the SMTP setting as the existing authentication method is valid. In the condition of the example illustrated in
The <security></security> tag indicated by a frame E12 is a new tag related to a newly added setting item and indicates that the authentication method of the multifunction peripheral is set to the OAuth authentication method ([oauth]).
Moreover, the setting value of the <username></username> tag representing the account name and the setting value of the <provider></provider> tag representing the provider information are set as in the example illustrated in
Note that although the <password></password> tag representing the password is blank, a blank character string is encrypted and thus the value is not blank as the XML data.
On the other hand, the setting items illustrated in
The <authentication></authentication> tag indicated by a frame E10 is a tag indicating whether or not the SMTP setting as the existing authentication method is valid. In the condition of the example illustrated in
The <security></security> tag indicated by a frame E12 is a new tag related to a newly added setting item and indicates that the authentication method of the multifunction peripheral is set to the SMTP authentication method ([auth]).
In addition, the setting value of the <username></username> tag representing the account name and the setting value of the <password></password> tag representing the password are set as in the example illustrated in
Note that although the setting value of the <provider></provider> tag representing the provider information is blank, a blank character string is encrypted and thus the value is not blank as the XML data.
On the other hand, setting items illustrated in
The <authentication></authentication> tag indicated by a frame E10 is a tag indicating whether or not the SMTP setting as the existing authentication method is valid. In the condition of the example illustrated in
The <security></security> tag indicated by a frame E12 is a new tag related to a newly added setting item and indicates that the authentication method of the multifunction peripheral is set to no authentication ([none]).
Moreover, the setting value of the <username></username> tag representing the account name is set as in the example illustrated in
Note that although the <password></password> tag representing the password is blank, a blank character string is encrypted and thus the value is not blank as the XML data.
The <authentication></authentication> tag indicated by a frame E10 is a tag indicating whether or not the SMTP setting as the existing authentication method is valid. In the condition of the example illustrated in
The <security></security> tag indicated by the frame E12 in the example illustrated in each of
The <authentication></authentication> tag indicated by a frame E10 is a tag indicating whether or not the SMTP setting as the existing authentication method is valid. In the condition of the example illustrated in
The <security></security> tag indicated by the frame E12 in the example illustrated in each of
Next, operation examples according to the present embodiment will be described.
The notification screen W10 includes a message screen M10 having a notification content “The import data has been verified and the authentication information is the same. Thus, the relevant setting has been skipped.”. The user can recognize that the related setting has been skipped in the import processing by checking the display content of the message screen M10.
The notification screen W20 includes a reflection information notification area R10, an OK button B10, a return button B12, and a partial edit button B14.
The reflection information notification area R10 is an area for notifying the device setting in which the import data is reflected.
The OK button B10 is a button for receiving permission of the reflection result of the import data. When the OK button B10 is selected by the user, the controller 11 determines that the import data is permitted to be reflected in the device setting and ends display of the notification screen W20. The return button B12 is a button for receiving selection for returning the device setting to the state before the import data is reflected. When the return button B12 is selected by the user, the controller 11 returns the device setting to the state before the import data is imported. The partial edit button B14 is a button for receiving an instruction to edit the device setting after the import data is reflected. When the partial edit button B14 is selected by the user, the controller 11 makes the device setting notified in the reflection information notification area R10 editable and receives the edit instruction from the user. The controller 11 edits the device setting based on the received edit instruction.
The authorization processing screen W30 includes a selection item display area R12, an advanced setting area R14, and a close button B18.
The selection item display area R12 is an area in which setting items that can be set by the user are displayed in a selectable manner.
The advanced setting area R14 is an area for displaying setting items for receiving input of setting values and the like for an item selected in the selection item display area R12. Note that
The advanced setting area R14 includes an authentication method pull-down menu PM10, a provider pull-down menu PM12, an account name input box Bx10 for receiving input of an account name for the provider, and a connection button B16.
The authentication method pull-down menu PM10 is a pull-down menu for receiving selection of an authentication method.
The provider pull-down menu PM12 is a pull-down menu for receiving selection of the authentication service 50 as an authentication destination necessary for the OAuth authentication. When a downward arrow provided at an edge portion of the menu is selected by the user, the provider pull-down menu PM12 displays a selectable provider name.
The account name input box Bx10 is an input box for receiving input of an account name for the provider “abcdefg”.
The connection button B16 is a button for receiving an instruction to start authorization processing with the provider “abcdefg”. Upon receiving the instruction to select the connection button B16 from the user, the controller 11 starts the authorization processing with the provider “abcdefg”.
The close button B18 is a button for receiving an instruction to end display of the authorization processing screen W30. When the user selects the close button B18, the controller 11 ends display of the authorization processing screen W30.
As described above, according to the present embodiment, when the authentication information related to the OAuth authentication is imported to the device that supports the OAuth authentication method, rewriting of the existing first authentication information is omitted and the token serving as the second authentication information is maintained in a case where the imported authentication information is the same as the first authentication information serving as the existing device setting of the import destination, and the first authentication information is rewritten with the imported authentication information and the token is deleted in a case where the imported authentication information is different from the existing first authentication information. Thus, it is possible to provide a processing device and the like capable of appropriately reflecting the authentication information related to the OAuth authentication in the device setting of the import destination without incorrectly reusing the token.
As a second embodiment, a mode will be described in which, when imported authentication information is the same as first authentication information serving as an existing device setting of an import destination, only the first authentication information is rewritten and rewriting of second authentication information is restricted.
Since the functional configuration according to the second embodiment can be similar to the functional configuration according to the first embodiment, description thereof will be omitted here.
OAuth data import processing according to the second embodiment can be explained with reference to a flowchart in which
In Step S303 of
According to the second embodiment, when the imported authentication information is the same as the first authentication information serving as the existing device setting of the import destination, it is possible to rewrite only the first authentication information and restrict rewriting of the token serving as the second authentication information. Thus, a similar effect as that of the first embodiment can be achieved.
As a third embodiment, a mode will be described in which when imported authentication information is different from first authentication information serving as an existing device setting of an import destination, a token serving as second authentication information is maintained without being deleted, and the first authentication information is rewritten with the imported authentication information.
Since the functional configuration according to the third embodiment can be similar to the functional configuration according to the first embodiment, description thereof will be omitted here.
OAuth data import processing according to the third embodiment can be explained with reference to a flowchart in which
In step S303 of
According to the third embodiment, when the imported authentication information is different from the first authentication information serving as the existing device setting of the import destination, the token serving as the second authentication information is maintained. In this case, since the maintained token does not match the token corresponding to the rewritten first authentication information, the token is not incorrectly reused. Then, since it is notified that reacquisition of the token by the administrator user is necessary, the authentication information related to the OAuth authentication can be appropriately reflected in the device setting of the import destination while the token is not incorrectly reused.
The present disclosure is not limited to the embodiments described above and can be changed in various manners. In other words, embodiments obtained by combining technical mechanisms appropriately changed without departing from the gist of the present disclosure are also included in the technical scope of the present disclosure.
Although some parts of the above-described embodiments are described separately for convenience of explanation, it is a matter of course that combinations can be executed within a technically allowable range.
The programs running on each device in the embodiments are programs for controlling a CPU or the like (programs for causing a computer to function) to realize the aforementioned functions in the embodiments. The information handled by these devices is temporarily accumulated in a transitory storage device (for example, a RAM) at the time of processing, is then stored in a storage device such as a read only memory (ROM) or an HDD, and is read, corrected, and written by the CPU as needed.
The recording medium storing the programs may be any of a semiconductor medium (for example, a ROM, a nonvolatile memory card, or the like), an optical recording medium or a magneto-optical recording medium (for example, a digital versatile disc (DVD), a magneto optical disc (MO), a mini disc (MD), a compact disc (CD), a Blu-ray (trade name) disc (BD) or the like), a magnetic recording medium (for example, a magnetic tape, a flexible disk, or the like), and the like. Not only the aforementioned functions of the embodiments are realized by executing the loaded programs, but also the functions of the present disclosure may be realized by performing processing in cooperation with an operating system, another application program, or the like based on instructions of the programs.
In a case where the programs are distributed to the market, the programs can be stored and distributed in a portable recording medium, or can be transferred to a server computer connected via a network such as the Internet. In this case, it is a matter of course that the storage device of the server computer is also included in the present disclosure.
In addition, each functional block or each characteristic of the device used in the above-described embodiments can be implemented and executed by an electric circuit, for example, an integrated circuit or a plurality of the integrated circuits. An electric circuit designed to implement the function 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 devices, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or any known processor, controller, microcontroller, or state machine. The above-described electric circuit may be constituted by a digital circuit or an analog circuit. In addition, in a case where an integrated circuit technology that replaces the current integrated circuit becomes available due to advancement of the semiconductor technology, one or more aspects of the present disclosure can use a new integrated circuit based on the new integrated circuit technology.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2023-057720 | Mar 2023 | JP | national |
