JP2020086691A - Authentication system - Google Patents

Abstract

To authenticate a user who has logged in to a client device.SOLUTION: An authentication system includes a client device and a server device communicatively connected to the client device. The client device acquires authentication information from a user that is used to authenticate the user who has logged in to the client device, transmits the authentication information to the server device, receives a token from the server as a result of successful user authentication, stores the authentication information and the received token in association with each other in a cache memory, determines whether the cash memory stores the authentication information and the received token when authenticating the user who has logged in to the client device, and authenticates locally the user using the authentication information that the cash memory has stored without transmitting the authentication information to the server when determining that the cache memory stores the authentication information and the token.SELECTED DRAWING: Figure 6

Description

The present disclosure relates to an authentication system including a client device and a server device.

There is known a technique in which a server device authenticates a user who has logged in to a client device in order for an electronic device to execute a job received from the client device.

Japanese Patent No. 4899882 JP 2006-164174 A

In the technology in which the server device authenticates the user who has logged in to the client device in order for the electronic device to execute the job received from the client device, it is desired to be more and more user-friendly.

An authentication system according to an aspect of the present disclosure,
A client device,
A server device communicatively connected to the client device;
Equipped with,
The client device is
Obtaining authentication information used to authenticate a user who has logged in to the client device from the user,
Sending the authentication information to the server device,
Receive a token from the server device as a result of successful authentication of the user,
Storing the authentication information and the received token in a cache memory in association with each other,
When authenticating a user who has logged in to the client device, it is determined whether the cache memory stores the authentication information and the token,
When it is determined that the cache memory stores the authentication information and the token, the authentication information stored in the cache memory is used to identify the user without transmitting the authentication information to the server device. Authenticate locally.

(1) According to this embodiment, when the client device determines that the cache memory stores the authentication information and the token, the authentication information stored in the cache memory is not transmitted to the server device. Authenticate the user locally with. As a result, the client device does not communicate with the server device at the time of authentication, so that it does not put pressure on the network, and it is possible to prevent the authentication from taking a long time as a result of pressing the network. In addition, even if a failure occurs in the server device (for example, server down) or a problem occurs in the network N (for example, excessive traffic due to narrow bandwidth), the client device can locally authenticate the user.

The client device is
If it fails to authenticate the user locally using the credentials,
Sending the authentication information to the server device,
Receive a token from the server device as a result of successful authentication of the user,
The authentication information and the received token are associated with each other and stored in the cache memory.

(2) According to this embodiment, when the client device fails to locally authenticate the user using the authentication information, the client device causes the server device to authenticate the user and associates the authentication information and the token received from the server device with each other. Stored in cache memory. With this, the client device can authenticate the user locally from the next time without performing communication with the server device at the time of authentication.

The client device is
Obtaining authentication information used to authenticate a user who has logged in to the client device from the user,
When it is determined that the cache memory stores the authentication information and the token, it is determined whether the reset time has elapsed,
If it is determined that the reset time has not elapsed,
Without sending the authentication information to the server device, using the authentication information stored in the cache memory, locally authenticates the user,
If it is determined that the reset time has elapsed,
Deleting the authentication information and the token from the cache memory,
Sending authentication information used to authenticate the user logged in to the client device to the server device,
Receive a token from the server device as a result of successful authentication of the user,
The authentication information and the received token are associated with each other and stored in the cache memory.

(3) According to the present embodiment, when the client device determines that the reset time has elapsed, the client device deletes the authentication information and the token from the cache memory, causes the server device to authenticate the user, and receives the authentication information and the server device. The tokens are stored in cache memory in association with each other. This allows the server device to authenticate the user every time the reset time elapses, thereby improving security. Also, the client device can authenticate the user locally from the next time without performing communication with the server device at the time of authentication.

Further comprising an electronic device communicatively connected to the client device,
The client device is
When the cache memory does not store the authentication information and the token, an authentication failure job which is a job including the authentication information and not including the token is transmitted to the electronic device,
The electronic device is
Receiving the authentication failure job from the client device,
Authenticating the user locally using the authentication information contained in the authentication failure job,
Upon successfully authenticating the user locally using the credentials, execute the authentication failure job,
If it fails to locally authenticate the user using the authentication information, the authentication failure job is not executed.

