JP2020119036A - Information processing device, test method of client application, and program - Google Patents

Abstract

To solve a problem of a large load on an operator for conducting a communication test by operating each application on a terminal capable of executing a plurality of applications.SOLUTION: According to an embodiment, there is provided a communication unit. The communication unit notifies one or more client applications of start of a communication test with a resource server, acquires token information for communication with the resource server according to the request from the one or more client applications, provides the acquired token information in response to the request from the one or more client applications, and receives a result of the communication test from the one or more client applications.SELECTED DRAWING: Figure 1

Description

The present invention relates to an information processing apparatus for performing a communication test of one or more client applications, a client application test method, and a program.

The cloud service generally exposes the API (Application Programming Interface) of the Web service, and the function provided by the service from the terminal or another cloud service via the API can be used. A standard protocol called OAuth 2.0 has been established as a protocol for authentication and authorization in the use of this API. In OAuth2.0, authentication and authorization are performed by cooperation between the client terminal and other resource servers and the authorization server. The authenticated and authorized client uses the API by acquiring the authorization token from the authorization server and transmitting the authorization token.
In OAuth2.0, the flow of authorization protocol is called Grant Type. As a typical Grant Type, an Authorization Code Grant by which the user delegates the authority to the client and a Client Credentials Grant for the client to access its own resource are defined. It is considered that the terminal uses different Grant Type depending on the use case. For example, when the user who is the owner of the terminal cooperates with the cloud service when the terminal is operated, the Authorization Code Grant is selected. On the other hand, Client Credentials Grant is selected when detecting a change in the sensor or device of the terminal and linking with the cloud service. In this way, it is possible to support various use cases by using OAuth2.0.

In the case of a system where multiple client applications, each of which cooperates with a resource server, operate on one terminal, it is inefficient for each application to perform authentication/authorization processing for each, so a token that takes over authentication/authorization processing A configuration in which a provider application is arranged has been proposed (Patent Document 1). At that time, each client application acquires an access token from the token provider application after authentication by OAuth2.0 and links with the resource server.

At this time, the resource server that cooperates with a plurality of client applications differs for each application, and its domain may also differ. Whether or not each domain can be accessed depends on the network configuration and security settings of the terminal installation destination such as firewall settings. Therefore, in order for each client application on the terminal to properly cooperate with the resource server, it is necessary to confirm whether communication between the client application and the resource server is possible. Since the resource server of the communication partner is determined for each client application, this confirmation must be performed for each client application.

Patent No. 6066647

Therefore, in order to guarantee that each application can cooperate with the cloud service, the terminal user first registers the terminal in the authorization server in the token provider application. After that, the user needs to start the client applications one by one, conduct a communication test, and confirm the result. This work is a complicated work, and the work amount increases as the number of client applications increases, which becomes a burden on the user.

The present invention has been made in view of the above, and an object thereof is to automate a communication test of a client application and reduce a work load on a worker.

In order to achieve the above object, the present invention has the following configurations. That is, according to one aspect of the present invention, there is provided an information processing device having one or more client applications, the token provider application providing token information required for the one or more client applications to communicate with a resource server. Therefore, the following functions are provided, and the function is
A test start notification function for notifying the one or more client applications of the start of a communication test with the resource server,
An acquisition function for acquiring token information for communicating with the resource server in response to a request from the one or more client applications,
A test result receiving function for receiving the result of the communication test from the one or more client applications,
An information processing device is provided.

According to the present invention, the communication test of the client application can be automated to reduce the work load on the worker.

It is a figure showing an example of system composition. It is a figure which shows the hardware structural example of a terminal. It is a figure which shows the module structure of the token provider application 310 which concerns on 1st embodiment. It is a figure which shows the sequence of the communication test which concerns on 1st embodiment. It is a figure which shows the sequence of the communication test which concerns on 1st embodiment. It is a figure which shows the example of a display screen of a communication test start. It is a figure which shows the example of a display screen of a communication test result. It is a figure which shows the example of a display screen of a communication test result detail. It is a figure which shows the module structure of the token provider application 310 which concerns on 2nd embodiment. It is a figure which shows the sequence of the communication test which concerns on 2nd embodiment.

