JP2018116740A - Relay device, relay system, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable a user to access a service providing device without registering authority information, when the authority information used for accessing the service providing device is available.SOLUTION: A relay device 30 acquires from a client device 20, user's credit information registered in a service providing device 10A which serves as a target of an access request from the client device 20, and when a token required for accessing the service providing device 10A is not stored in a user management table or when the token is not available, the relay device uses the acquired credit information without using the token stored in the user management table, to access the service providing device 10A.SELECTED DRAWING: Figure 7

Description

  The present invention relates to a relay device, a relay system, and a program.

  A technique for accessing a server device via a relay device when using a server device on a network is known. For example, Patent Documents 1 and 2 describe techniques in which a multi-function device uploads data to a service providing device or downloads data from the service providing device in cooperation with a relay device.

JP 2012-113701 A JP 2012-118971 A

  An object of the present invention is to make it possible to access a service providing apparatus without registering the authority information when the authority information used for accessing the service providing apparatus is not valid.

  According to the first aspect of the present invention, a storage unit that stores authority information used for access to a service providing apparatus, and user identification information registered in a service providing apparatus that is a target of an access request from a client apparatus If the authority information stored in the first acquisition unit and the storage unit acquired from the client device is not valid, the first information is used without using the authority information used when the authority is valid. There is provided a relay system including an access unit that accesses the target service providing apparatus using the identification information acquired by the acquisition unit.

  The invention according to claim 2 is used for displaying a screen for accepting input of the identification information when the authority information stored in the storage unit is not valid in the relay system according to claim 1. The information processing apparatus further includes a transmission unit configured to transmit screen information to the client device, and the first acquisition unit receives the identification information input to the screen displayed using the screen information in the client device from the client device. get.

  The invention according to claim 3 is the relay system according to claim 1 or 2, wherein the storage unit further stores state information indicating a state of the authority information, and the authority information stored in the storage unit When is not valid, the information processing apparatus further includes an update unit that updates the state information stored in the storage unit.

  The invention according to claim 4 is stored in a storage unit and a first acquisition unit that acquires, from the client device, user identification information registered in a service providing device that is a target of an access request from the client device. If the authority information used to access the target service providing apparatus is not valid, the first acquisition unit is used without using the authority information used when the authority information is valid. A relay device is provided that includes an access unit that accesses the target service providing device using the identification information acquired by the above.

  According to a fifth aspect of the present invention, in the relay device according to the fourth aspect, when access is permitted by the target service providing device, data exchanged between the service providing device and the client device is performed. A relay unit for relaying is further provided.

  According to a sixth aspect of the present invention, the computer stores the user identification information registered in the service providing apparatus that is the target of the access request from the client apparatus, and stored in the storage unit. If the authority information used to access the target service providing device is not valid, the target information is used by using the acquired identification information without using the authority information used when it is valid. A program for executing the step of accessing the service providing apparatus is provided.

  According to the first to sixth aspects of the present invention, when the authority information used for accessing the service providing apparatus is not valid, the service providing apparatus can be accessed without registering the authority information.

It is a figure which shows the whole structure of a relay system. It is a figure which shows the hardware constitutions of a client apparatus. It is a figure which shows the hardware constitutions of a relay apparatus. It is a figure which shows an example of a user management table. It is a figure which shows the hardware constitutions of the authority registration apparatus. It is a figure which shows the function structure of a relay system. It is a sequence diagram which shows operation | movement when the token is not registered into the relay apparatus. It is a figure which shows an example of a service list screen. It is a sequence diagram which shows operation | movement when the expiration date of the token registered into the relay apparatus has expired. It is a figure which shows an example of a user management table. It is a figure which shows an example of a service list screen. It is a figure which shows an example of the user management table after an update. It is a figure which shows an example of a service list screen. FIG. 10 is a sequence diagram illustrating an operation when a token registered in a relay device has expired when performing a skewer search. It is a figure which shows an example of a search screen. It is a sequence diagram which shows the process which registers a token with a relay apparatus. It is a figure which shows an example of a service list screen. It is a figure which shows the function structure of the relay system which concerns on a modification.

1. Configuration (1) Overall Configuration of System FIG. 1 is a diagram showing an overall configuration of a relay system 1 according to the present embodiment. The relay system 1 includes service providing apparatuses 10A, 10B, and 10C, a client apparatus 20, a relay apparatus 30, and an authority registration apparatus 40. In the following description, when it is not necessary to distinguish between the service providing apparatuses 10A, 10B, and 10C, these are collectively referred to as “service providing apparatus 10”.

  The service providing apparatus 10, the client apparatus 20, the relay apparatus 30, and the authority registration apparatus 40 are connected via a communication line 2 such as the Internet. The client device 20 and the authority registration device 40 may be connected to the communication line 2 via another communication line such as a LAN (Local Area Network).

  The service providing apparatus 10 provides various services such as a service for storing data. This service may be a so-called cloud service. In order to access the service providing apparatus 10, a token indicating the right to access the service providing apparatus 10 or credit information that can be provided by a correct user is required.

  The client device 20 is an image processing device, for example, and is used when a user uses a service provided from the service providing device 10. In addition to the scanner function, the client device 20 may have a plurality of functions such as a copy function, a print function, and a facsimile function.

  The relay device 30 has a function of relaying data exchange between the client device 20 or the authority registration device 40 and the service providing device 10. By using the relay device 30 to exchange data, the service provided from the plurality of service providing devices 10 can be used simply by logging in to the relay device 30.

  The authority registration device 40 is, for example, a personal computer, and performs processing for registering the token issued from the service providing device 10 in the relay device 30 in cooperation with the relay device 30. The client device 20 may not have a configuration necessary for executing this process. Therefore, the authority registration device 40 performs this process instead of the client device 20.

