Image forming apparatus, information processing method, and computer program product

Abstract

The invention provides an image forming apparatus, an information processing method, and a computer program product. The present disclosure addresses the problem of causing a user to always perform an input operation of login information for use of a cloud service with respect to an image forming apparatus, resulting in low user convenience related to authentication. An image forming apparatus (100) is connected to a cloud server (200) that provides a cloud service, and includes: a storage unit (102) that associates and stores card information of a card of a legitimate user distributed to the image forming apparatus (100) and a token that makes use of the cloud service possible; a card information acquisition unit (103) that acquires card information of a card held by a target user that is a user who wants to use the cloud service via the image forming apparatus (100); and a service utilization unit (105) for utilizing the cloud service by using the token stored in the storage unit (102) so as to be associated with the acquired card information.

Description

Technical Field

[0001] The present disclosure relates to an image forming apparatus, an information processing method, and a computer program product. Background Art

[0002] Cloud services have become increasingly popular in recent years. Along with this, technologies for utilizing cloud services via image forming devices such as printers have been proposed. For example, Patent Document 1 discloses a technology for accessing files or folders in a cloud service's storage from an image forming device.

[0003] In the technology disclosed in Patent Document 1, users must authenticate themselves to access cloud services via an image forming device. This means users must constantly input login information into the image forming device to access the cloud service. Consequently, user convenience in accessing the cloud service is limited.

[0004] Patent Document 1: Japanese Patent Application Laid-Open No. 2022-140537 Summary of the Invention

[0005] The image forming device involved in the present disclosure is connected to a server that provides cloud services, and comprises: a storage unit that stores card information of a card distributed to a legitimate user of the image forming device and a token that enables the use of the cloud service in a manner that establishes a correspondence; a card information acquisition unit that acquires card information of a card held by a target user, wherein the target user is a user who wants to use the cloud service via the image forming device; and a service utilization unit that uses the token stored in the storage unit in a manner that establishes a correspondence with the acquired card information to utilize the cloud service.

[0006] In addition, the information processing method involved in the present disclosure is an information processing method for an image forming device connected to a server providing a cloud service, wherein card information of a card of a legitimate user distributed to the image forming device and a token that enables the use of the cloud service are stored in a manner that establishes a correspondence, card information of a card held by a target user is obtained, and the target user is a user who wants to use the cloud service via the image forming device, and the cloud service is used using the token stored in a manner that establishes a correspondence with the obtained card information.

[0007] In addition, the computer program product involved in the present disclosure enables a computer of an image forming device connected to a server providing a cloud service to execute the following steps, namely: a storage processing step, in which card information of a card distributed to a legitimate user of the image forming device and a token that enables the use of the cloud service are stored in a storage unit in a corresponding relationship; a card information acquisition step, in which card information of a card held by a target user is acquired, wherein the target user is a user who wants to use the cloud service via the image forming device; and a service utilization step, in which the cloud service is utilized using the token stored in the storage unit in a corresponding relationship with the acquired card information. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 This is a block diagram showing an example of the configuration of an information processing system according to an embodiment.

[0009] Figure 2 This is a block diagram showing an example of the functional configuration of the image forming apparatus according to the embodiment.

[0010] Figure 3 A diagram showing a specific example of information stored in the storage unit.

[0011] Figure 4 This is a block diagram showing an example of the hardware configuration of the image forming apparatus according to the embodiment.

[0012] Figure 5A This is a flowchart showing the flow of processing performed by the image forming apparatus according to the embodiment.

[0013] Figure 5B This is a flowchart showing the flow of processing performed by the image forming apparatus according to the embodiment.

[0014] Figure 6 A diagram showing a specific example of information stored in the storage unit.

[0015] Figure 7 This is a diagram showing a specific example of information acquired from the cloud server in the first confirmation process.

[0016] Figure 8 A diagram showing a specific example of information stored in the storage unit.

[0017] Figure 9 A diagram schematically showing the deletion of invalid information.

[0018] Figure 10 A diagram showing a specific example of information stored in the storage unit.

[0019] Figure 11A diagram showing a specific example of information stored in the storage unit. DETAILED DESCRIPTION

[0020] Hereinafter, the embodiments will be described with reference to the accompanying drawings. For the purpose of clarity of description, the following description and the accompanying drawings have been appropriately omitted and simplified. In addition, in each of the accompanying drawings, the same elements are marked with the same symbols, and repeated descriptions are omitted as needed.

[0021] Figure 1 1 is a block diagram showing an example of the structure of the information processing system 1 according to the embodiment. Figure 1 In the illustrated example, the information processing system 1 includes an image forming apparatus 100 and a cloud server 200. The image forming apparatus 100 and the cloud server 200 are connected to a network N such as the Internet.

[0022] In this embodiment, user U utilizes the cloud service provided by the cloud server 200 via the image forming device 100. In this embodiment, a token that enables the use of the cloud service provided by the cloud server 200 is stored in the image forming device 100. Moreover, the image forming device 100 uses the token to utilize the cloud service. Therefore, user U can utilize the cloud service without performing an authentication operation for utilizing the cloud service, that is, an operation of inputting login information for utilizing the cloud service. Therefore, according to this embodiment, the convenience of the user's utilization of the cloud service can be improved. In addition, the image forming device 100 only permits the use of the functions of the image forming device 100 and the use of the cloud service via the image forming device 100 to the user U who has successfully performed the user authentication implemented by the authentication unit 104 described later. Therefore, the information processing system 1 can be used securely. In this embodiment, authentication by the authentication unit 104 is basically successful when the card ID (card identification information) input by the image forming apparatus 100 is registered in the cloud server 200. However, in other cases, authentication by the authentication unit 104 may also succeed as an exception when predetermined conditions are met. This embodiment is described in detail below.

[0023] The cloud server 200 is a server that provides predetermined cloud services. The provided service is, for example, a data storage service. In this case, the following cloud service is utilized via the image forming apparatus 100. For example, the image forming apparatus 100 downloads data stored in the cloud server 200 using the data storage service provided as a cloud service and prints an image related to the data. In addition, the image forming apparatus 100 uses the data storage service to store image data generated by scanning a document in the cloud server 200. These are merely examples of the use of cloud services via the image forming apparatus 100, and processes other than those described above may also be implemented as the use of cloud services via the image forming apparatus 100.

[0024] If the login information obtained by the cloud server 200 through input operations performed by user U matches the login information pre-registered in the cloud server 200 for each user, the cloud server 200 permits the use of cloud services by the user U. Specifically, the login information is a combination of a user ID (user identification information) and a password, also referred to as account information. Furthermore, if the cloud server 200 obtains a token issued to each user to enable use of the cloud services, the cloud server 200 permits the use of cloud services by the user U corresponding to the token.