Embodiments of the present invention will be described below with reference to the drawings.
[System configuration]
The system according to the present embodiment is a diagram showing a configuration as shown in FIG.
The authorization server 100 is a server including an API for realizing terminal authentication/issuance of an access token.
The resource server 200 has an API published as a web service. The terminal 300 corresponds to, for example, a mobile terminal called a PC (Personal Computer), a smartphone, a multifunction peripheral, or the like.
The token provider application 310 authenticates the terminal by using the API published by the authorization server 100, and provides the client application 320 with an access token required for using the API of the resource server 200. The number of client applications 320 is not limited to one, and may be one or more.
The client application 320 uses the API published by the resource server 200 to provide the user with a service combined with the function provided by the client application 320.

The components of the system according to the present embodiment are realized by, for example, an information processing device having a configuration shown in FIG.
FIG. 2 shows an example of the hardware configuration of the authorization server 100, the resource server 200, and the terminal 300. Since the authorization server 100 and the resource server 200 have the same hardware configuration, they are shown as servers. Further, as the terminal 300, in addition to an information processing device such as a general-purpose personal computer, a multifunction peripheral such as an MFP or simply a device can be used. Since the personal computer may have the same hardware configuration as the server, its figure is omitted and the configuration of the multi-function peripheral device is shown in FIG. Regarding the server, the user interface is not shown because the server can interact with the terminal without the user interface. However, if the computer is used as a terminal, the terminal requires a user interface such as a keyboard, a pointing device, and a touch panel.

FIG. 2 shows a configuration example in which the terminal device 300 and the servers 100 and 200 are connected. Although the terminal device 300 and the servers 100 and 200 are connected via the network 220 in FIG. 2, the network 220 may include various types of networks such as LAN, WAN, and the Internet, or a combination thereof.

Hardware of Terminal (MFP) In FIG. 2, the terminal device 300 shows the hardware configuration of the MFP, which is an example of. The operation unit 210 has a display unit having a touch panel function, various hard keys, and the like, displays information to the user according to the data from the control unit 301, and inputs information according to the user's operation to the control unit 301. To do The scanner unit 212 reads an image on a document, creates image data of the image, and supplies the image data to the control unit 301. The printer unit 213 prints an image on a sheet based on the image data received from the control unit 301.

The control unit 301 is electrically connected to the operation unit 210, the scanner unit 212, and the printer unit 213, and is also connected to the network 220 via the network interface (I/F) 206. As a result, communication by a communication protocol such as TCP/IP is possible via the network 220. In the control unit 301, the CPU 201, the ROM 202, the RAM 203, the HDD 204, the operation unit I/F 205, the network I/F 206, the scanner I/F 207, the image processing unit 208, and the printer I/F 209 are connected via the system bus 211. The CPU 201 executes the boot program of the ROM 202, expands the OS and the control program stored in the HDD 204 into the RAM 203, and totally controls the terminal (MFP) 300 based on the program. This control also includes execution of a program for realizing the flowcharts described below. The ROM 202 stores the boot program of the MFP 110 and various data. The RAM 203 provides a work memory for the CPU 201 to operate and also an image memory for temporarily storing image data. The HDD 204 is a hard disk drive and stores an OS, various programs, and image data.

The operation unit I/F 205 is an interface unit for connecting the system bus 211 and the operation unit 210. The network I/F 206 is connected to the network 220 and the system bus 211, and inputs/outputs information via the network. The scanner I/F 207 controls an interface between the scanner unit 212 and the control unit 301. The image processing unit 208 performs image processing such as rotation, color conversion, and image compression/expansion processing on the image data input from the scanner unit 212 and the image data output to the printer unit 213. The printer I/F 209 receives the image data processed by the image processing unit 208, and controls the printing by the printer unit 213 according to the attribute data attached to this image data.

On the operation unit 210, for example, a registered shortcut (or GUI button) of the client application 320 is displayed on the initial screen after startup. The client application 320 is prepared for each resource server 200 of the access destination. When the shortcut is operated (pressed), the corresponding client application 320 is activated to access the set access destination (resource server).

Hardware of Server FIG. 2 also shows the hardware configurations of the authorization server 100 and the resource server 200 (these are collectively referred to as the server 100). The server 100 includes a CPU 251, a RAM 252, a ROM 253, a hard disk drive (HDD) 254, and a network I/F 255, which are communicably connected to each other via a system bus 256. The ROM 253 stores a boot program, and when the power is turned on, the CPU 251 reads this boot program and expands the OS, control program, etc. installed in the HDD 254 in the RAM 252. The functions of the server 100 are realized by the CPU 251 executing the program loaded in the RAM 252. The CPU 251 also communicates with other devices on the network, such as the terminal 300, which are connected via the network I/F 255. When the terminal 300 is a computer, it has a user interface such as a keyboard.