(2) Hardware Configuration of Client Device 20 FIG. 2 is a diagram illustrating a hardware configuration of the client device 20. The client device 20 includes a control unit 21, a communication unit 22, an operation unit 23, a display unit 24, a storage unit 25, an image reading unit 26, and an image forming unit 27.

  The control unit 21 includes, for example, a CPU (Central Processing Unit) and a memory, and controls each unit of the client device 20. The CPU executes a program stored in the memory or the storage unit 25. The memory includes, for example, a ROM (Read Only Memory) and a RAM (Random Access Memory). The ROM stores programs and data in advance. The RAM temporarily stores programs and data, and is used as a work area when the CPU executes the programs.

  The communication unit 22 is a communication interface connected to the communication line 2. The communication unit 22 communicates with the relay device 30 via the communication line 2. The operation unit 23 includes, for example, various keys and a touch panel, and inputs information corresponding to a user operation to the control unit 21. The display unit 24 includes a liquid crystal display, for example, and displays various types of information. The storage unit 25 includes, for example, a hard disk, and stores various programs and data used by the control unit 21. This program includes a Web browser.

  The image reading unit 26 includes, for example, an image scanner and reads an image of a document to generate image data. The image forming unit 27 includes an electrophotographic print engine, for example, and forms an image corresponding to the image data on a medium such as paper.

(3) Hardware Configuration of Relay Device 30 FIG. 3 is a diagram illustrating a hardware configuration of the relay device 30. The relay device 30 includes a control unit 31, a communication unit 32, and a storage unit 33.

  The control unit 31 includes, for example, a CPU and a memory, and controls each unit of the relay device 30. The CPU executes a program stored in the memory or the storage unit 33. The memory includes, for example, a ROM and a RAM. The ROM stores programs and data in advance. The RAM temporarily stores programs and data, and is used as a work area when the CPU executes the programs.

  The communication unit 32 is a communication interface connected to the communication line 2. The communication unit 32 communicates with the client device 20, the service providing device 10, and the authority registration device 40 via the communication line 2. The storage unit 33 includes a hard disk, for example, and stores various programs and data used by the control unit 31. This program includes Web server software. In addition, the storage unit 33 stores a user management table 331 used for managing information about users.

  FIG. 4 is a diagram illustrating an example of the user management table 331. In the user management table 331, account information, a token of each service providing apparatus 10, and a state of this token are stored in association with each other. The account information is information necessary for logging in to the relay device 30. The account information includes a user ID and a password. The user ID may be a user name or an email address assigned to the user. The token is information indicating the authority to access the service providing apparatus 10. The token is issued for each user and stored in the user management table 331. The token status is information indicating whether or not the token is registered or the validity of the token. For example, when the token is stored in the user management table 331, the state of “present” is stored, and when the token is not stored in the user management table 331, the state of “none” is stored. . Further, when the token has expired, a state of “revocation” is stored.

  In the user management table 331 shown in FIG. 4, in association with the user ID “User01@aaa.example.com”, the token state “none” of the service providing apparatus 10A and the token state “none” of the service providing apparatus 10B are associated. And the token status “none” of the service providing apparatus 10C is stored. This indicates that the token of the user with the user ID “User01@aaa.example.com” for accessing the service providing apparatuses 10A to 10C is not registered in the relay apparatus 30.

(4) Hardware Configuration of Authority Registration Device 40 FIG. 5 is a diagram illustrating a hardware configuration of the authority registration device 40. The authority registration device 40 includes a control unit 41, a communication unit 42, an operation unit 43, a display unit 44, and a storage unit 45.

  The control unit 41 includes, for example, a CPU and a memory, and controls each unit of the authority registration device 40. The CPU executes a program stored in the memory or the storage unit 45. The memory includes, for example, a ROM and a RAM. The ROM stores programs and data in advance. The RAM temporarily stores programs and data, and is used as a work area when the CPU executes the programs.

  The communication unit 42 is a communication interface connected to the communication line 2. The communication unit 42 communicates with the relay device 30 and the service providing device 10 via the communication line 2. The operation unit 43 includes, for example, a keyboard and a mouse, and inputs information corresponding to a user operation to the control unit 41. The display unit 44 includes, for example, a liquid crystal display and displays various types of information. The storage unit 45 includes a hard disk, for example, and stores various programs and data used by the control unit 41. This program includes a Web browser.

(5) Functional Configuration of System FIG. 6 is a diagram illustrating a functional configuration of the relay system 1. The client device 20 has a function called a client unit 211. This function is realized, for example, when the CPU of the control unit 21 executes a program. The client unit 211 performs processing necessary to receive a service provided from the service providing apparatus 10.

  The relay device 30 has functions of an authentication unit 311, a relay unit 312, a first acquisition unit 313, an access unit 314, a registration processing unit 315, and a second acquisition unit 316. These functions are realized, for example, when the CPU of the control unit 31 executes a program. The authentication unit 311 authenticates the user with reference to the user management table 331 in response to a login request from the client device 20. The relay unit 312 relays data exchange between the client device 20 or the authority registration device 40 and the service providing device 10.

  The first acquisition unit 313 acquires user identification information registered in the service providing apparatus 10 that is the target of an access request from the client apparatus 20. This identification information is user's credit information including, for example, a user ID and a password. If the authority information necessary for access to the target service providing apparatus 10 is not stored in the storage unit 33, the access unit 314 replaces the authority information stored in the storage unit 33 with the first acquisition. The target service providing apparatus 10 is accessed using the identification information acquired by the unit 313. This authority information is, for example, a token. The registration processing unit 315 performs token registration processing in response to a request from the client device 20. The second acquisition unit 316 acquires authority information indicating authority to access the service providing apparatus 10 from the service providing apparatus 10.

  The authority registration device 40 has functions of an authority registration unit 411, a third acquisition unit 412, and a transmission unit 413. These functions are realized, for example, when the CPU of the control unit 41 executes a program. The authority registration unit 411 performs processing for registering authority information indicating authority to access the service providing apparatus 10 in the relay apparatus 30 in cooperation with the relay apparatus 30. The third acquisition unit 412 acquires permission information permitting acquisition of authority information indicating authority to access the service providing apparatus 10 from the service providing apparatus 10. This permission information is, for example, a code that permits token acquisition. The transmission unit 413 transmits the permission information acquired by the third acquisition unit 412 to the relay device 30.

  Note that data exchange among the client device 20, the relay device 30, the service providing device 10, and the authority registration device 40 may be performed according to HTTP (HyperText Transfer Protocol). Further, the relay device 30 and the service providing device 10 may provide a screen displayed on the client device 20 or the authority registration device 40 by the function of the Web server. In this case, the client device 20 and the authority registration device 40 display this screen by the function of the Web browser.

2. Operation Next, the operation of the relay system 1 will be described. In the relay system 1, the user uses the client device 20 to store data in the service providing device 10 via the relay device 30 and acquire data from the service providing device 10. At this time, the relay device 30 accesses the service providing device 10 using a token registered in advance. However, when a token necessary for access by the service providing apparatus 10 is not registered in the relay apparatus 30 such as when a token is not registered in the relay apparatus 30 or when a token registered in the relay apparatus 30 has expired. There is. Here, the operation of the relay system 1 in such a case will be described.