[0025] The above-mentioned tokens will now be described in more detail. Specifically, these tokens are refresh tokens. In this embodiment, two types of tokens are issued: access tokens and refresh tokens. An access token is information that proves access was performed by a legitimate user. A refresh token is issued along with an access token when one is also issued. Both access tokens and refresh tokens have a validity period. That is, these tokens are valid from the time they are issued until a predetermined period has passed. While the validity period of an access token is relatively short, approximately a few hours, the validity period of a refresh token is longer than that of an access token. In this embodiment, the validity period of a refresh token is, as an example, 90 days. An access token is issued when the login information obtained by cloud server 200 matches the login information pre-registered in cloud server 200 for each user, and when cloud server 200 obtains a refresh token. In other words, a refresh token is information that can be used as an alternative to login information for the purpose of issuing an access token. Cloud server 200 authorizes the use of cloud services in response to a request from image forming device 100 using an access token. Furthermore, as mentioned above, using a refresh token will result in the issuance of an access token. Therefore, the refresh token can be considered information that enables the use of cloud services. Furthermore, since using a refresh token eliminates the need for authentication to utilize cloud services, specifically the input of login information, the refresh token can also be considered information used to complete the authentication required for utilizing cloud services. Furthermore, the refresh token can also be considered information that serves as an alternative to login information. In the following description, the refresh token will be referred to simply as a "token."

[0026] Furthermore, in cloud server 200, the card information of a card distributed to a legitimate user of image forming device 100 is registered in a manner that establishes a correspondence with the user ID (user identification information) of that user. In other words, in cloud server 200, the card information of a card distributed to a legitimate user of image forming device 100 is registered in a manner that establishes a correspondence with the user ID of that user, who is also a user of the cloud service. In other words, the user ID of a legitimate user of the cloud service and the card information of that user are registered in cloud server 200 in a manner that establishes a correspondence. In this embodiment, the card information is more specifically referred to as the card ID (card identification information). Registration of card information is achieved, for example, through a registration operation performed by an administrator on cloud server 200. However, card information may not be registered in cloud server 200 for some or all of the cards distributed to legitimate users of image forming device 100 due to, for example, an administrator's omission in the registration operation.

[0027] Next, the details of image forming apparatus 100 will be described. Image forming apparatus 100 is connected to cloud server 200 , which is a server providing cloud services, via network N. FIG. Figure 2 FIG. 1 is a block diagram showing an example of the functional structure of the image forming apparatus 100. Figure 2 As shown, the image forming apparatus 100 includes a storage processing unit 101 , a storage unit 102 , a card information acquisition unit 103 , an authentication unit 104 , a service utilization unit 105 , an apparatus function utilization unit 106 , and a notification unit 107 .

[0028] The storage processing unit 101 causes the storage unit 102 to store information. For example, the storage processing unit 101 associates card information of a card issued to a legitimate user of the image forming device 100 with a token enabling the use of cloud services, and stores the associated information in the storage unit 102. More specifically, the storage processing unit 101 causes the storage unit 102 to store the card ID (card information) of a card issued to a legitimate user of the image forming device 100, the user ID (user identification information) of the user, the token enabling the use of cloud services, and information indicating the issuance time of the token, in such a manner that the associated information is associated with each user. Furthermore, the token stored in the storage unit 102 is, more specifically, a refresh token issued based on legitimate login information, or a refresh token reissued based on a legitimate refresh token.

[0029] The storage unit 102 is a storage area that stores information used by the authentication unit 104, the service utilization unit 105, and the like. Figure 3 1 is a diagram showing a specific example of information stored in the storage unit 102. Figure 3 As shown, the information stored in the storage unit 102 is information in which a user ID, a card ID, a token, and information indicating the issuance time of the token (hereinafter referred to as issuance time information) are associated with each user.

[0030] The card information acquisition unit 103 acquires the card information of the card held by the target user. More specifically, the card information acquisition unit 103 acquires the identification information of the card, that is, the card ID, as the card information. Here, the target user refers to a user who wants to use the cloud service provided by the cloud server 200 via the image forming device 100. In this embodiment, the user U is equivalent to the target user. The card information acquisition unit 103 acquires the card ID via the UI device 152 described later. More specifically, the card information acquisition unit 103 acquires the card ID read by the card reader provided by the image forming device 100 as the UI device 152. In addition, the card information acquisition unit 103 can also acquire the card ID input by the user U via the input device provided by the image forming device 100 as the UI device 152.

[0031] The authentication unit 104 performs an authentication process to verify that the target user (user U) is a legitimate user of the image forming apparatus 100. In this embodiment, the use of the functions of the image forming apparatus 100 and the use of cloud services via the image forming apparatus 100 are permitted if the authentication process performed by the authentication unit 104 results in a successful authentication. In other words, if the authentication process results in a successful authentication, the authentication unit 104 permits the use of the functions of the image forming apparatus 100 and the use of cloud services via the image forming apparatus 100 by the user U. If the authentication process results in a failed authentication, the authentication unit 104 prohibits the use of the functions of the image forming apparatus 100 and the use of cloud services via the image forming apparatus 100 by the user U.

[0032] The authentication process performed by the authentication unit 104 may include a first confirmation process, a second confirmation process, and a third confirmation process. The authentication process performed for user U may include all or only a portion of these confirmation processes. The specific confirmation processes that are performed in different situations will be described later with reference to the flowchart.

[0033] The first confirmation process is a process of acquiring user identification information (user ID) registered in the cloud server 200 in a manner associated with the card information (card ID) acquired by the card information acquisition unit 103. That is, in the first confirmation process, a process is performed to acquire, from the cloud server 200, user identification information corresponding to the acquired card information (card ID) from the user identification information of a legitimate user registered in the cloud service of the cloud server 200.

[0034] The second confirmation process is a process for confirming that the card information (card ID) acquired by the card information acquisition unit 103 is stored in the storage unit 102. In other words, the second confirmation process is a process for confirming that the card information acquired by the card information acquisition unit 103 is managed in the image forming apparatus 100 as the card information of a legitimate user of the image forming apparatus 100.

[0035] The third confirmation process is a process of obtaining specific user identification information from the cloud server 200 and confirming that the obtained user identification information is consistent with the user identification information stored in the storage unit 102 in a manner corresponding to the card information (card ID) obtained by the card information acquisition unit 103. Here, the above-mentioned specific user identification information is specifically the user identification information of a legitimate user of the cloud service who is registered in the cloud server 200 in association with the token stored in the storage unit 102 in a manner corresponding to the card information (card ID) obtained by the card information acquisition unit 103.

[0036] Furthermore, as shown in the flowchart described later, if the first confirmation process fails, the authentication unit 104 determines whether the main cause of the failure is an error in communication with the cloud server 200. If the authentication unit 104 does not receive a response from the cloud server 200 during the first confirmation process, the authentication unit 104 determines that the main cause of the failure in the first confirmation process is a communication error. Furthermore, if the authentication unit 104 receives a response but does not obtain the user identification information (user ID) registered in the cloud server 200 in a manner associated with the card information (card ID) obtained by the card information acquisition unit 103, the authentication unit 104 determines that the main cause of the failure in the first confirmation process is a cause other than a communication error.