<First embodiment>
Below, the description concerning 1st embodiment is described.
[Module configuration]
FIG. 3 is a diagram showing an example of a module configuration of the token provider application 310 according to the first embodiment. Services are provided by executing each module. The token provider application 310 is installed in the terminal 300 and executed. Here, only the module according to the present embodiment is shown, and other modules are omitted.
The token provider application 310 includes an access token supply unit 311, a notification test start notification unit 312, a communication test result reception unit 313, and a communication test result display unit 314.
The access token supply unit 311 is a module for receiving a request from the client application 320 and acquiring an access token from the authorization server 100. It also functions as a token providing unit that provides the acquired access token to the client. Since the access token is information, it is also called access token information, authorization token information, or simply token information.
The communication test start notification unit 312 is a module for preparing an event to be registered by the client application 320, issuing the event according to a communication test start instruction, and notifying the registered client application 320. The communication test start instruction may be input as an independent instruction by the operator, or may be input by the operator or the like to register the terminal 300 in the authorization server 100 or received from the authorization server 100. It may be a response indicating that the registration of the terminal 300 has been completed, or a communication test instruction itself after completion of registration, or may be issued by using them as a trigger.

The communication test result receiving unit 313 is a module that receives a communication test completion result from each client application 320. The communication test result receiving unit 313 also has a function of processing the communication test result as a failure when the communication test start notification unit 312 does not receive a notification within a predetermined time after the communication test start instruction, and processes the communication test result as a failure.
The communication test result display unit 314 is a module that collects the communication test results received from the client application 320 by the communication test result receiving unit 313 and displays them on a display device such as an LCD of the operation unit 210.

[Processing sequence]
4A to 7 will be used to describe the steps necessary for the system according to the present embodiment to complete the communication test.
FIG. 4A shows processing when the client application 320 is installed in the terminal 300. Here, it is assumed that the token provider application 310 has already been installed before the client application 320 is installed.

In step S401, first, the client application 302 is installed in the terminal 300. At this time, the client application 320 registers itself as an event listener in the event provided by the token provider application 310 (step S402). As a result, the token provider application 310 can notify the client application 320. That is, in step S402, the client application 320 registers itself in the token provider application 310 as an event notification destination.

In the present embodiment, the sequence when the token provider application 310 actually performs the communication test in the series of terminal registration processes will be described using steps S403 to S408 of FIG. 4B. This procedure is executed when the terminal 300 needs to acquire the client credential from the authorization server 100. For example, this is the case when the terminal 300 is newly installed, when a new authorization server 100 is used, or when the client credential has expired.

In step S403, first, the token provider application 310 requests the authorization server 100 to register the terminal 300. If the process is successful, the authorization server 100 returns the client credential indicating that the terminal 300 is an authenticated device. As a result, the access token can be acquired in the subsequent processing.

In step S404, the token provider application 310 issues a communication test start event, and notifies the client application registered as the event listener in step S402 of the communication test start. In this embodiment, the client application 320 is notified of the start of the communication test.
The content of the communication test is unique to each client application 320. Also, the client application 320 can hold the URL of the resource server 200 that is the access destination, and the authority information when the authority is required to access the resource. The authorization information may be, for example, an access token, and once acquired, it can be retained and used as long as it is valid. When performing a communication test that requires access authority, the client application 320 requests the access token from the token provider application 310 in step S405.

Upon receiving the request, the token provider application 310 requests the access token from the authorization server 100 using the client credential acquired in step S403, and acquires the access token in response to the request (S406).

In step S407, the client application 320 performs a communication test with the resource server 200 and acquires the communication test result. The communication test may be performed between the resource server 200 and the client application 320 according to a predetermined procedure. The procedure for that purpose may be programmed in advance in each of the resource server 200 and the client application 320. When the response to the communication test is not returned within a certain time, the client application 320 times out and determines that the communication test has failed.

When the communication test is completed, the client application 320 notifies the token provider application 310 of the communication test result in step S408.

Finally, in step S409, the token provider application 310 receives the test results from all the client applications 320 notified of the start of the communication test, and displays the results on the display device.