(1) When token is not registered First, an operation when a token is not registered in the relay device 30 will be described. FIG. 7 is a sequence diagram showing an operation when no token is registered in the relay device 30. Here, it is assumed that the relay device 30 and the service providing devices 10A, 10B, and 10C are registered in cooperation with each other in advance.

  When using a service provided from the service providing apparatus 10, the user first logs in to the relay apparatus 30 using the client apparatus 20. Specifically, the user inputs account information for logging in to the relay device 30 by an operation using the operation unit 23. For example, when the account information for logging in to the relay device 30 is the user ID “User01@aaa.example.com” and the password “password01”, the user ID and password are input.

  In step S <b> 101, the client unit 211 of the client device 20 transmits an authentication request including account information input by a user operation to the relay device 30 via the communication unit 22. The relay device 30 receives this authentication request via the communication unit 32.

  In step S <b> 102, the authentication unit 311 of the relay device 30 performs user authentication in response to the authentication request received from the client device 20. Specifically, the authentication unit 311 performs user authentication based on whether the account information included in the authentication request is stored in the user management table 331. When the account information included in the authentication request is stored in the user management table 331, the user authentication is successful. On the other hand, when the account information included in the authentication request is not stored in the user management table 331, user authentication fails. In this example, since the set of the user ID “User01@aaa.example.com” and the password “password01” included in the authentication request is stored in the user management table 331 shown in FIG. 4, the user authentication is successful. In this case, the authentication unit 311 stores this user ID in the memory. The user ID stored in the memory is used as the user ID of the login user.

  In step S <b> 103, the authentication unit 311 transmits the authentication result of the user authentication performed in step S <b> 102 to the client device 20 via the communication unit 32. The client device 20 receives this authentication result via the communication unit 22. If the client apparatus 20 receives the authentication result indicating that the user authentication is successful, the process proceeds to step S104. On the other hand, when receiving an authentication result indicating that the user authentication has failed, the client device 20 ends this processing without performing the subsequent processing. In this example, the client device 20 proceeds to step S104 in order to receive an authentication result indicating that the user authentication is successful.

  In step S <b> 104, the client unit 211 of the client device 20 transmits a service list acquisition request indicating a list of services provided from the service providing device 10 registered in advance to the relay device 30 via the communication unit 22. . The relay device 30 receives this acquisition request via the communication unit 32.

  In step S <b> 105, the relay unit 312 of the relay device 30 creates a service list in response to the acquisition request received from the client device 20. In this service list, identification information of all the service providing apparatuses 10 registered in cooperation with each other and the status of the login user's token for accessing these service providing apparatuses 10 are described.

  In this example, since the relay device 30 is registered in cooperation with the service providing devices 10A to 10C in advance, identification information of the service providing devices 10A to 10C is described in the service list. In this example, in the user management table 331 shown in FIG. 4, the token status of the service providing apparatus 10A “None” is associated with the user ID “User01@aaa.example.com” of the login user stored in the memory. ”, The token state“ None ”of the service providing apparatus 10B and the token state“ None ”of the service providing apparatus 10C are stored, and the state of these tokens is described in the service list.

  In step S <b> 106, the relay unit 312 transmits the service list created in step S <b> 105 to the client device 20 via the communication unit 32. The client device 20 receives this service list via the communication unit 22.

  In step S <b> 107, the client unit 211 of the client device 20 displays the service list screen 241 on the display unit 24 based on the service list received from the relay device 30.

  FIG. 8 is a diagram illustrating an example of the service list screen 241. On the service list screen 241, the service list received from the relay device 30 is displayed. The user selects the service providing apparatus 10 that provides a desired service from the service list. For example, when the user wants to use a service provided from the service providing apparatus 10 </ b> A, the user selects the service providing apparatus 10 </ b> A by an operation using the operation unit 23.

  The service list screen 241 displays an input field C1 used for inputting credit information. When the token status of the selected service providing apparatus 10 is “None”, the user inputs the credit information registered in advance in the service providing apparatus 10 into the input field C1 by an operation using the operation unit 23. To do. In this example, since the token status of the service providing apparatus 10A is “None”, the user can enter the credit information registered in advance in the service providing apparatus 10A in the input field C1 by the operation using the operation unit 23. input. For example, when the user's credit information registered in the service providing apparatus 10A is the user ID “user01@service_a.example.com” and the password “passwordA1”, the user ID and password are input in the input field C1. .

  The service list screen 241 displays buttons used to instruct execution of various processes requested to the service providing apparatus 10. For example, when the user wants to browse a list of data available to the user stored in the service providing apparatus 10 </ b> A, the user presses the list display button B <b> 1 using the operation unit 23. As described above, when the list display button B1 is pressed after the credit information is input, the client device 20 proceeds to step S108.

  In step S <b> 108, the client unit 211 transmits a file list acquisition request of the service providing apparatus 10 selected on the service list screen 241 to the relay apparatus 30 via the communication unit 22. This acquisition request includes the identification information of the service providing apparatus 10 selected on the service list screen 241 and the credit information input in the input field C1. In this example, the acquisition request includes the identification information of the service providing apparatus 10A, the user ID “user01@service_a.example.com”, and the password “passwordA1”. The relay device 30 receives this acquisition request via the communication unit 32. The first acquisition unit 313 acquires the credit information from the acquisition request, and stores the credit information in a memory whose stored contents are deleted by turning off the power of the RAM or the like.

  In step S109, the access unit 314 of the relay device 30 transfers the acquisition request received from the client device 20 to the target service providing device 10 via the communication unit 32. At this time, the access unit 314 accesses the service providing apparatus 10 using the credit information stored in the memory. In this example, since the acquisition request includes the identification information of the service providing apparatus 10A, the user ID “user01@service_a.example.com”, and the password “passwordA1”, the service providing apparatus 10A is used by using the user ID and password. Is accessed.

  When accessed from the relay device 30 using the credit information, the service providing device 10A determines whether to permit access from the relay device 30 based on whether or not the credit information is registered. If the credit information included in the acquisition request is registered, the service providing apparatus 10A permits access from the relay apparatus 30 and proceeds to step S110. On the other hand, when the credit information included in the acquisition request is not registered, the service providing apparatus 10A denies access from the relay apparatus 30 and ends the process without performing the subsequent processes. In this example, since the user ID “user01@service_a.example.com” and the password “passwordA1” included in the acquisition request are registered in the service providing apparatus 10A, the service providing apparatus 10A accesses the relay apparatus 30. Allow and proceed to step S110.

  In step S110, the service providing apparatus 10A creates a file list in response to the acquisition request received from the relay apparatus 30. In the file list, identification information of all data usable by the user among the data stored in the service providing apparatus 10A is described. In this example, the file list describes identification information of all data that can be used by the user with the user ID “user01@service_a.example.com”. The data that can be used by the user is determined based on, for example, attribute information added to the data. For example, when the user ID “user01@service_a.example.com” or a user ID corresponding thereto is added to the data, this data is determined as data that can be used by the user.

  In step S111, the service providing apparatus 10A transmits the file list created in step S110 to the relay apparatus 30. The relay device 30 receives this file list via the communication unit 32.

  In step S112, the relay unit 312 of the relay device 30 transfers the file list received from the service providing device 10A to the client device 20 via the communication unit 32. The client device 20 receives this file list via the communication unit 22.

  In step S <b> 113, the client unit 211 of the client device 20 displays a file list screen on the display unit 24 based on the file list received from the relay device 30. A file list is displayed on the file list screen.

  Thereafter, when data is selected from the file list by the user's operation, the client apparatus 20 transmits the selected data to the service providing apparatus via the relay apparatus 30 in the same procedure as steps S108 to S112 described above. Acquired from 10A. At this time, the access unit 314 of the relay device 30 accesses the service providing device 10A using the credit information stored in the memory in step S108 described above. The data acquired from the service providing apparatus 10A is used for image formation by the image forming unit 27, for example.