(4) According to this embodiment, even if the client device fails in the local authentication or the authentication using the server device, the electronic device can locally authenticate the user and execute the job. As a result, the electronic device can always execute a job of a user who is highly required to use the electronic device.

The client device is
When the cache memory stores the authentication information and the token, the authentication success job, which is a job including the authentication information and the token, is transmitted to the electronic device,
The electronic device is
Receiving the authentication successful job from the client device,
The authentication success job is executed.

(5) According to the present embodiment, when the client device succeeds in the local authentication or the authentication using the server device, the electronic device can execute the job without fail.

The electronic device is communicatively connected to the server device,
The client device is
When the cache memory stores the authentication information and the token, the authentication success job, which is a job including the authentication information and the token, is transmitted to the electronic device,
The electronic device is
Receiving the authentication successful job from the client device,
Transmitting the authentication information included in the authentication successful job to the server device,
When the result of successful authentication of the user is received from the server device, the authentication success job is executed,
If the result indicating that the user has been successfully authenticated is not received from the server device,
Authenticating the user locally using the authentication information contained in the successful authentication job,
If the user is successfully authenticated locally using the authentication information, the authentication success job is executed,
If it fails to locally authenticate the user using the authentication information, the authentication success job is not executed.

(6) According to the present embodiment, even if the client device succeeds in the local authentication or the authentication using the server device, the electronic device executes the local authentication or the server device again, so that the security is enhanced. You can

According to the present disclosure, in order for the electronic device to execute the job received from the client device, the server device can be made more and more user-friendly in the technique of authenticating the user who has logged in to the client device.

Note that the effects described here are not necessarily limited, and may be any effects described in the present disclosure.

1 illustrates an authentication system according to an embodiment of the present disclosure. 1 shows a hardware configuration of an image forming apparatus. The hardware structure of a server apparatus is shown. 3 shows a hardware configuration of a client device. The functional structure of an authentication system is shown. The 1st operation sequence of an authentication system is shown. 4 shows an operation flow of a client device. The operation|movement flow of a server apparatus is shown. The 2nd operation sequence of an authentication system is shown. 3 shows an operation flow of the image forming apparatus.

Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

1. Authentication system

FIG. 1 shows an authentication system according to an embodiment of the present disclosure.

The authentication system 1 includes an electronic device 10, a server device 20, and a client device 30.

The electronic device 10, the server device 20, and the client device 30 are communicatively connected to each other via a network N including the Internet.

The electronic device 10 is, for example, an image forming apparatus (Multifunction Peripheral, MFP). Hereinafter, the electronic device 10 will be referred to as the image forming apparatus 10.

The server device 20 is a so-called authentication server that authenticates a user who has logged in to the client device 30.

The client device 30 is, for example, a terminal device (personal computer, tablet computer, smartphone, etc.) used by a user. The client device 30 transmits a job (print job or the like) to the image forming apparatus 10 to execute the job.

2. Hardware configuration of image forming apparatus

FIG. 2 shows the hardware configuration of the image forming apparatus.

The image forming apparatus 10 includes a control circuit 11. The control circuit 11 includes a CPU 11 a (Central Processing Unit) that is a processor, a RAM 11 b (Random Access Memory), a ROM 11 c (Read Only Memory) that is a memory, a dedicated hardware circuit, and the like, and the entire image forming apparatus 10 includes Controls motion control. The CPU 11a loads the information processing program stored in the ROM 11c into the RAM 11b and executes it. The ROM 11c fixedly stores programs and data executed by the CPU 11a. The ROM 11c is an example of a non-transitory computer-readable recording medium.

The control circuit 11 includes an image reading unit 12 (image scanner), an image processing unit 14 (including a GPU (Graphics Processing Unit)), an image memory 15, an image forming unit 16 (printer), and an operating unit 17 (including a display unit 17a. It is connected to a large-capacity non-volatile storage device 18, such as a touch panel), an HDD (Hard Disk Drive) and an SSD (Solid State Drive), a facsimile communication unit 19, a network communication interface 13, and the like. The control circuit 11 controls the operation of each of the above-mentioned connected parts and transmits/receives signals or data to/from each part.

3. Server device hardware configuration

FIG. 3 shows the hardware configuration of the server device.