[0037] The service utilization unit 105 implements a process of utilizing the cloud service provided by the cloud server 200 according to an instruction from the user U. When the result of the authentication process implemented by the authentication unit 104 for the user U is successful, the service utilization unit 105 performs the process of utilizing the cloud service according to the instruction of the user U. In particular, in this embodiment, the service utilization unit 105 uses a token stored in the storage unit 102 in a manner that establishes a correspondence with the card information (card ID) obtained by the card information acquisition unit 103 to utilize the cloud service. In this case, specifically, the service utilization unit 105 sends a refresh token as a token stored in the storage unit 102 to the cloud server 200, and requests the issuance of an access token and a new refresh token. When the image forming device 100 receives the access token, the service utilization unit 105 implements the utilization of the cloud service by sending a request for utilization of the cloud service together with the access token to the cloud server 200. For example, the service utilization unit 105 may download data from the cloud server 200 in response to a user instruction, or may upload image data generated by scanning to the cloud server 200 .

[0038] Furthermore, when the image forming apparatus 100 receives a new refresh token, the storage processing unit 101 causes the storage unit 102 to store the new refresh token in a manner that establishes a correspondence with the card information obtained by the card information acquisition unit 103. Consequently, the old refresh token, which had been stored in a manner that established a correspondence with the card information obtained by the card information acquisition unit 103, is updated to the new refresh token. Furthermore, the storage processing unit 101 causes the storage unit 102 to store the issuance time information of the new refresh token in a manner that establishes a correspondence with the card information obtained by the card information acquisition unit 103. Consequently, the old issuance time information, which had been stored in a manner that established a correspondence with the card information obtained by the card information acquisition unit 103, is updated to the new issuance time information.

[0039] In addition, the service utilization unit 105 does not necessarily need to use the token stored in the storage unit 102 when utilizing the cloud service. Specifically, when the user U performs an operation to input legitimate login information for utilizing the cloud service, the service utilization unit 105 utilizes the cloud service without using the token stored in the storage unit 102. In this case, the service utilization unit 105 sends the login information to the cloud server 200 and requests the issuance of an access token and a refresh token. Moreover, when the image forming device 100 receives the access token, the service utilization unit 105 utilizes the cloud service by sending the cloud service utilization request together with the access token to the cloud server 200. In this case, the storage processing unit 101 also stores the received refresh token and its issuance time point information in the storage unit 102 in a manner that establishes a correspondence with the card information obtained by the card information acquisition unit 103.

[0040] The device function utilization unit 106 performs processing for utilizing functions provided by the image forming apparatus 100 in accordance with instructions from the user U. In this embodiment, as an example, the device function utilization unit 106 performs processing for utilizing the printing function implemented by the printing unit 150 or the scanning function implemented by the scanner 151 (described later) in accordance with instructions from the user U. If the authentication processing performed by the authentication unit 104 on the user U is successful, the device function utilization unit 106 executes processing for utilizing the functions provided by the image forming apparatus 100 in accordance with the instructions of the user U.

[0041] When the remaining validity period of a token identified based on the issuance time information stored in the storage unit 102 is less than a predetermined threshold, the notification unit 107 notifies the user corresponding to the token of a predetermined message. Specifically, the notification unit 107 notifies the user of the token that its validity period is about to expire. Alternatively, the notification unit 107 may be a message urging the user to utilize cloud services provided by the image forming device 100. In this embodiment, the notification unit 107 performs notification processing in more detail as follows. Based on the time (date) indicated by each issuance time information stored in the storage unit 102 and the current time (date), the notification unit 107 confirms whether a token whose validity period is about to expire exists. For example, the notification unit 107 confirms whether a token exists that has been issued for 80 days. This confirmation can be performed at any desired time, for example, whenever the image forming device 100 is powered on, during the first authentication process performed by the authentication unit 104 in a day, or at a predetermined time. Furthermore, in the case where there is a token whose validity period is about to expire, the notification unit 107 obtains the email address of the user corresponding to the token. In the present embodiment, the cloud server 200 manages the email address of each registered user, and the notification unit 107 queries the cloud server 200 for the email address of the user. In addition, in more detail, the notification unit 107 uses the token of the user stored in the storage unit 102 to query the email address. Furthermore, the notification unit 107 uses the email address obtained in this manner to send the above-mentioned message by email. In addition, the user's email address does not necessarily have to be obtained from the cloud server 200, and can also be pre-stored in the storage unit 102 of the image forming device 100, etc.

[0042] Next, an example of the hardware configuration of the image forming apparatus 100 will be described. Figure 4 FIG. 1 is a block diagram showing an example of the hardware structure of the image forming apparatus 100. Figure 4 As shown, the image forming apparatus 100 includes a printing unit 150 , a scanner 151 , a UI device 152 , a network interface 153 , a memory 154 , and a processor 155 .

[0043] The printing unit 150 has a printing function for forming an image on a printing medium such as paper. For example, the printing unit 150 includes a printing engine. The printing engine refers to a mechanical structure that uses color materials to print an image on a printing medium. The printing engine may also have a mechanism that uses ink to print by an inkjet method, for example. Alternatively, the printing engine may also have a mechanism that uses toner to print by an electronic photographic method, for example. The scanner 151 scans the original and generates image data. For example, the scanner 151 scans the original in a predetermined direction, that is, the sub-scanning direction, by using a light source and a sensor, thereby optically reading the original and generating image data. In addition, the image forming apparatus 100 may also have a conveying mechanism that conveys the printing medium printed by the printing unit 150 or the original scanned by the scanner 151.

[0044] The UI device 152 functions as a user interface. Specifically, the UI device 152 is composed of a display that displays various information and an input device such as a keyboard or pointing device that receives input operations from the user. Alternatively, the UI device may be configured as a touch panel in which the display and input device are integrated.

[0045] The network interface 153 is used for communication via the network N. The network interface 153 may include, for example, a network interface card (NIC).

[0046] The memory 154 is composed of, for example, a combination of volatile memory and nonvolatile memory. The memory 154 is used to store programs executed by the processor 155. In addition, the storage unit 102 described above can also be implemented by a storage device such as the memory 154. The memory 154 can also include multiple memories.

[0047] Processor 155 reads and executes programs from memory 154. Thus, processor 155 implements the functions of the aforementioned storage processing unit 101, card information acquisition unit 103, authentication unit 104, service utilization unit 105, device function utilization unit 106, and notification unit 107. Processor 155 may be, for example, a microprocessor, an MPU (Micro Processor Unit), or a CPU (Central Processing Unit). Processor 155 may also include multiple processors. Thus, image forming apparatus 100 has a computer configuration.

[0048] The cloud server 200 also has a configuration as a computer, and the processor of the cloud server 200 reads and executes programs from the memory of the cloud server 200 , thereby realizing various functions of the cloud server 200 .

[0049] The program includes a command group (or software code) for causing the computer to implement one or more functions described in the embodiment when read by the computer. The program can also be stored in a non-temporary computer-readable medium or a storage medium with entity. As non-limiting examples, the computer-readable medium or the storage medium with entity includes random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drive (SSD) or other memory technology, CD-ROM, digital versatile disc (DVD), Blu-ray (registered trademark) Blu-ray disc or other optical disc storage, cassette tape, magnetic tape, magnetic disk storage or other magnetic storage device. The program can also be sent on a temporary computer-readable medium or communication medium. As non-limiting examples, the temporary computer-readable medium or communication medium includes electrical, optical, acoustic, or other forms of propagation signals.