(2) When the token has expired Next, the operation when the token registered in the relay device 30 has expired will be described. FIG. 9 is a sequence diagram illustrating an operation in the case where the token registered in the relay device 30 has expired. Here, it is assumed that the storage unit 33 stores a user management table 331 shown in FIG. 10 instead of the user management table 331 shown in FIG.

  In the user management table 331 shown in FIG. 10, the token status “present” of the service providing apparatus 10A and the token status “present” of the service providing apparatus 10B are associated with the user ID “User01@aaa.example.com”. And the token status “present” of the service providing apparatus 10C is stored. This indicates that all the tokens of the user with the user ID “User01@aaa.example.com” for accessing the service providing apparatuses 10A to 10C are registered in the relay apparatus 30.

  The processes in steps S201 to S207 shown in FIG. 9 are the same as the processes in steps S101 to S107 described above. However, in step S205, a service list is created based on the user management table 331 shown in FIG. In the user management table 331 shown in FIG. 10, the token status “present” of the service providing apparatus 10A is associated with the user ID “User01@aaa.example.com” of the login user stored in the memory, and the service providing apparatus. The token state “present” of 10B and the token state “present” of service providing apparatus 10C are stored. In this case, the status of these tokens is described in the service list.

  In step S207, a service list screen 241 is displayed based on the service list. FIG. 11 is a diagram showing an example of the service list screen 241 displayed at this time. In the example illustrated in FIG. 11, the service providing apparatus 10A is selected. However, since the token state of the service providing apparatus 10A is “present”, the user does not input credit information at this stage.

  In step S <b> 208, the client unit 211 transmits a file list acquisition request of the service providing apparatus 10 selected on the service list screen 241 to the relay apparatus 30 via the communication unit 22. This acquisition request includes identification information of the service providing apparatus 10 selected on the service list screen 241. In this example, since credit information is not input on the service list screen 241, unlike the above-described step S108, the acquisition request does not include credit information.

  In step S209, the access unit 314 of the relay device 30 transfers the acquisition request received from the client device 20 to the target service providing device 10 via the communication unit 32. Here, unlike step S109 described above, the access unit 314 reads the login user token for accessing the service providing apparatus 10 from the user management table 331, and accesses the service providing apparatus 10 using the read token. . In this example, the token A1 of the service providing apparatus 10A stored in association with the user ID “User01@aaa.example.com” of the login user stored in the memory is read from the user management table 331 illustrated in FIG. Then, the service providing apparatus 10A is accessed using this token A1.

  When accessed from the relay device 30 using the token A1, the service providing device 10A determines whether or not to permit access from the relay device 30 based on whether or not the token A1 is valid. The token has an expiration date. For example, when the token A1 is valid, such as when the token A1 is within the expiration date, the service providing apparatus 10A permits access from the relay apparatus 30. On the other hand, if the token A1 has expired, such as when the token A1 has expired, the service providing apparatus 10A rejects access from the relay apparatus 30. Here, it is assumed that the token A1 has expired because the token A1 has expired.

  In step S210, if access from the relay device 30 is denied by the service providing device 10A, the relay device 30 fails to acquire the file list. Thereby, the relay device 30 determines that the token A1 of the login user for accessing the service providing device 10A has expired.

  In step S211, the relay unit 312 of the relay device 30 updates the user management table 331 according to this determination. FIG. 12 is a diagram illustrating an example of the user management table 331 after the update. In this example, it is considered that the token A1 has expired because access using the token A1 is denied. Accordingly, as shown in FIG. 12, the state of the token A1 of the login user stored in the user management table 331 is changed from “present” to “revoked”.

  In step S212, the relay unit 312 transmits to the client device 20 via the communication unit 32 an error notification indicating that the acquisition of the file list of the service providing device 10A has failed due to the expiration of the token. The client device 20 receives this error notification via the communication unit 22.

  Thereafter, in steps S213 to S216, processing similar to that in steps S204 to S207 described above is performed. However, in step S214, a service list is created based on the user management table 331 updated in step S212. The updated user management table 331 shown in FIG. 12 is associated with the user ID “User01@aaa.example.com” of the login user stored in the memory, and the token status “revocation” of the service providing apparatus 10A. The token status “present” of the service providing apparatus 10B and the token status “present” of the service providing apparatus 10C are stored. In this case, the status of these tokens is described in the service list.

  In step S216, a service list screen 241 is displayed based on the service list. FIG. 13 is a diagram showing an example of the service list screen 241 displayed at this time. In the service list screen 241 illustrated in FIG. 13, the token status of the service providing apparatus 10 </ b> A is “revoked”. In this case, when selecting the service providing apparatus 10A, the user inputs the credit information registered in the service providing apparatus 10A into the input field C1 by an operation using the operation unit 23. For example, when the user's credit information registered in the service providing apparatus 10A is the user ID “user01@service_a.example.com” and the password “passwordA1”, the user ID and password are input in the input field C1. . The subsequent processing is the same as the processing in steps S108 to S113 described above.