The server device 20 includes a CPU 21, a ROM 22, a RAM 23, a large-capacity non-volatile storage device 24 such as an HDD and an SSD, a network communication interface 25, an operating device 26 and a display device 27, and a bus 28 interconnecting them. Have.

The CPU 21, ROM 22, and RAM 23 form a control circuit 200. The CPU 21 loads the information processing program stored in the ROM 22 into the RAM 23 and executes it. The ROM 22 fixedly stores programs and data executed by the CPU 21. The ROM 22 is an example of a non-transitory computer-readable recording medium.

4. Hardware configuration of client device

FIG. 4 shows the hardware configuration of the client device.

The client device 30 includes a CPU 31, a ROM 32, a RAM 33, a large-capacity non-volatile storage device 34 such as an SSD, a network communication interface 35, an operating device 36, a display device 37 (touch panel), and a reading device 39 (imaging device such as a camera). And a bus 38 interconnecting them.

The CPU 31, the ROM 32, and the RAM 33 form a control circuit 300. The CPU 31 loads the information processing program stored in the ROM 32 into the RAM 33 and executes it. The ROM 32 fixedly stores programs and data executed by the CPU 31. The ROM 32 is an example of a non-transitory computer-readable recording medium.

5. Functional configuration of authentication system

FIG. 5 shows a functional configuration of the authentication system.

In the control circuit 300 of the client device 30, the CPU 31 operates as the client authentication unit 301 and the job generation unit 302 by loading the information processing program stored in the ROM 32 into the RAM 33 and executing it. The storage device 34 has a cache memory 310.

In the control circuit 200 of the server device 20, the CPU 21 operates as the server authentication unit 201 by loading the information processing program stored in the ROM 22 into the RAM 23 and executing it. The storage device 24 has an authentication list 210.

In the control circuit 11 of the image forming apparatus 10, the CPU 11a operates as the device authentication unit 101 and the job execution unit 102 by loading the information processing program stored in the ROM 11c into the RAM 11b and executing the information processing program. The storage device 18 has a user list 110.

The client authentication unit 301 of the client device 30 locally authenticates the user using the authentication information acquired from the user and the authentication information stored in the cache memory 310. The client authentication unit 301 also causes the server device 20 to authenticate the user using the authentication information acquired from the user.

The job generation unit 302 of the client device 30 generates a job (for example, a print job) to be executed by the image forming apparatus 10 and transmits the job to the image forming apparatus 10.

The server authentication unit 201 of the server device 20 authenticates the user using the authentication information received from the client device 30 or the image forming apparatus 10 and the authentication information stored in the authentication list 210.

The device authentication unit 101 of the image forming apparatus 10 locally authenticates the user using the authentication information acquired from the user and the authentication information stored in the user list 110. Also, the device authentication unit 101 causes the server device 20 to authenticate the user using the authentication information acquired from the user.

The job execution unit 102 of the image forming apparatus 10 executes the job received from the client device 30.

6. How the authentication system works

FIG. 6 shows a first operation sequence of the authentication system.

First, the premise of the operation will be described with reference to the upper part of FIG. The device authentication unit 101 of the image forming apparatus 10 receives an input from the user (administrator or the like) to the operation unit 17, and stores authentication information of a specific user in the user list 110. The users stored in the user list 110 are users who are highly likely to use the image forming apparatus 10, such as administrators.

The client authentication unit 301 of the client device 30 receives an input from the user (administrator or the like) to the operation device 36 and sets a reset time. The “reset time” is a length of time from when the cache memory 310 of the client device 30 stores the authentication information and the token (described later) to the reset (described later). The above is the premise of the operation.

"Authentication information" will be described. The authentication information is used to authenticate the user who has logged in to the client device 30. The authentication information includes a user identifier and a password. If the user identifier and the password included in the authentication information match the combination of the user identifier and the password associated with each other in advance, it means that the user has been successfully authenticated. On the other hand, if the user identifier and the password included in the authentication information do not match the combination of the user identifier and the password associated with each other in advance, it means that the user authentication has failed. In the following, for ease of understanding of the description, the term “combination of user identifier and password” is not used, but the term “authentication information” is used. Further, it is not described as “match or mismatch of the combination of the user identifier and the password”, but simply as “success or failure of the authentication information”. However, in the following description, “success or failure of authentication information” is based on “match or mismatch of combination of user identifier and password”.