With the above configuration and procedure, the communication test with the resource server 100 by the client application 320 can be performed without giving an instruction to the individual client application 320. To perform the communication test more efficiently, for example, the token provider application 310 may be installed before connecting the terminal 300 to the network 220, and then the client application 320 to be used may be installed. After that, if the terminal 300 is connected to the network and the terminal 300 is registered in the authorization server 100 by, for example, an explicit instruction from the operator, the communication test can be performed on all the installed client applications 320 according to the above procedure.

In the present embodiment, the processing from steps S403 to S404 is expressed by a series of sequences, but the processing is not limited to this. If the processing in step S404 is after step S403, another operation is triggered. May be started.
Further, although the client application 320 requests the access token from the token provider application 310 in step S405, this method is not necessarily required, and the token provider application 310 acquires the access token in advance, and the communication of step S404. A method of passing an access token when notifying the start of the test may be used.

Display Example FIG. 5 shows an example of the screen of the token provider application 310 displayed when starting the communication test in the present embodiment.
FIG. 5A is an example of a screen when a communication test is performed by using an operator's registration instruction of the terminal as a trigger. When the registration button 501 is pressed, after the token provider application 310 registers the terminal 300 in the authorization server 100, the communication test start notification is continuously issued to the client application 320 in the sequence of FIG. 4B. It is supposed to operate in line with it.

On the other hand, FIG. 5B is an example of a screen when the operator gives a communication test start instruction separately from the terminal registration instruction. In this example, the screen is displayed in a state where the processes up to step S403 are completed, and the process of step S404 is started by pressing the communication test execution button 502. The screen of FIG. 5B may be displayed after the registration of the terminal is completed on the screen of FIG. In the screen example of FIG. 5B, the communication test is optional. By pressing the button 503 (OK button or cancel button), the device registration can be completed without executing the communication test. In that case, the screen of FIG. 5(B) can be displayed after that to perform a communication test.

6 and 7 show examples of display screens of the token provider application 310 after the communication test is completed. FIG. 6 is an example of a screen showing an outline of the result, and the communication test result is displayed together with the terminal registration processing result. If there is a terminal that failed the communication test, a message indicating that fact is displayed. In addition to the display of FIG. 6, the ID of the failed terminal may be displayed. By further pressing the test result details button 601, the communication test result details as shown in the example of FIG. 7 can be viewed.

In the example of the communication test result detail screen of FIG. 7, the communication test result of each client application 320 can be browsed, and in the test in which the communication test has failed, the details of the error can be confirmed. A test retry button 701 is arranged on the detail screen, and when there is a failed communication test, the test may be executed again in response to the pressing. That is, steps S407 to S409 of FIG. 4 may be repeated. In this case, for example, a check box for selection may be provided for each client application listed on the detail screen of FIG. 7 so that the client application to be tested can be selected. Then, if the retest is instructed, the retest may be performed on the selected application. Alternatively, a check box or the like for selecting only the client application that failed the test may be provided, and if it is checked, the retest may be executed for the client application that failed the communication test.

As described above, according to the present embodiment, the operator can confirm the communication test result of each client application 320 in a series of flow from the registration operation of the terminal 300 on the token provider application 310.

<Second embodiment>
In the first embodiment, as shown in FIG. 4A, the client application 320 is assumed to be a client application (hereinafter referred to as an add-on application) installed after the token provider application 310 is installed. However, in the case of a client application (hereinafter referred to as a pre-installed application) installed before the token provider application 310 is installed in the terminal 300, the event described in step S402 cannot be registered, and The communication test cannot be performed in one embodiment. The second embodiment solves this problem.

[Module configuration]
FIG. 8 is a diagram showing an example of a module configuration of the token provider application 310 according to the second embodiment.
Since the description here is almost the same as that of FIG. 3 of the above-described embodiment, only different parts will be described below. The communication test instructing unit 801 is a module that instructs the client application 320, which is not registered as an event in the communication test start notifying unit 312, to perform a communication test. The communication test instructing unit 801 holds a list of client applications 320 to be tested in advance. When receiving a communication test start instruction, the communication test instructing unit 801 performs a communication test of the client application 320 according to the list and passes the result to the communication test result display unit 314. The list of client applications 320 to be tested, which the communication test instructing unit 801 holds, may be created by the token provider application 310, for example. In that case, for example, the token provider application 310 may acquire the information of the installed client application 320 by referring to the registry or the like when the token provider application 310 is installed, and create the information based on the acquired information. Alternatively, it may be created by the operator inputting the ID of the target client application on the user interface.