(3) When a token expires during skewering search Next, an operation when a token registered in the relay device 30 expires when performing skewering search will be described. This skewered search refers to collectively searching data stored in a plurality of service providing apparatuses 10 under the same search condition. FIG. 14 is a sequence diagram illustrating an operation in the case where the token registered in the relay device 30 has expired when performing a skewer search. Here, it is assumed that the storage unit 33 stores a user management table 331 shown in FIG.

  The process of steps S301 to S306 is the same as the process of steps S101 to S106 described above. In step S307, the client unit 211 of the client device 20 first displays the service list screen 241 on the display unit 24 based on the service list received from the relay device 30 as in step S107 described above. In this example, the service list screen 241 shown in FIG. 11 is displayed. For example, when performing a skewer search for the service providing apparatuses 10A to 10C, the user selects the service providing apparatuses 10A to 10C by an operation using the operation unit 23, and then presses the search button B2. In the example shown in FIG. 11, since the token states of the service providing apparatuses 10A to 10C are all “present”, the user does not input credit information at this stage.

  When the search button B2 is pressed, the service list screen 241 transitions to the search screen 242. FIG. 15 is a diagram illustrating an example of the search screen 242. On this search screen 242, an input field C2 used for inputting search conditions and a search button B3 are displayed. The user inputs a search condition in the input field C2 by an operation using the operation unit 23, and then presses the search button B3. When the search button B3 is pressed, the client device 20 proceeds to step S308.

  In step S <b> 308, the client unit 211 transmits a search request for the service providing device 10 selected on the service list screen 241 to the relay device 30 via the communication unit 22. This search request includes the identification information of the service providing apparatus 10 selected on the service list screen 241 and the search conditions input on the search screen 242. The relay device 30 receives this search request via the communication unit 32.

  In step S <b> 309, the relay unit 312 responds to the service providing apparatus 10 in which the token status of the logged-in user stored in the user management table 331 is “Yes” among the service providing apparatuses 10 selected on the service list screen 241. To check the validity of the token. Specifically, the relay unit 312 transmits an information acquisition request to the target service providing apparatus 10 via the communication unit 32. The information that is the target of the acquisition request may be any information as long as it is information stored in the service providing apparatus 10. For example, when user information is stored in the service providing apparatus 10, this user information may be used.

  In this example, the search request includes identification information of the service providing apparatuses 10A to 10C selected on the service list screen 241. Further, in the user management table 331 shown in FIG. 10, “Yes” is set as the token status of each of the service providing apparatuses 10 </ b> A to 10 </ b> C in association with the user ID “User01@aaa.example.com” of the login user. Stored. In this case, an information acquisition request is transmitted to each of the service providing apparatuses 10A to 10C.

  At this time, the relay unit 312 reads the login user token for accessing the service providing apparatuses 10A to 10C from the user management table 331, and accesses the service providing apparatuses 10A to 10C using the read token. In the example illustrated in FIG. 10, the user management table 331 associates the login user ID “User01@aaa.example.com” stored in the memory with the token A1 of the service providing apparatus 10A and the service providing apparatus 10B. And the token C1 of the service providing apparatus 10C are stored. In this case, the relay unit 312 accesses the service providing apparatuses 10A, 10B, and 10C using the tokens A1, B1, and C1, respectively.

  When accessed from the relay device 30 using the tokens A1, B1, and C1, the service providing devices 10A, 10C, and 10C determine the validity of the tokens A1, B1, and C1, respectively. For example, when the token is within the expiration date, the service providing apparatus 10 determines that the token is valid. On the other hand, when the token has expired, the service providing apparatus 10 determines that the token has expired.

  Here, it is assumed that the tokens B1 and C1 are valid, but the token A1 has expired. In this case, the service providing apparatuses 10B and 10C permit access from the relay apparatus 30 and transmit target information to the relay apparatus 30 in response to the acquisition request received from the relay apparatus 30. The relay apparatus 30 determines that the tokens of the service providing apparatuses 10B and 10C are valid by receiving information from the service providing apparatuses 10B and 10C. On the other hand, the service providing apparatus 10A denies access from the relay apparatus 30. In this case, the relay device 30 fails to acquire information from the service providing device 10A. Thereby, the relay device 30 determines that the token A1 of the service providing device 10A has expired.

  In step S310, the relay unit 312 of the relay device 30 updates the user management table 331 as in step S211 described above. In this example, it is considered that the token A1 has expired because access using the token A1 is denied. Accordingly, as shown in FIG. 12, the state of the token A1 of the login user stored in the user management table 331 is changed from “present” to “revoked”.

  In step S311, the relay unit 312 transmits an error notification indicating that acquisition of information of the service providing apparatus 10A has failed to the client apparatus 20 via the communication unit 32, as in step S212 described above. The client device 20 receives this error notification via the communication unit 22.

  Thereafter, in steps S312 to S315, processing similar to that in steps S304 to S307 described above is performed. However, in step S313, a service list is created based on the user management table 331 updated in step S310. In this example, in the user management table 331 shown in FIG. 12, the token status “revocation” of the service providing apparatus 10A is associated with the user ID “User01@aaa.example.com” of the login user stored in the memory. Since the token status “present” of the service providing apparatus 10B and the token status “present” of the service providing apparatus 10C are stored, the status of these tokens is described in the service list.

  In step S315, a service list screen 241 as shown in FIG. 13 is displayed based on the service list. On the service list screen 241, the user selects the service providing apparatuses 10 </ b> A to 10 </ b> C by an operation using the operation unit 23. Here, among the service providing apparatuses 10A to 10C, the service status of the service providing apparatus 10A is “revoked”. In this case, the user inputs the credit information registered in the service providing apparatus 10A. For example, when the user's credit information registered in the service providing apparatus 10A is the user ID “user01@service_a.example.com” and the password “passwordA1”, the user ID and password are input in the input field C1. .

  In step S316, the client unit 211 transmits a search request for the service providing apparatus 10 selected on the service list screen 241 to the relay apparatus 30 via the communication unit 22, as in step S308 described above. However, unlike the step S308, in this search request, in addition to the identification information of the service providing apparatus 10 selected on the service list screen 241 and the search conditions input on the search screen 242, the credit input in the input field C1 is included. Contains information. In this example, a search request including identification information, search conditions, user ID “user01@service_a.example.com” and password “passwordA1” of the service providing devices 10A to 10C is transmitted to the relay device 30. The relay device 30 receives this acquisition request via the communication unit 32. The first acquisition unit 313 acquires the credit information included in the acquisition request, and stores the credit information in a memory whose stored contents are deleted by turning off the power of the RAM or the like.

  In step S317, the relay unit 312 determines that the status of the login user token stored in the user management table 331 in the service providing apparatus 10 selected on the service list screen 241 is “Yes”, as in step S309 described above. The validity of the token is confirmed with respect to the service providing apparatus 10. However, here, the validity of the token is confirmed based on the user management table 331 updated in step S310.

  In this example, the search request includes identification information of the service providing apparatuses 10A to 10C selected on the service list screen 241. Further, in the updated user management table 331 shown in FIG. 12, the token status “revocation” of the service providing apparatus 10A is associated with the login user ID “User01@aaa.example.com” stored in the memory. ”, The token status“ present ”of the service providing apparatus 10B and the token status“ present ”of the service providing apparatus 10C are stored. In this case, the validity of the token is confirmed for the service providing apparatuses 10B and 10C, but the validity of the token is not confirmed for the service providing apparatus 10A. As described in step S309 described above, since the tokens B1 and C1 of the service providing apparatuses 10B and 10C are both valid, the service providing apparatuses 10B and 10C are targeted according to acquisition requests, respectively. Information is returned.

  In step S318, the relay unit 312 transfers the search request received from the client device 20 to the service providing device 10 selected on the service list screen 241 via the communication unit 32. In this example, since the search request includes the identification information of the service providing apparatuses 10A to 10C selected on the service list screen 241, the search request is transferred to the service providing apparatuses 10A to 10C.

  Here, since the service providing apparatuses 10B and 10C have confirmed the validity of the token in step S317 described above, the relay unit 312 provides the service using the tokens B1 and C1 of the login user in the same manner as in step S317. Access devices 10B and 10C. On the other hand, in the service providing apparatus 10A, since the token A1 of the login user has expired, the relay unit 312 accesses the service providing apparatus 10A using the credit information stored in the memory. In this example, the service providing apparatus 10A corresponds to a first service providing apparatus that does not permit access using a token, and the service providing apparatuses 10B and 10C are second service providing apparatuses other than the first service providing apparatus. It corresponds to.

  When accessed from the relay device 30 using the credit information, the service providing device 10A determines whether or not to permit access from the relay device 30 based on whether or not the credit information is registered. When the credit information included in the acquisition request is registered, the service providing apparatus 10A permits access from the relay apparatus 30. On the other hand, when the credit information included in the acquisition request is not registered, the service providing apparatus 10A denies access from the relay apparatus 30 and ends the process without performing the subsequent processes. In this example, since the user ID “user01@service_a.example.com” and the password “passwordA1” included in the acquisition request are registered in the service providing apparatus 10A, the service providing apparatus 10A accesses the relay apparatus 30. To give permission. The service providing apparatuses 10B and 10C permit access from the relay apparatus 30 because the tokens B1 and C1 are valid.

  In this case, the service providing apparatuses 10 </ b> A to 10 </ b> C search for data in response to the search request received from the relay apparatus 30. Specifically, the service providing apparatuses 10A, 10B, and 10C search for data that meets the search conditions included in the search request. Then, the service providing apparatuses 10A, 10B, and 10C transmit the data search results to the relay apparatus 30. The relay device 30 receives these search results via the communication unit 32.

  In step S319, the relay unit 312 of the relay device 30 merges the search results received from the service providing devices 10A, 10B, and 10C.

  In step S320, the relay unit 312 transmits the search result merged in step S319 to the client device 20 via the communication unit 32. The client device 20 receives this search result via the communication unit 22.

  In step S321, the client unit 211 of the client device 20 causes the display unit 24 to display a search result screen based on the search result received from the relay device 30. The search result is displayed on this search result screen.

  Thereafter, when data is selected from the search results by the user's operation, the client apparatus 20 transmits the selected data to the service providing apparatus via the relay apparatus 30 in the same procedure as in steps S108 to S112 described above. Acquired from 10A, 10B or 10C. Here, when acquiring data from the service providing apparatus 10A, the access unit 314 of the relay apparatus 30 accesses the service providing apparatus 10A using the credit information stored in the memory in step S316 described above. The data acquired from the service providing apparatuses 10A, 10B, or 10C is used for image formation by the image forming unit 27, for example.