FIG. 7 shows an operation flow of the client device.

The client authentication unit 301 of the client device 30 acquires the authentication information acquired by being input from the user (end user) who has logged in to the client device 30 via the operation device 36 (step S301). The client authentication unit 301 determines whether the cache memory 310 stores the authentication information acquired from the user (step S302).

The client authentication unit 301 of the client device 30 determines that the cache memory 310 does not store authentication information (step S302, NO). In this case, the client authentication unit 301 transmits the authentication information acquired from the user to the server device 20 (step S303).

FIG. 8 shows an operation flow of the server device.

The server authentication unit 201 of the server device 20 receives the authentication information from the client device 30 (step S201, YES). The server authentication unit 201 determines whether or not the authentication list 210 stores the received authentication information (step S202).

The server authentication unit 201 of the server device 20 determines that the authentication list 210 stores the received authentication information. In this case, the server authentication unit 201 determines that the authentication of the user identified by the user identifier included in the authentication information has succeeded (step S203, YES). On the other hand, when the authentication list 210 does not store the received authentication information, the server authentication unit 201 determines that the authentication of the user identified by the user identifier included in the authentication information has failed (step S203, NO). ..

When the user authentication succeeds (step S203, YES), the server authentication unit 201 of the server device 20 generates a token as a result indicating that the user authentication succeeds. The server authentication unit 201 transmits the token to the client device 30 as a result indicating that the user authentication is successful (step S204).

On the other hand, the server authentication unit 201 of the server device 20 does not generate a token if the user authentication fails (step S203, NO). The server authentication unit 201 transmits a result (not including a token) indicating that the user authentication has failed to the client device 30 (step S205).

By the way, the client authentication unit 301 of the client device 30 transmits the authentication information (step S303), but the server authentication unit 201 of the server device 20 may not receive the authentication information (step S201, NO). This is the case, for example, when a failure occurs in the server device 20 (for example, the server is down) or a failure occurs in the network N (for example, excessive traffic due to a narrow band). In this case, the client authentication unit 301 of the client device 30 does not receive the result from the server device 20 (step S304, NO) even though the authentication information is transmitted (step S303).

Referring to FIG. 7 again, the client authentication unit 301 of the client device 30 has a token (step S204) as a result indicating that the user authentication has succeeded or a result indicating that the user authentication has failed (not including the token). ) (Step S205) is received from the server device 20 (step S304, YES).

The client authentication unit 301 of the client device 30 receives the token (step S204) from the server device 20 as a result indicating that the user authentication is successful (step S305, YES). In this case, the client authentication unit 301 stores the authentication information acquired from the user (step S301) and the token received from the server device 20 in the cache memory 310 in association with each other (step S306).

On the other hand, the client authentication unit 301 of the client device 30 determines that the cache memory 310 stores the authentication information (step S302, YES). In the case where “the cache memory 310 stores the authentication information”, the client authentication unit 301 has the authentication information acquired from the user and the token received as a result of successful authentication of the user from the server device 20 in the past. , Which are associated with each other and stored in the cache memory 310 (step S306). In this case (YES in step S302), the client authentication unit 301 determines whether the reset time has elapsed (step S307).

When the client authentication unit 301 of the client device 30 determines that the reset time has elapsed (step S307, YES), the authentication information acquired from the user (step S301) and the token associated therewith are deleted from the cache memory 310. (Step S308). Then, the client authentication unit 301 executes the processes of steps S303 to S306. In other words, the client authentication unit 301 newly causes the server device 20 to execute user authentication. As a result, if the server device 20 succeeds in the authentication, the client authentication unit 301 stores the authentication information acquired from the user (step S301) and the token received from the server device 20 in the cache memory 310 in association with each other ( Step S306).

On the other hand, when the client authentication unit 301 of the client device 30 determines that the reset time has not elapsed (step S307, NO), it uses the authentication information (step S302, YES) stored in the cache memory 310, The user is locally authenticated (step S309). Specifically, the client authentication unit 301 determines whether or not the authentication information acquired from the user (step S301) and the authentication information stored in the cache memory 310 (step S302, YES) match. Step S310).