[0050] Next, the flow of processing performed by image forming apparatus 100 will be described. Figure 5A as well as Figure 5B FIG. 1 is a flowchart showing an example of a process flow of the image forming apparatus 100. Figure 5A as well as Figure 5B At the same time, the processing flow is explained.

[0051] In step S100 , the card information acquisition unit 103 acquires card information, ie, a card ID, of a card held by the target user U. After step S100 , an authentication process is performed by the authentication unit 104 in steps S101 and thereafter.

[0052] In step S101, authentication unit 104 performs a first confirmation process. Specifically, authentication unit 104 attempts to obtain a user ID registered in cloud server 200 in association with the card ID obtained in step S100. Specifically, authentication unit 104 queries cloud server 200 for a user ID registered in cloud server 200 in association with the card ID obtained in step S100. Specifically, authentication unit 104 requests cloud server 200 to transmit the user ID corresponding to the card ID obtained in step S100. If the first confirmation process is successful, that is, if the user ID registered in cloud server 200 in association with the card ID obtained in step S100 can be obtained from cloud server 200 (YES in step S102), processing proceeds to step S103. In contrast, if the first confirmation process fails, that is, if the user ID registered in the cloud server 200 in a manner associated with the card ID obtained in step S100 cannot be obtained from the cloud server 200 (No in step S102), the processing transfers to step S106.

[0053] In step S103, the authentication unit 104 performs a second confirmation process. Specifically, the authentication unit 104 checks whether the card ID obtained in step S100 is stored in the storage unit 102. If the second confirmation process is successful, that is, if the card ID obtained in step S100 is stored in the storage unit 102 (YES in step S104), the process proceeds to step S119. On the other hand, if the second confirmation process fails, that is, if the card ID obtained in step S100 is not stored in the storage unit 102 (NO in step S104), the process proceeds to step S105.

[0054] In step S105, the storage processing unit 101 associates the card ID acquired in step S100 with the user ID acquired in step S101, and stores the associated information in the storage unit 102. After step S105, the process proceeds to step S119.

[0055] When the process proceeds to step S106, the authentication unit 104 determines whether the main cause of the failure of the first confirmation process in step S101 was a communication error with the cloud server 200. If the main cause of the failure of the first confirmation process was a communication error (YES in step S106), the process proceeds to step S107. On the other hand, if the main cause of the failure of the first confirmation process was not a communication error (NO in step S106), the process proceeds to step S110.

[0056] In step S107, the authentication unit 104 performs a second confirmation process. Specifically, the authentication unit 104 checks whether the card ID obtained in step S100 is stored in the storage unit 102. If the second confirmation process is successful, that is, if the card ID obtained in step S100 is stored in the storage unit 102 (YES in step S108), the process proceeds to step S119. In contrast, if the second confirmation process fails, that is, if the card ID obtained in step S100 is not stored in the storage unit 102 (NO in step S108), the process proceeds to step S109. In step S109, the authentication unit 104 determines that authentication has failed. This determination is made because, although the failure to confirm that the card ID of user U's card is registered in the cloud server 200 is due to a communication error, since the card ID is not found in the image forming device 100, authentication cannot be considered successful as an exception. Since it is determined that the authentication has failed, the process ends and the target user U cannot use the image forming apparatus 100 .

[0057] If the process proceeds to step S110, the authentication unit 104 performs a second confirmation process in step S110. Specifically, the authentication unit 104 checks whether the card ID acquired in step S100 is stored in the storage unit 102. If the second confirmation process succeeds, that is, if the card ID acquired in step S100 is stored in the storage unit 102 (YES in step S111), the process proceeds to step S112. On the other hand, if the second confirmation process fails, that is, if the card ID acquired in step S100 is not stored in the storage unit 102 (NO in step S111), the process proceeds to step S115.

[0058] In step S112, authentication unit 104 performs a third confirmation process. In this third confirmation process, authentication unit 104 first searches for the token stored in storage unit 102 in association with the card ID obtained in step S100, and then queries cloud server 200 for the user ID registered in cloud server 200 in association with the token. Specifically, authentication unit 104 requests cloud server 200 to transmit the user ID corresponding to the token. Next, authentication unit 104 confirms whether the user ID obtained from cloud server 200 matches the user ID stored in storage unit 102 in association with the card ID obtained in step S100. If the third confirmation process is successful—that is, if the user ID obtained from cloud server 200 is successful and the obtained user ID matches the user ID stored in storage unit 102 in association with the card ID obtained in step S100 (YES in step S113), processing proceeds to step S119. On the other hand, if the third confirmation process fails (No in step S113), the process proceeds to step S114. In other words, if the acquisition of the user ID from the cloud server 200 fails, or if the acquired user ID differs from the user ID stored in the storage unit 102 in a manner associated with the card ID acquired in step S100, the process proceeds to step S114.

[0059] In step S114, the storage processing unit 101 deletes the invalid information. Specifically, the storage processing unit 101 deletes the information stored in the storage unit 102 in a manner associated with the card ID obtained in step S100. After step S114, the process moves to step S115.

[0060] In step S115, the authentication unit 104 prompts the user U to perform an operation of inputting login information for utilizing the cloud service, that is, an authentication operation for logging into the cloud service. In response to this, the user U performs an operation of inputting login information via the UI device 152, for example. The cloud server 200 determines whether the login information input by the user U is legitimate information. If the login information is legitimate information, the login to the cloud service will be successful. In step S116, the authentication unit 104 determines whether the login to the cloud service has been successful. If the login to the cloud service is successful (yes in step S116), the processing transfers to step S118. In contrast, if the login to the cloud service fails (no in step S116), the processing transfers to step S117. In step S117, the authentication unit 104 determines that the authentication has failed. Since it is determined that the authentication has failed, the processing ends, and the user U as the target user cannot utilize the image forming device 100.

[0061] On the other hand, if the login to the cloud service is successful, in step S118, the storage processing unit 101 re-saves the target user's information in the storage unit 102. Specifically, the storage processing unit 101 stores the user ID and token obtained from the cloud service, as well as the issuance time information of the token, in the storage unit 102 in a manner associated with the card ID obtained in step S100.

[0062] When processing transfers to step S119, authentication unit 104 determines that authentication is successful. This determination allows user U, the target user, to use image forming device 100. Furthermore, the reason processing transfers from step S104 or step S105 to step S119 and is determined to be successful is that the first confirmation process is successful. That is, this is because the card ID entered into image forming device 100 is confirmed to be registered with cloud server 200. Furthermore, when processing transfers from step S108 to step S119, although the first confirmation process fails, authentication is exceptionally determined to be successful. This is because the primary reason for the failure of the first confirmation process is simply a communication error, and the card ID obtained in step S100 is confirmed to be managed in image forming device 100. In other words, based on this fact, the target user can be inferred to be a legitimate user of image forming device 100. Furthermore, when processing is transferred from step S113 to step S119, even though the first confirmation process failed, authentication is exceptionally determined to be successful. This is because, while the primary cause of the failure of the first confirmation process was not a communication error, it is confirmed that the card ID obtained in step S100 is managed by image forming device 100, and that a user ID associated with the card ID is registered in cloud server 200. In other words, based on these facts, the target user can be inferred to be a legitimate user of image forming device 100. Furthermore, when processing is transferred from step S118 to step S119, even though the first confirmation process failed, authentication is determined to be successful. This is because, based on the login information, the target user (user U) is confirmed to be a legitimate user of the cloud service.