(4) Token Registration Processing When the token is not registered in the relay device 30 or the token registered in the relay device 30 has expired, the user uses the authority registration device 40 to enter the relay device 30. A process for registering a new token is performed. FIG. 16 is a sequence diagram illustrating processing for registering a token in the relay device 30. Here, it is assumed that the storage unit 33 stores a user management table 331 shown in FIG.

  In the user management table 331 shown in FIG. 12, the token status “revocation” of the service providing apparatus 10A is stored in association with the user ID “User01@aaa.example.com”. This indicates that the token of the user with the user ID “User01@aaa.example.com” for accessing the service providing apparatus 10A has expired.

  When performing processing for registering a token in the relay device 30, the user first logs in to the relay device 30 using the authority registration device 40. Specifically, the user inputs account information for logging in to the relay device 30 by an operation using the operation unit 43. For example, when the account information for logging in to the relay device 30 is the user ID “User01@aaa.example.com” and the password “password01”, the user ID and password are input.

  In step S <b> 401, the authority registration unit 411 of the authority registration apparatus 40 transmits an authentication request including account information input by a user operation to the relay apparatus 30 via the communication unit 42. The relay device 30 receives this authentication request via the communication unit 32.

  In step S402, the authentication unit 311 of the relay device 30 performs user authentication in response to the authentication request received from the authority registration device 40, as in step S102 described above.

  In step S403, the authentication unit 311 transmits the authentication result of the user authentication to the authority registration device 40 via the communication unit 32. The authority registration device 40 receives this authentication result via the communication unit 42. When the authority registration apparatus 40 receives an authentication result indicating that the user authentication is successful, the authority registration apparatus 40 proceeds to step S404. On the other hand, when receiving the authentication result indicating that the user authentication has failed, the authority registration device 40 ends this process without performing the subsequent processes. In this example, the authority registration device 40 proceeds to step S404 in order to receive an authentication result indicating that the user authentication is successful.

  In step S <b> 404, the authority registration unit 411 of the authority registration apparatus 40 transmits a service list acquisition request indicating a list of services provided from the service providing apparatus 10 previously registered in cooperation to the relay apparatus 30 via the communication unit 42. To do. The relay device 30 receives this acquisition request via the communication unit 32.

  In step S405, the registration processing unit 315 of the relay device 30 creates a service list in response to the acquisition request received from the authority registration device 40, as in step S105 described above.

  In step S406, the registration processing unit 315 transmits the service list created in step S405 to the authority registration device 40 via the communication unit 32. The authority registration device 40 receives this service list via the communication unit 42.

  In step S <b> 407, the authority registration unit 411 of the authority registration apparatus 40 displays the service list screen 243 on the display unit 44 based on the service list received from the relay apparatus 30.

  FIG. 17 is a diagram showing an example of the service list screen 243 displayed at this time. The service list screen 243 displays a service list in which token states of the service providing apparatuses 10A to 10C are described. From this service list, the user selects the service providing apparatus 10 that is an issuer of a token to be newly registered in the relay apparatus 30. In the service list screen 243 shown in FIG. 16, the token status of the service providing apparatus 10A is “revoked”. In this case, in order to register a valid token of the service providing apparatus 10A in the relay apparatus 30, the user selects the service providing apparatus 10A by an operation using the operation unit 43, and then presses the selection button B4. When the selection button B4 is pressed, the authority registration device 40 proceeds to step S408.

  In step S <b> 408, the authority registration unit 411 transmits a token registration processing request issued from the service providing apparatus 10 selected on the service list screen 243 to the relay apparatus 30 via the communication unit 42. This registration processing request includes the identification information of the service providing apparatus 10 selected on the service list screen 243. In this example, since the service providing apparatus 10A is selected on the service list screen 243, the registration processing request includes identification information of the service providing apparatus 10A. The relay device 30 receives this registration processing request via the communication unit 32.

  In step S409, the registration processing unit 315 of the relay device 30 redirects the access destination of the authority registration device 40 to the service providing device 10 selected on the service list screen 243. Specifically, the registration processing unit 315 transmits a response notifying the URL of the service providing apparatus 10 selected on the service list screen 243 as the movement destination to the authority registration apparatus 40 via the communication unit 32. In this example, since the registration processing request includes the identification information of the service providing apparatus 10A selected on the service list screen 243, a response notifying the URL (Uniform Resource Locator) of the service providing apparatus 10A as the destination is authorized. It is transmitted to the registration device 40. The response includes the URL of the relay device 30. The authority registration device 40 receives this response via the communication unit 42.

  In step S <b> 410, the third acquisition unit 412 of the authority registration device 40 transmits a code acquisition request permitting token acquisition to the redirect-destination service providing device 10 via the communication unit 42. In this example, since the URL of the service providing apparatus 10A is notified as the destination by the response received from the relay apparatus 30, this acquisition request is transmitted to the service providing apparatus 10A. The acquisition request includes the URL of the relay device 30 included in the response.

  In step S411, the service providing apparatus 10A issues a code permitting token acquisition in response to the acquisition request received from the relay apparatus 30, and redirects the access destination of the authority registration apparatus 40 to the relay apparatus 30. Specifically, the service providing apparatus 10 </ b> A first transmits a login request to the authority registration apparatus 40. In response to this request, the user inputs a user ID and a password for logging in to the service providing apparatus 10 </ b> A by an operation using the operation unit 43. The authority registration device 40 transmits the user ID and password input by the user's operation to the service providing device 10A via the communication unit 42. The service providing apparatus 10A performs user authentication based on the user ID and password received from the authority registration apparatus 40, and issues a code for permitting token acquisition when the user authentication is successful. In addition, the service providing apparatus 10 </ b> A transmits a response that notifies the URL of the relay apparatus 30 included in the acquisition request received from the authority registration apparatus 40 as a movement destination to the authority registration apparatus 40. This response includes the issued code. The authority registration device 40 receives this response via the communication unit 42. The third acquisition unit 412 acquires a code included in this response.

  In step S412, the transmission unit 413 of the authority registration device 40 transmits the code included in the response received from the service providing device 10A to the redirect destination relay device 30 via the communication unit 42. The relay device 30 receives this code via the communication unit 32.

  In step S413, the second acquisition unit 316 of the relay apparatus 30 transmits a token acquisition request to the service providing apparatus 10 selected on the service list screen 243 via the communication unit 32. This acquisition request includes the code received from the authority registration device 40. In this example, since the registration processing request received in step S408 includes the identification information of the service providing apparatus 10A selected on the service list screen 243, a token acquisition request is transmitted to the service providing apparatus 10A.

  In step S <b> 414, the service providing apparatus 10 </ b> A issues a login user token because the acquisition request received from the relay apparatus 30 includes a code, and transmits the issued token to the relay apparatus 30. The relay device 30 receives this token via the communication unit 32. The second acquisition unit 316 acquires this token.

  In step S415, the registration processing unit 315 of the relay device 30 stores the token received from the service providing device 10A in the user management table 331. In this example, since the token of the login user is acquired from the service providing apparatus 10A, the token is stored in association with the user ID “User01@aaa.example.com” of the login user in the user management table 331 illustrated in FIG. Instead of the token A1 of the service providing apparatus 10A, a new token received from the service providing apparatus 10A is stored.

  In step S416, the registration processing unit 315 updates the user management table 331 according to the storage of a new token. In this example, in step S415, a new token of the login user for accessing the service providing apparatus 10A is stored in the user management table 331. Therefore, in the user management table 331 shown in FIG. 12, the token status of the service providing apparatus 10A stored in association with the user ID “User01@aaa.example.com” stored in the memory is “revoked”. Is changed to “Yes”.

  In step S417, the registration processing unit 315 transmits a notification indicating that the token registration processing has been completed to the authority registration device 40 via the communication unit 32. The authority registration device 40 receives this notification via the communication unit 42.

  According to the embodiment described above, even when a token necessary for access to the service providing apparatus 10 is not registered in the relay apparatus 30, by inputting the credit information registered in the service providing apparatus 10, The providing device 10 is accessed and the provision of the service is received. Therefore, as in the prior art, in such a case, the client apparatus 20 is moved to the authority registration apparatus 40 in spite of the operation of the client apparatus 20, and the authority registration apparatus 40 is operated to register the token in the relay apparatus 30. Therefore, the convenience for the user is improved.

  In addition, the credit information input by the user is stored in a memory such as a RAM of the relay device 30 and is deleted when the power is turned off. In this case, access to the service providing apparatus 10 is realized using the credit information only during the period when the credit information is stored in the memory. Thereby, temporary access to the service providing apparatus 10 is realized. Moreover, the credit information input by the user is the user's personal information. According to the present embodiment, since the user's credit information is not continuously held in the relay device 30, the risk that the credit information is leaked from the relay device 30 is reduced.

  Further, as in the above-described embodiment, when the expiration date of the token is managed by the service providing apparatus 10, the token stored in the relay apparatus 30 may have expired. However, according to the operation of “(2) When the token has expired” described above, even in such a case, by inputting the credit information registered in the service providing apparatus 10, the service providing apparatus 10 And access to services.

  When performing skewered search, the service providing apparatus 10 in which a token necessary for access is registered in the service providing apparatus 10 to be searched, and the service providing apparatus in which a token necessary for access is not registered 10 may be mixed. However, according to the operation of “(3) When token expires during skew search” described above, access to each service providing apparatus 10 is realized even in such a case.

  Further, according to “(4) Token registration process” described above, when a token necessary for accessing the service providing apparatus 10 is not registered in the relay apparatus 30, the access to the service providing apparatus 10 can be performed. The token is registered in the relay device 30.