If the authentication information acquired from the user (step S301) does not match the authentication information stored in the cache memory 310 (step S302, YES), the client authentication unit 301 of the client device 30 locally authenticates the user. It is determined that the process has failed (step S310, NO). Then, the client authentication unit 301 executes the processes of steps S303 to S306. In other words, the client authentication unit 301 causes the server device 20 to execute user authentication. As a result, if the server device 20 succeeds in the authentication, the client authentication unit 301 stores the authentication information acquired from the user (step S301) and the token received from the server device 20 in the cache memory 310 in association with each other ( Step S306).

On the other hand, if the authentication information acquired from the user (step S301) and the authentication information stored in the cache memory 310 (step S302, YES) match, the client authentication unit 301 of the client device 30 locally determines the user. It is determined that the authentication is successful (step S310, YES).

FIG. 9 shows a second operation sequence of the authentication system.

The job generation unit 302 of the client apparatus 30 generates a job (for example, a print job) to be executed by the image forming apparatus 10 and sends it to the image forming apparatus 10.

When the client authentication unit 301 of the client device 30 receives the token as a result of the successful authentication of the user (YES in step S310, YES in step S305), the job generation unit 302 generates an authentication successful job and performs image formation. It transmits to the apparatus 10 (step S311). The “authentication success job” is a job including the authentication information (step S301) acquired from the user and the token. The token included in the authentication success job is the token stored in the cache memory 310 in association with the authentication information (step S302, YES) when the user is successfully authenticated locally (step S310, YES). is there. When the token included in the authentication success job is received from the server device 20 as a result indicating that the user has been successfully authenticated (step S305, YES), the token is stored in the cache memory 310 in association with the authentication information. It is the stored token (step S306).

On the other hand, when the client authentication unit 301 of the client device 30 receives the result of the user authentication failure (step S305, NO) and when the result is not received from the server device 20 (step S304, NO). explain. “When the result is not received from the server device 20 ”is, for example, when the server device 20 has a problem (for example, the server is down) or the network N has a problem (for example, the traffic is excessive due to a narrow band). Is. In these cases, the job generation unit 302 of the client device 30 generates an authentication failure job and sends it to the image forming apparatus 10 (step S312). The “authentication failed job” is a job that includes the authentication information (step S301) acquired from the user and does not include the token (the token value is null).

FIG. 10 shows an operation flow of the image forming apparatus.

The job execution unit 102 of the image forming apparatus 10 receives the job from the client device 30 (step S101). When the received job includes the token, the device authentication unit 101 of the image forming apparatus 10 determines that the job is an authentication successful job (step S311) (step S102, YES). On the other hand, when the received job does not include a token (the token value is null), the device authentication unit 101 determines that the job is an authentication failure job (step S311) (step S102, NO).

When the device authentication unit 101 of the image forming apparatus 10 determines that the authentication successful job has been received (step S102, YES), the device authentication unit 101 transmits the authentication information included in the authentication successful job to the server device 20 (step S103).

Referring back to FIG. 8, the server authentication unit 201 of the server device 20 receives the authentication information from the image forming apparatus 10 (step S201). The server authentication unit 201 determines whether or not the authentication list 210 stores the received authentication information (step S202).

The server authentication unit 201 of the server device 20 determines that the authentication list 210 stores the received authentication information. In this case, the server authentication unit 201 determines that the authentication of the user identified by the user identifier included in the authentication information has succeeded (step S203, YES). On the other hand, when the authentication list 210 does not store the received authentication information, the server authentication unit 201 determines that the authentication of the user identified by the user identifier included in the authentication information has failed (step S203, NO). ..

When the user authentication is successful (YES in step S203), the server authentication unit 201 of the server device 20 generates a result indicating that the user authentication is successful. The server authentication unit 201 transmits a result indicating that the user authentication is successful to the image forming apparatus 10 (step S204).

On the other hand, if the server authentication unit 201 of the server device 20 fails in the user authentication (NO in step S203), the server authentication unit 201 generates a result indicating that the user authentication has failed. The server authentication unit 201 transmits a result indicating that the user authentication has failed to the image forming apparatus 10 (step S205).