[Processing sequence]
In the present embodiment, the sequence when the token provider application 310 actually executes the communication test in the series of processes for terminal registration will be described using steps S901 to S907 in FIG. This processing sequence is executed in parallel with the processing sequence of FIG. As a result, regardless of the installation order of the token provider application 310 and the client application 320, automation of the communication test can be realized for the installed client application 320. However, the client credential may be acquired only once, whichever is performed first.
Since the description of the processing of FIG. 9 is almost the same as that of FIG. 4B of the above-described embodiment, only different parts will be described below.

In step S902, the token provider application 310 acquires the client application list of the designated test target that is held.
Then, in step S903, a communication test start process is instructed to all the client applications 320 in the client application list.

In step S907, upon completion of the communication test for all the client applications 320, the event notification communication test result is displayed together with the communication test result according to the processing sequence of FIG. 4B.
At this time, of the client applications 320 listed in the client application list, the result is not displayed for the client application 320 that is not installed or is invalidated.

According to the present embodiment, it is possible to perform a communication test on a plurality of installed client applications by a series of operations including not only add-on applications installed after the token provider application 310 but also pre-installed applications. .. Therefore, the investigation is simplified and the operation load on the operator is reduced.

Note that all the client applications 320 installed on the terminal 300 may be registered in the communication test instruction unit 801. In this case, for example, the token provider application 310 first creates a list of installed client applications by referring to the registry or the like in response to an instruction to carry out the communication test. Then, after that, the processing from step S903 shown in FIG. 9 is executed. By doing so, the communication test can be performed on all the installed client applications 320 by the configuration and procedure shown in the second embodiment.

[Other Examples]
The present invention supplies a program that implements one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in a computer of the system or apparatus read and execute the program. It can also be realized by the processing. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

100 authorization server, 200 resource server, 300 terminal, 310 token provider application, 320 client application, 300 terminal, 311 access token supply unit, 312 communication test start notification unit, 313 communication test result receiving unit, 314 communication test result display unit, 801 Communication test instruction unit

Claims (8)

An information processing apparatus having one or more client applications, comprising the following functions by having a token provider application that provides token information necessary for the one or more client applications to communicate with a resource server: And the function is
A test start notification function for notifying the one or more client applications of the start of a communication test with the resource server,
An acquisition function for acquiring token information for communicating with the resource server in response to a request from the one or more client applications,
A test result receiving function for receiving the result of the communication test from the one or more client applications,
An information processing device characterized in that The information processing apparatus according to claim 1, wherein
Further having a registration function for registering as an event notification destination in response to a request from the one or more client applications,
The information processing apparatus, wherein the test start notification function notifies the one or more client applications registered as the event notification destination of the start of the communication test with the resource server. The information processing apparatus according to claim 1 or 2, wherein
It further has a holding function for holding a list in which the one or more client applications to be tested are registered,
The information processing apparatus, wherein the test start notifying means notifies the one or more client applications registered in the list of the start of the communication test with the resource server. The information processing apparatus according to any one of claims 1 to 3,
The test start notification function notifies the start of the communication test by using a registration instruction of the information processing apparatus to the authorization server or a communication test instruction after completion of registration of the information processing apparatus received from the authorization server as a trigger. An information processing device characterized by the above. The information processing apparatus according to any one of claims 1 to 4,
An information processing apparatus further comprising an output means for outputting the result of the communication test. The information processing apparatus according to any one of claims 1 to 5,
An information processing apparatus that executes the one or more client applications. An information processing apparatus having one or more client applications, further comprising a token provider application for providing token information required for the one or more client applications to communicate with a resource server,
Test start notifying means for notifying the one or more client applications of the start of a communication test with the resource server,
Acquisition means for acquiring token information for communicating with the resource server in response to a request from the one or more client applications;
A program for functioning as a test result receiving means for receiving the result of the communication test from the one or more client applications. An information processing apparatus having one or more client applications, the client application executed by the information processing apparatus further having a token provider application for providing token information required for the one or more client applications to communicate with a resource server. The test method of
Notifying the one or more client applications of the start of a communication test with the resource server,
Acquiring token information for communicating with the resource server in response to a request from the one or more client applications,
A method of testing a client application, comprising receiving the result of the communication test from the one or more client applications.

Images