3. Modified Embodiment The above-described embodiment is an example of the present invention. These embodiments may be modified as follows. The following modifications may be combined with each other.

(1) In the above-described embodiment, the credit information input by the user is stored in a memory such as the RAM of the relay device 30 and deleted when the power is turned off. However, the credit information may be deleted when a predetermined condition is satisfied.

  FIG. 18 is a diagram illustrating a functional configuration of the relay system according to the present modification. The relay device 30 according to the present modification has a function called a deletion unit 317 in addition to the function described in the embodiment. The deletion unit 317 deletes the credit information from the memory when a predetermined condition is satisfied. In this modification, the memory functions as a storage unit. The predetermined condition may be that the process with the service providing apparatus 10 relating to the request from the client apparatus 20 has been completed. For example, when performing the process of acquiring data from the service providing apparatus 10A, the deletion unit 317 may delete the credit information stored in the memory when the data selected by the user is acquired from the service providing apparatus 10A. Good.

  In addition, the predetermined condition may be that the user has logged out from the relay device 30. In this case, the deletion unit 317 may delete the credit information from the memory when a logout request is received from the client device 20, for example.

  In addition, the predetermined condition may be that a predetermined time has elapsed since the credit information was stored in the memory. In this case, the deletion unit 317 measures the time from the time when the credit information is stored in the memory using, for example, a timer, and deletes the credit information from the memory when the measured time passes a predetermined time. May be.