Referring back to FIG. 10, the device authentication unit 101 of the image forming apparatus 10 sends the result indicating that the user authentication has succeeded (step S204) or the result indicating that the user authentication has failed (step S205) to the server. It is received from the device 20 (step S104, YES).

The device authentication unit 101 of the image forming apparatus 10 receives the result indicating that the user authentication is successful from the server device 20 (step S105, YES). In this case, the job execution unit 102 of the image forming apparatus 10 executes the authentication success job (step S102, YES) received from the client device 30 (step S101) (step S106).

On the other hand, when the device authentication unit 101 of the image forming apparatus 10 determines that the authentication failure job is received (step S102, NO), and when the result is not received from the server device 20 (step S104, NO), A case where the result indicating that the user authentication has failed is received from the server device 20 (step S105, NO) will be described. “When the result is not received from the server device 20 ”is, for example, when the server device 20 has a problem (for example, the server is down) or the network N has a problem (for example, the traffic is excessive due to a narrow band). Is.

In these cases, the device authentication unit 101 of the image forming apparatus 10 locally authenticates the user by using the authentication information (described on the premise of the operation) stored in the user list 110 (step S107). Specifically, the device authentication unit 101 determines whether or not the authentication information included in the job (step S101) received from the client device 30 and the authentication information stored in the user list 110 match ( Step S108).

The device authentication unit 101 of the image forming apparatus 10 locally authenticates the user if the authentication information included in the job (step S101) received from the client device 30 matches the authentication information stored in the user list 110. It is determined that the operation has succeeded (step S108, YES). Then, the job execution unit 102 of the image forming apparatus 10 executes the job (step S101) received from the client device 30 (step S109).

On the other hand, if the authentication information included in the job (step S101) received from the client device 30 does not match the authentication information stored in the user list 110, the device authentication unit 101 of the image forming apparatus 10 identifies the user. It is determined that the local authentication has failed (step S108, NO). Then, the job execution unit 102 of the image forming apparatus 10 does not execute the job (step S101) received from the client device 30 (cancels the job) and deletes it (step S110).

7. Modification

According to the above-described embodiment, the electronic device 10, the server device 20, and the client device 30 are communicably connected to each other via the network N including the Internet.

Alternatively, the image forming apparatus 10 and the client apparatus 30 may be communicably connected to each other via a USB cable or the like, not via a network (not shown). The server device 20 and the client device 30 are communicably connected to each other via a network N including the Internet.

In this case, the image forming apparatus 10 and the server apparatus 20 are not connected and cannot communicate with each other. Therefore, the communication between the image forming apparatus 10 and the server apparatus 20 may be omitted from the above embodiment.

Specifically, when the device authentication unit 101 of the image forming apparatus 10 determines that the authentication successful job has been received (step S102, YES), the job execution unit 102 must execute the authentication successful job (step S106). ). Conversely speaking, steps S103 to S105 may be omitted.

8. Conclusion

(1) According to the present embodiment, when the client device 30 determines that the cache memory 310 stores the authentication information and the token, the client device 30 stores the authentication information in the cache memory 310 without transmitting the authentication information to the server device 20. Authenticate the user locally with the credentials provided. As a result, the client device 30 does not communicate with the server device 20 at the time of authentication, and thus does not put pressure on the network, and it is possible to prevent the authentication from taking a long time as a result of pressing the network. Further, even if the server device 20 has a problem (for example, the server is down) or the network N has a problem (for example, traffic is excessive due to a narrow band), the client device 30 can locally authenticate the user.

(2) According to the present exemplary embodiment, when the client device 30 fails to locally authenticate the user using the authentication information, the client device 30 causes the server device 20 to authenticate the user, and outputs the authentication information and the token received from the server device 20. , Are stored in the cache memory 310 in association with each other. As a result, the client device 30 can authenticate the user locally from the next time without performing communication with the server device 20 at the time of authentication.

(3) According to the present embodiment, when the client device 30 determines that the reset time has elapsed, the client device 30 deletes the authentication information and the token from the cache memory 310, causes the server device 20 to perform user authentication, The tokens received from 20 are stored in the cache memory 310 in association with each other. This allows the server device 20 to authenticate the user every time the reset time elapses, thereby improving security. Also, the client device 30 can authenticate the user locally from the next time without performing communication with the server device 20 at the time of authentication.