[0063] After step S119, the processing transfers to step S120. In step S120, the service utilization unit 105 implements the processing of utilizing the cloud service provided by the cloud server 200 according to the instruction from the target user (user U). At this time, if there is a token stored in the storage unit 102 in a manner corresponding to the card ID obtained in step S100, the service utilization unit 105 uses the token to utilize the cloud service. In this case, a new token is obtained, and the storage processing unit 101 updates the token and issuance time point information of the storage unit 102. In addition, in this flowchart, the processing of the service utilization unit 105 is recorded in step S120, but the processing of the device function utilization unit 106 can also be implemented in step S120.

[0064] Next, in order to help understand the above-mentioned image forming apparatus 100, several specific examples will be described. Figure 3,as well as Figures 6 to 11 . Figure 6 A diagram showing a specific example of information stored in the storage unit 102. Figure 7 This is a diagram showing a specific example of information acquired from the cloud server 200 in the first confirmation process. Figure 8 A diagram showing a specific example of information stored in the storage unit 102. Figure 9 A diagram schematically showing the deletion of invalid information. Figure 10 A diagram showing a specific example of information stored in the storage unit 102. Figure 11 A diagram showing a specific example of information stored in the storage unit 102.

[0065] Scenario 1

[0066] Scenario 1 is an example of a case in which the user U, whose card ID is registered in cloud server 200 by an administrator and whose user ID, card ID, token, and issuance time information are stored in storage unit 102, is the target user for authentication. For example, if the user who becomes the target user for authentication in Scenario 7 described later uses image forming device 100 again, he or she becomes the target user for authentication in Scenario 1. The flow of Scenario 1 described below corresponds to the processing flow that reaches step S119 through steps S100, S101, S102, S103, and S104 described above.

[0067] As a premise of the case 1, it is assumed that the storage unit 102 stores Figure 6 The information shown is assumed to be obtained as the card ID in step S100. At this time, in case 1, the first confirmation process (step S101) is successful (step S102 is yes), and the authentication unit 104 obtains the card ID from the cloud server 200 as an example. Figure 7 The user information shown. That is, the authentication unit 104 obtains "user4" as the user ID corresponding to the card ID "4444". Thereafter, the second confirmation process is implemented (step S103). Since the card ID "4444" is stored in the storage unit 102, the second confirmation process is successful (yes in step S104). Therefore, without implementing the process of step S105, it is determined that the authentication is successful (step S119). Thereafter, the service utilization unit 105 uses the token "Dd" stored in the storage unit 102 to utilize the cloud service (step S120). That is, user U can utilize the cloud service without entering the login information for the cloud service.

[0068] Scenario 2

[0069] Case 2 is an example of a case where the user U, the target of authentication, has a card ID registered in the cloud server 200 by the administrator but no information is stored in the storage unit 102. The flow of Case 2 described below corresponds to the processing flow that reaches step S119 through steps S100, S101, S102, S103, S104, and S105 described above.

[0070] As a premise of the second scenario, it is assumed that the storage unit 102 stores Figure 3 The information shown is assumed to be obtained as the card ID in step S100. At this time, in case 2, the first confirmation process (step S101) is successful (step S102 is yes), and the authentication unit 104 obtains the card ID from the cloud server 200 as an example. Figure 7 The user information shown. That is, the authentication unit 104 obtains "user4" as the user ID corresponding to the card ID "4444". Thereafter, the second confirmation process is implemented (step S103). Since the card ID "4444" is not stored in the storage unit 102, the second confirmation process fails (No in step S104). Therefore, the storage processing unit 101 Figure 8 As shown, a correspondence is established between the card ID "4444" and the user ID "user4" obtained from the cloud server 200, and the storage unit 102 stores the information (step S105). The authentication unit 104 then determines that authentication is successful (step S119). In this case, since the token has not yet been stored in the storage unit 102, user U must enter the cloud service login information before using the cloud service (step S120).

[0071] Scenario 3

[0072] Scenario 3 illustrates a situation in which the user U, the target user for authentication, whose user ID, card ID, token, and issuance time information are stored in storage unit 102, is unable to communicate with image forming device 100 and cloud server 200. For example, this scenario corresponds to a situation in which the user who becomes the target user for authentication in Scenario 7, described later, experiences a communication failure when attempting to use image forming device 100 again. The process described below for Scenario 3 corresponds to the processing flow that proceeds through steps S100, S101, S102, S106, S107, and S108 described above, ultimately reaching step S119.

[0073] As a premise of case 3, it is assumed that the storage unit 102 stores Figure 6The information shown is used, and it is assumed that "4444" is obtained as the card ID in step S100. In this case, in scenario 3, the first confirmation process (step S101) fails due to a communication error (No in step S102, Yes in step S106), and the second confirmation process is implemented (step S107). Since the card ID "4444" is stored in the storage unit 102, the second confirmation process is successful (Yes in step S108). In this case, although the first confirmation process failed, the main reason for the failure was simply a communication error, and the second confirmation process was successful, so it is exceptionally determined that the authentication is successful (step S119). Thereafter, the service utilization unit 105 uses the token "Dd" stored in the storage unit 102 to utilize the cloud service (step S120). In other words, user U can utilize the cloud service without entering the cloud service login information.

[0074] Scenario 4

[0075] Case 4 is an example of a case where the user U, the target of authentication, has no information stored in storage unit 102, and the image forming apparatus 100 and cloud server 200 cannot communicate. The flow of Case 4 described below corresponds to the processing flow that proceeds through steps S100, S101, S102, S106, S107, and S108 described above, and reaches step S109.

[0076] As a premise of the scenario 4, it is assumed that the storage unit 102 stores Figure 3 The information shown in FIG. 4 is provided, and "4444" is obtained as the card ID in step S100. In this case, in scenario 4, the first confirmation process (step S101) fails due to a communication error (No in step S102, Yes in step S106), and the second confirmation process (step S107) is performed. Since the card ID "4444" is not stored in the storage unit 102, the second confirmation process also fails (No in step S108). Therefore, the authentication is not determined to be successful, but rather failed (step S109).

[0077] Scenario 5