(2) In the above-described embodiment, the example in which the service providing devices 10A to 10C permit access using credit information has been described. However, the service providing apparatus 10 may include a device that does not permit access using credit information. In this case, the relay device 30 stores correspondence information indicating whether or not each service providing device 10 supports access using credit information, and the service providing device whose token has expired based on the correspondence information It may be determined whether 10 corresponds to access using credit information.

  When the service providing apparatus 10 whose token has expired supports access using credit information, the relay apparatus 30 provides a service list screen 241 for displaying the credit information input field C1 as shown in FIG. To do. On the other hand, when the service providing apparatus 10 whose token has expired does not support access using credit information, the relay apparatus 30 displays a service list screen 241 that displays a message “Register token,” for example. provide. The service list screen 241 does not display an input field C1 used for inputting credit information.

(3) In the above-described embodiment, the program executed by the control unit 21 of the client device 20, the program executed by the control unit 31 of the relay device 30, and the program executed by the control unit 41 of the authority registration device 40 are It may be downloaded via a communication line such as the Internet. The program is provided in a state of being recorded on a computer-readable recording medium such as a magnetic recording medium (magnetic tape, magnetic disk, etc.), an optical recording medium (optical disk, etc.), a magneto-optical recording medium, or a semiconductor memory. May be.

DESCRIPTION OF SYMBOLS 1 ... Relay system, 10A, 10B, 10C ... Service provision apparatus, 20 ... Client apparatus, 30 ... Relay apparatus, 40 ... Authority registration apparatus, 211 ... Client part, 311 ... Authentication part, 312 ... Relay part, 313 ... 1st Acquisition unit, 314 ... access unit, 315 ... registration processing unit, 316 ... second acquisition unit, 317 ... deletion unit, 411 ... authority registration unit, 412 ... third acquisition unit, 413 ... transmission unit

Claims (6)

A storage unit for storing authority information used to access the service providing device;
A first acquisition unit that acquires, from the client device, user identification information registered in the service providing device that is the target of the access request from the client device;
When the authority information stored in the storage unit is not valid, the identification information acquired by the first acquisition unit is used without using the authority information used when it is valid. A relay system comprising: an access unit that accesses the target service providing apparatus. When the authority information stored in the storage unit is not valid, the transmission unit further includes a transmission unit that transmits screen information used to display a screen that accepts input of the identification information to the client device,
The relay system according to claim 1, wherein the first acquisition unit acquires the identification information input to the screen displayed using the screen information in the client device. The storage unit further stores state information indicating a state of the authority information,
The relay system according to claim 1, further comprising: an update unit that updates the state information stored in the storage unit when the authority information stored in the storage unit is not valid. A first acquisition unit that acquires, from the client device, user identification information registered in the service providing device that is the target of the access request from the client device;
If the authority information stored in the storage unit and used to access the target service providing apparatus is not valid, the first information is used without using the authority information used when it is valid. A relay device comprising: an access unit that accesses the target service providing device using the identification information acquired by the acquisition unit. The relay device according to claim 4, further comprising: a relay unit that relays data exchanged between the service providing device and the client device when access is permitted by the target service providing device. On the computer,
Obtaining from the client device identification information of the user registered in the service providing device that is the target of the access request from the client device;
If the authority information used to access the target service providing apparatus stored in the storage unit is not valid, the acquired information is used without using the authority information used when it is valid. A program for executing the step of accessing the target service providing apparatus using the identification information.

Images