(4) According to this embodiment, even if the client device 30 fails in the local authentication or the authentication using the server device 20, the image forming device 10 can locally authenticate the user and execute the job. .. Accordingly, the image forming apparatus 10 can always execute a job of a user who needs to use the image forming apparatus 10, for example.

(5) According to the modified example, when the client device 30 succeeds in the local authentication or the authentication using the server device 20, the image forming apparatus 10 can execute the job without fail.

(6) According to the present embodiment, even if the client device 30 succeeds in the local authentication or the authentication using the server device 20, the image forming apparatus 10 executes the local authentication or the server device 20 again. Security can be improved.

Although each embodiment and each modified example of the present technology have been described above, the present technology is not limited to the above-described embodiments, and various modifications may be made without departing from the scope of the present technology. Of course.

Authentication system 1
Electronic device (image forming apparatus) 10
Server device 20
Client device 30
Device authentication unit 101
Job execution unit 102
User list 110
Server authentication unit 201
Authentication list 210
Client authentication unit 301
Job generation unit 302
Cache memory 310

Claims (6)

A client device,
A server device communicatively connected to the client device;
Equipped with,
The client device is
Obtaining authentication information used to authenticate a user who has logged in to the client device from the user,
Sending the authentication information to the server device,
Receive a token from the server device as a result of successful authentication of the user,
Storing the authentication information and the received token in a cache memory in association with each other,
When authenticating a user who has logged in to the client device, it is determined whether the cache memory stores the authentication information and the token,
When it is determined that the cache memory stores the authentication information and the token, the authentication information stored in the cache memory is used to identify the user without transmitting the authentication information to the server device. An authentication system that authenticates locally. The authentication system according to claim 1, wherein
The client device is
If it fails to authenticate the user locally using the credentials,
Sending the authentication information to the server device,
Receive a token from the server device as a result of successful authentication of the user,
An authentication system that stores the authentication information and the received token in a cache memory in association with each other. The authentication system according to claim 1 or 2, wherein
The client device is
Obtaining authentication information used to authenticate a user who has logged in to the client device from the user,
When it is determined that the cache memory stores the authentication information and the token, it is determined whether a reset time has elapsed,
If it is determined that the reset time has not elapsed,
Without sending the authentication information to the server device, using the authentication information stored in the cache memory, locally authenticates the user,
If it is determined that the reset time has elapsed,
Deleting the authentication information and the token from the cache memory,
Sending authentication information used to authenticate the user logged in to the client device to the server device,
Receive a token from the server device as a result of successful authentication of the user,
An authentication system that stores the authentication information and the received token in a cache memory in association with each other. The authentication system according to any one of claims 1 to 3,
Further comprising an electronic device communicatively connected to the client device,
The client device is
When the cache memory does not store the authentication information and the token, an authentication failure job which is a job including the authentication information and not including the token is transmitted to the electronic device,
The electronic device is
Receiving the authentication failure job from the client device,
Authenticating the user locally using the authentication information contained in the authentication failure job,
Upon successfully authenticating the user locally using the credentials, execute the authentication failure job,
An authentication system that does not execute the authentication failure job if it fails to locally authenticate the user using the authentication information. The authentication system according to claim 4, wherein
The client device is
When the cache memory stores the authentication information and the token, an authentication success job, which is a job including the authentication information and the token, is transmitted to the electronic device,
The electronic device is
Receiving the authentication successful job from the client device,
An authentication system that executes the authentication success job. The authentication system according to claim 4, wherein
The electronic device is communicatively connected to the server device,
The client device is
When the cache memory stores the authentication information and the token, the authentication success job, which is a job including the authentication information and the token, is transmitted to the electronic device,
The electronic device is
Receiving the authentication successful job from the client device,
Transmitting the authentication information included in the authentication successful job to the server device,
When the result of successful authentication of the user is received from the server device, the authentication success job is executed,
If the result indicating that the user has been successfully authenticated is not received from the server device,
Authenticating the user locally using the authentication information contained in the successful authentication job,
If the user is successfully authenticated locally using the authentication information, the authentication success job is executed,
An authentication system that does not execute the authentication success job if it fails to locally authenticate the user using the authentication information.

Images