[0078] Scenario 5 illustrates a case where the user U, whose card ID has not been registered with the cloud server 200 by the administrator and whose user ID, card ID, token, and issuance time information are stored in storage unit 102, is the authentication target. However, assume that user U, while not having his card ID registered with cloud server 200, is registered with cloud server 200 as a legitimate user of cloud services. Since card ID registration with cloud server 200 is unnecessary for cloud service use, there is a possibility that the card ID of a legitimate cloud service user may not be stored in cloud server 200. Furthermore, in this scenario, as described above, user U's user ID and card ID are stored in storage unit 102. This information is pre-stored in storage unit 102 of image forming device 100, for example, through user U's own registration operation or an administrator's registration operation. Furthermore, storage unit 102 also stores a token and its issuance time information, associated with user U's user ID and card ID. This information stores, for example, information about a token issued when user U successfully logs into the cloud service by inputting login information prior to the occurrence of scenario 5. The process for scenario 5 described below corresponds to the processing flow that proceeds through steps S100, S101, S102, S106, S110, S111, S112, and S113 described above and reaches step S119.

[0079] As a premise of case 5, it is assumed that the storage unit 102 stores Figure 6The information shown is shown, and it is assumed that "4444" is obtained as the card ID in step S100. In this case, in scenario 5, since card ID "4444" is not registered in cloud server 200, the first confirmation process (step S101) fails (No in step S102). In other words, the first confirmation process fails for reasons other than a communication error (No in step S106). Subsequently, the second confirmation process is performed (step S110). Since card ID "4444" is stored in storage unit 102, the second confirmation process succeeds (Yes in step S111). In this scenario, the third confirmation process is then performed (step S112). Since the token "Dd" is stored in storage unit 102 in association with card ID "4444", the third confirmation process attempts to obtain the user ID of the user registered in cloud server 200 in association with this token "Dd". Here, it is assumed that user ID "user4" is obtained from cloud server 200 in the third confirmation process. Since the user ID "user4" obtained from cloud server 200 matches the user ID "user4" stored in storage unit 102 in a manner associated with card ID "4444," the third confirmation process is successful in this case (Yes in step S113). Therefore, authentication is determined to be successful in this case (step S119). That is, although the failure of the first confirmation process was not primarily due to a communication error, the presence of card ID "4444" in storage unit 102 is confirmed, and the user ID "user4" associated with card ID "4444" in storage unit 102 is also registered in cloud server 200, so authentication is determined to be successful. The service utilization unit 105 then uses the token "Dd" stored in storage unit 102 to access the cloud service (step S120). This means that user U can now access the cloud service without having to enter login information for the cloud service.

[0080] Scenario 6

[0081] Scenario 6 is an example of a situation in which a card used by another user who previously had access to the image forming device 100 and the cloud service but is no longer currently eligible (for example, a card used by a retired employee) is distributed to user U, the target of authentication. Furthermore, in this scenario, it is assumed that the card ID of the card used by user U, the target of authentication, has not been registered by the administrator in cloud server 200. Furthermore, it is assumed that the user ID, card ID, token, and issuance time information of the aforementioned other user who previously used the card are stored in storage unit 102. Furthermore, it is assumed that user U has been registered as a legitimate user of the cloud service in cloud server 200, and that the aforementioned other user who previously used the card has had their user registration as a legitimate user of the cloud service deleted from cloud server 200. In addition, the process of situation 6 described below corresponds to the processing flow of reaching step S119 through the above-mentioned steps S100, S101, S102, S106, S110, S111, S112, S113, S114, S115, S116, and S118.

[0082] As a premise of scenario 6, it is assumed that the storage unit 102 stores Figure 6 The information shown is shown, and it is assumed that "4444" is obtained as the card ID in step S100. In this case, in scenario 6, since the card ID "4444" is not registered in cloud server 200, the first confirmation process (step S101) fails (No in step S102). In other words, the first confirmation process fails for reasons other than a communication error (No in step S106). Thereafter, the second confirmation process is implemented (step S110). Since the card ID "4444" is stored in storage unit 102, the second confirmation process is successful (Yes in step S111). In this scenario, the third confirmation process is also implemented thereafter (step S112). Since the token "Dd" is stored in storage unit 102 in a manner associated with card ID "4444", the third confirmation process attempts to obtain the user ID of the user registered in cloud server 200 in association with this token "Dd". Here, since the information of the user who previously held the card with the card ID "4444" has been erased from the cloud server 200, there is no user ID associated with the token "Dd" in the cloud server 200. Therefore, since the user ID cannot be obtained from the cloud server 200 in the third confirmation process, the third confirmation process fails (No in step S113). Therefore, the invalid information is deleted from the storage unit 102 (step S114). Figure 9As shown, the information related to the card ID "4444" is deleted from the storage unit 102. Thereafter, the authentication unit 104 prompts the user U to perform an authentication operation accompanied by the input of login information, and in response to this, the user U implements the input of login information (step S115). Here, it is assumed that the login to the cloud service is successful (yes in step S116). Along with this, the process of saving the information of the target user in the storage unit 102 is re-implemented (step S118). Thus, as Figure 10 As shown, the user ID "user5" and token "Ee" obtained from the cloud server 200 in a manner corresponding to the card ID "4444" and the issuance time of the token are stored in the storage unit 102. In this case, since the login to the cloud service is successful, it is determined that the authentication is successful (step S119). In this case, since the login to the cloud service is successful by inputting the login information, the service utilization unit 105 can utilize the cloud service (step S120).

[0083] Scenario 7

[0084] Scenario 7 illustrates a case where the authentication target user, user U, has a card ID that has not been registered with cloud server 200 by the administrator and whose information is not stored in storage unit 102. However, assume that user U, while not having his card ID registered with cloud server 200, is registered with cloud server 200 as a legitimate user of cloud services. In other words, the authentication target user, user U in this scenario, differs from the authentication target user, user U, in Scenario 2 described above, in that his card ID is not registered with cloud server 200. The process described below for Scenario 7 corresponds to the process flow that proceeds through steps S100, S101, S102, S106, S110, S111, S115, S116, and S118 described above, and reaches step S119.

[0085] As a premise of scenario 7, it is assumed that the storage unit 102 stores Figure 3, and it is assumed that "4444" is obtained as the card ID in step S100. At this time, in scenario 7, since the card ID "4444" is not registered in the cloud server 200, the first confirmation process (step S101) fails (No in step S102). That is, the first confirmation process fails for reasons other than a communication error (No in step S106). Thereafter, the second confirmation process is implemented (step S110). Since the card ID "4444" is not stored in the storage unit 102, the second confirmation process fails (No in step S111). Therefore, the authentication unit 104 prompts the user U to perform an authentication operation accompanied by the input of login information, and in response to this, the user U implements the input of login information (step S115). Here, it is assumed that the login to the cloud service is successful (Yes in step S116). Along with this, the process of saving the information of the target user in the storage unit 102 is re-implemented (step S118). Thus, as Figure 6 As shown, the user ID "user4" and token "Dd" obtained from the cloud server 200 in a manner corresponding to the card ID "4444" and the issuance time information of the token are stored in the storage unit 102. In this case, since the login to the cloud service is successful, it is determined that the authentication is successful (step S119). In this case, since the login to the cloud service is successful by inputting the login information, the service utilization unit 105 can utilize the cloud service (step S120).

[0086] Scenario 8

[0087] Case 8 is an example of a case where a notification of a message is implemented by the notification unit 107. As a premise of Case 8, it is assumed that the storage unit 102 stores Figure 11 , and the current date is December 23, 2023. In addition, it is assumed that the notification unit 107 implements the notification of the message when there is a token that has been issued for 80 days. At this time, in scenario 8, the notification unit 107 detects that 80 days have passed since the token of the user with the user ID "user4" was issued. For example, this situation is detected by the notification unit 107 confirming the issuance time point information of each user stored in the storage unit 102 when the power of the image forming device 100 is turned on. The notification unit 107 notifies the user with the user ID "user4" that the validity period of the token will soon end. Specifically, the notification unit 107 obtains the user's email address from the cloud server 200 and sends an email containing the above message to the obtained email address.

[0088] The above describes the embodiment. The image forming device 100 of this embodiment obtains card information from a target user's card and utilizes cloud services using a token stored in storage unit 102 in a manner associated with the obtained card information. Therefore, the target user does not need to perform authentication operations to utilize the cloud service. Consequently, the user can utilize the cloud service with greater convenience.

[0089] Furthermore, as described in Scenario 6 or Scenario 7 above, in this embodiment, when the target user performs an authentication operation for logging into the cloud service, and thus login to the cloud service via the image forming device 100 is successful, the storage processing unit 101 performs the following processing. Specifically, in this case, the storage processing unit 101 performs processing to store the card information obtained by the card information acquisition unit 103 and the token obtained from the cloud service accompanying the login in the storage unit 102 in a manner that establishes a correspondence. Therefore, for the target user, the card information and the token are automatically stored in the storage unit 102 in a manner that establishes a correspondence. Therefore, according to this embodiment, information used to utilize the cloud service without performing an authentication operation can be automatically stored in the storage unit 102.

[0090] Furthermore, in this embodiment, as shown in steps S119 and S120, when the authentication process performed by the authentication unit 104 is successful, the service utilization unit 105 utilizes the cloud service using the token stored in the storage unit 102 in a manner associated with the card information acquired by the card information acquisition unit 103. Therefore, it is possible to suppress unauthorized use of the cloud service using the token.

[0091] Furthermore, in this embodiment, as described in Scenario 1 or Scenario 2 above, authentication unit 104 determines that authentication is successful during the authentication process if the first confirmation process succeeds. Specifically, by confirming that a user corresponding to the card information obtained by card information acquisition unit 103 is registered in the cloud service, authentication is performed to verify that the target user is a legitimate user of image forming device 100. Therefore, in this embodiment, authentication processing can be performed in collaboration with cloud server 200 without requesting authentication for the cloud service.

[0092] Furthermore, in this embodiment, as described in Scenario 3 above, if the first confirmation process fails due to a communication error with the cloud server 200, the authentication unit 104 determines that authentication has succeeded if the second confirmation process succeeds. Therefore, even in the event of a communication error, authentication of the target user can be performed using information stored in the image forming device 100. This improves user convenience.

[0093] Furthermore, in this embodiment, as shown in Scenario 2 above, in the authentication process performed by the authentication unit 104, if the first confirmation process succeeds but the second confirmation process fails, the card information of the target user acquired by the card information acquisition unit 103 is stored in the storage unit 102. Thus, the information (i.e., the card information of the target user) that enables the second confirmation process to succeed for the target user, which was performed when the first confirmation process failed due to a communication error, is automatically stored in the storage unit 102. This improves user convenience.

[0094] Furthermore, in this embodiment, as shown in Scenario 5 above, even if the first confirmation process fails due to a factor other than a communication error with the cloud server 200, the authentication unit 104 will determine that authentication has succeeded if both the second and third confirmation processes are successful. Therefore, even if card information is not registered with the cloud server 200 due to an administrator's omission, it is still possible to infer whether the target user is a legitimate user. This improves user convenience.

[0095] Furthermore, in this embodiment, as shown in Scenario 6 above, the storage processing unit 101 performs the following processing. If the first confirmation process fails due to a factor other than a communication error with the cloud server 200, the second confirmation process succeeds, and the third confirmation process fails, the storage processing unit 101 deletes the information stored in the storage unit 102 in a manner that corresponds to the card information obtained by the card information acquisition unit 103. Therefore, information that should be invalidated, such as information on retired employees, is deleted, enabling more secure system operation.

[0096] Furthermore, in this embodiment, as shown in Scenario 8 above, when the remaining validity period of a token identified based on the issuance time information stored in storage unit 102 is less than a predetermined threshold, notification unit 107 notifies the user corresponding to the token. This improves user convenience. In particular, in this embodiment, since a new token is issued when a user who confirms the message utilizes a cloud service via image forming device 100, the expiration of the token's validity period can be suppressed. In other words, the period during which cloud services can be utilized can be extended without performing authentication operations.

[0097] Although the embodiment has been described above, the present invention is not limited to the above embodiment, and can be appropriately modified within a scope not departing from the gist of the invention.

[0098] A part or all of the above-mentioned embodiments may be described as the following supplementary notes, but are not limited to the following contents.

[0099] Note 1

[0100] An image forming apparatus is connected to a server providing a cloud service and comprises:

[0101] a storage unit that stores card information of a card distributed to a legitimate user of the image forming apparatus and a token that enables use of the cloud service in a corresponding relationship;

[0102] a card information acquisition unit configured to acquire card information of a card held by a target user who wishes to use the cloud service via the image forming apparatus;

[0103] A service utilizing unit utilizes the cloud service using the token stored in the storage unit in a manner associated with the acquired card information.

[0104] Note 2

[0105] The image forming apparatus as described in Supplementary Note 1, wherein:

[0106] When the object user performs an authentication operation for logging into the cloud service and the login to the cloud service via the image forming device is successful, the obtained card information and the token obtained from the cloud service accompanying the login are stored in the storage unit in a manner that establishes a corresponding relationship.

[0107] Note 3

[0108] The image forming apparatus as described in Supplementary Note 1 or 2, wherein:

[0109] further comprising an authentication unit that performs authentication processing to verify that the target user is a legitimate user of the image forming apparatus,

[0110] When the authentication process results in successful authentication, the service utilization unit utilizes the cloud service using the token stored in the storage unit in correspondence with the acquired card information.

[0111] Note 4

[0112] The image forming apparatus as described in Supplementary Note 3, wherein:

[0113] The authentication process includes a first confirmation process of obtaining user identification information of a legitimate user of the cloud service registered in the server in a manner associated with the obtained card information,

[0114] The authentication unit determines that the authentication is successful in the authentication process when the first confirmation process is successful.

[0115] Note 5

[0116] The image forming apparatus as described in Supplementary Note 4, wherein:

[0117] The authentication process includes the first confirmation process and the second confirmation process, wherein the second confirmation process is a process for confirming that the acquired card information is stored in the storage unit.

[0118] When the first confirmation process fails due to an error in communication with the server, the authentication unit determines that the authentication is successful in the authentication process if the second confirmation process succeeds.

[0119] Note 6

[0120] The image forming apparatus as described in Supplementary Note 5, wherein:

[0121] When the first confirmation process succeeds and the second confirmation process fails, the acquired card information is stored in the storage unit.

[0122] Note 7

[0123] The image forming apparatus as described in any one of Supplementary Notes 4 to 6, wherein

[0124] The storage unit stores the user identification information in a manner corresponding to the card information.

[0125] The authentication process includes:

[0126] the first confirmation process;

[0127] a second confirmation process of confirming that the acquired card information is stored in the storage unit;

[0128] The third confirmation process is to obtain user identification information of a legitimate user who is registered to the cloud service in the server in association with the token stored in the storage unit in a manner corresponding to the obtained card information, and to confirm that the obtained user identification information is consistent with the user identification information stored in the storage unit in a manner corresponding to the card information.

[0129] When the first confirmation process fails due to a factor other than an error in communication with the server, the authentication unit determines that authentication is successful in the authentication process if both the second confirmation process and the third confirmation process are successful.

[0130] Note 8

[0131] The image forming apparatus as described in Supplementary Note 7, wherein:

[0132] In the event that the first confirmation process fails due to a main reason other than an error in communication with the server, the second confirmation process succeeds, and the third confirmation process fails, the information stored in the storage unit in a manner corresponding to the obtained card information will be deleted.

[0133] Note 9

[0134] The image forming apparatus as described in any one of Supplementary Notes 1 to 8, wherein:

[0135] The token is valid from the time of issuance of the token until a predetermined time has passed.

[0136] The storage unit further stores issuance time information indicating the issuance time of the token in a manner corresponding to the token.

[0137] The image forming apparatus further includes a notification unit configured to notify a user corresponding to the token when the remaining validity period of the token specified based on the issuance time point information is less than a predetermined threshold value.

[0138] Note 10

[0139] An information processing method is an information processing method for an image forming apparatus connected to a server providing a cloud service, wherein:

[0140] storing card information of a card issued to a legitimate user of the image forming apparatus and a token enabling use of the cloud service in a manner of establishing a correspondence between the card information and the token;

[0141] acquiring card information of a card held by a target user who wants to use the cloud service via the image forming apparatus,

[0142] The cloud service is utilized using the token stored in correspondence with the acquired card information.

[0143] Note 11

[0144] A computer program product causes a computer of an image forming apparatus connected to a server providing a cloud service to execute the following steps:

[0145] a storage processing step of storing, in a storage unit, card information of a card issued to a legitimate user of the image forming apparatus and a token enabling utilization of the cloud service in a corresponding relationship;

[0146] a card information obtaining step of obtaining card information of a card held by a target user who wants to use the cloud service via the image forming apparatus;

[0147] The service utilizing step utilizes the cloud service using the token stored in the storage unit in a manner associated with the acquired card information.

[0148] Explanation of symbols

[0149] 1…information processing system; 100…image forming device; 101…storage processing unit; 102…storage unit; 103…card information acquisition unit; 104…authentication unit; 105…service utilization unit; 106…device function utilization unit; 107…notification unit; 150…printing unit; 151…scanner; 152…UI device; 153…network interface; 154…memory; 155…processor; 200…cloud server; N…network; U…user.

Claims

1. An image forming apparatus connected to a server providing a cloud service, and comprising: a storage unit that stores card information of a card distributed to a legitimate user of the image forming apparatus and a token that enables use of the cloud service in a corresponding relationship; a card information acquisition unit configured to acquire card information of a card held by a target user who wishes to use the cloud service via the image forming apparatus; A service utilizing unit utilizes the cloud service using the token stored in the storage unit in a manner associated with the acquired card information.

2. The image forming apparatus according to claim 1, wherein When the object user performs an authentication operation for logging into the cloud service and the login to the cloud service via the image forming device is successful, the obtained card information and the token obtained from the cloud service accompanying the login are stored in the storage unit in a manner that establishes a corresponding relationship.

3. The image forming apparatus according to claim 1 or 2, wherein: further comprising an authentication unit that performs authentication processing to verify that the target user is a legitimate user of the image forming apparatus, When the authentication process results in successful authentication, the service utilization unit utilizes the cloud service using the token stored in the storage unit in correspondence with the acquired card information.

4. The image forming apparatus according to claim 3, wherein: The authentication process includes a first confirmation process of obtaining user identification information of a legitimate user of the cloud service registered in the server in a manner associated with the obtained card information, The authentication unit determines that the authentication is successful in the authentication process when the first confirmation process is successful.

5. The image forming apparatus according to claim 4, wherein: The authentication process includes the first confirmation process and the second confirmation process, wherein the second confirmation process is a process for confirming that the acquired card information is stored in the storage unit. When the first confirmation process fails due to an error in communication with the server, the authentication unit determines that the authentication is successful in the authentication process if the second confirmation process succeeds.

6. The image forming apparatus according to claim 5, wherein: When the first confirmation process succeeds and the second confirmation process fails, the acquired card information is stored in the storage unit.

7. The image forming apparatus according to claim 4, wherein: The storage unit stores the user identification information in a manner corresponding to the card information. The authentication process includes: the first confirmation process; a second confirmation process of confirming that the acquired card information is stored in the storage unit; The third confirmation process is to obtain user identification information of a legitimate user who is registered to the cloud service in the server in association with the token stored in the storage unit in a manner corresponding to the obtained card information, and to confirm that the obtained user identification information is consistent with the user identification information stored in the storage unit in a manner corresponding to the card information. When the first confirmation process fails due to a factor other than an error in communication with the server, the authentication unit determines that authentication is successful in the authentication process if both the second confirmation process and the third confirmation process are successful.

8. The image forming apparatus according to claim 7, wherein: In the event that the first confirmation process fails due to a main reason other than an error in communication with the server, the second confirmation process succeeds, and the third confirmation process fails, the information stored in the storage unit in a manner corresponding to the obtained card information will be deleted.

9. The image forming apparatus according to claim 1, wherein: The token is valid from the time of issuance of the token until a predetermined time has passed. The storage unit further stores issuance time information indicating the issuance time of the token in a manner corresponding to the token. The image forming apparatus further includes a notification unit configured to notify a user corresponding to the token when the remaining validity period of the token specified based on the issuance time point information is less than a predetermined threshold value.

10. An information processing method for an image forming apparatus connected to a server providing a cloud service, wherein: storing card information of a card issued to a legitimate user of the image forming apparatus and a token enabling use of the cloud service in a manner of establishing a correspondence between the card information and the token; acquiring card information of a card held by a target user who wants to use the cloud service via the image forming apparatus, and The cloud service is utilized using the token stored in correspondence with the acquired card information.

11. A computer program product that causes a computer of an image forming apparatus connected to a server providing a cloud service to execute the following steps: a storage processing step of storing, in a storage unit, card information of a card issued to a legitimate user of the image forming apparatus and a token enabling utilization of the cloud service in a corresponding relationship; a card information obtaining step of obtaining card information of a card held by a target user who wants to use the cloud service via the image forming apparatus; The service utilizing step utilizes the cloud service using the token stored in the storage unit in a manner associated with the acquired card information.

Images