JP2020087197A - Information processing system, information processing program and information processing method - Google Patents

Abstract

To provide an information processing system, an information processing program and an information processing method that allows easy addition of cooperation setting with an external service.SOLUTION: An information processing system comprises: a component setting reception unit; an external service coordination component; and an approval service unit. The component setting reception unit receives registration of external service coordination fixing information and external service coordination variation information (external service coordination information) which is information to be coordinated with the external service. The external service coordination component manages the external service coordination information. The approval service unit acquires a token from the external service using the external service coordination information. With this configuration, a developer can set external service coordination information from a component development screen of a developer site using an API of the external service. In addition, the developer can quickly add the external service coordination information on the basis of the information received on the API.SELECTED DRAWING: Figure 4

Description

The present invention relates to an information processing system, an information processing program, and an information processing method.

Patent Document 1 discloses a technique of reducing the number of authorization procedures when a user uses a service when linking with an external service such as a client ID or a client secret.

However, the conventional technique disclosed in Patent Document 1 does not disclose a method of adding a linked external service, and thus has a problem that it is not possible to meet the need to easily add an external service.

In view of the above problem, the present invention can easily add a cooperation setting with an external service.

In view of the above problems, the information processing system according to the present invention includes a component setting reception unit that receives registration of external service cooperation information that is information that cooperates with an external service, and an external service cooperation component that manages the external service cooperation information. An authorization service unit that acquires a token from the external service using the external service cooperation information.

According to the present invention, it is possible to easily add a link setting with an external service.

It is a block diagram of the information processing system 1 which concerns on embodiment of this invention. 3 is a hardware configuration diagram of a computer system 500. FIG. 4 is a processing block diagram of the service providing system 50. FIG. It is a figure for demonstrating the function for adding the external service 103. It is a figure which shows the example of a screen display of a development site. It is a figure which shows the screen (my page) of external service cooperation displayed when the user site 102 is accessed. It is a figure which shows an example of federation information. It is a figure which shows an example of the external service cooperation fixed information 90. It is a figure which shows an example of user information. It is a figure which shows an example of the external service cooperation change information 91. 7 is a sequence chart for explaining a component registration operation. It is a sequence chart for explaining an authorization operation for acquiring a token from an external service. It is a figure showing the example of composition concerning the modification of information processing system 1. 9 is a sequence chart for explaining a component registration operation according to a modified example of the information processing system 1. A modified example of the information processing system 1 is a sequence chart for explaining an authorization operation for acquiring a token from an external service.

Embodiments for carrying out the present invention will be described below with reference to the drawings.

FIG. 1 is a configuration diagram of an information processing system 1 according to an embodiment of the present invention. The information processing system 1 includes a service providing system 50 and an external service system 30.

The service providing system 50 includes an access control device 21, a print service providing device 22, a scan service providing device 23, a management setting service providing device 24, and another service providing device 25.

The access control device 21 controls login to a print service provided by the print service providing device 22, a scan service provided by the scan service providing device 23, a management setting service provided by the management setting service providing device 24, and the like.

The access control device 21, the print service providing device 22, the scan service providing device 23, the management setting service providing device 24, and the other service providing device 25 are connected to the network N2. The network N2 is connected to the network N4 such as the Internet via the access control device 21. The security of the network N2 is protected by the access control device 21.

A firewall FW in the office is connected to the network N4. The network N1 is connected to the firewall FW. The network N1 is a private network existing inside the firewall FW (for example, in an office). The firewall FW is installed at a contact point between the network N1 and the network N4, and detects and blocks unauthorized access.

A client terminal 11, a mobile terminal 12, an image forming apparatus 14 such as a multifunction peripheral, a projector 15, and other equipment 16 such as an electronic blackboard are connected to the network N1.

The client terminal 11 is an example of a terminal device. The client terminal 11 is an information processing device equipped with a general OS and the like. The client terminal 11 includes a wireless communication unit or a wired communication unit. The client terminal 11 is a terminal that can be operated by the user. The terminal is a tablet PC (Personal Computer), a notebook PC, or the like. The mobile terminal 12 is an example of a terminal device. The mobile terminal 12 includes a wireless communication unit or a wired communication unit. The mobile terminal 12 is a terminal that the user can carry. The terminal is a smartphone, a mobile phone, a tablet PC, a notebook PC, or the like. The image forming apparatus 14 is an apparatus having an image forming function. The device is a multifunction peripheral, a copier, a scanner, a printer, a laser printer, or the like. The image forming apparatus 14 includes a wireless communication unit or a wired communication unit. The projector 15 is a device that projects an image. The projector 15 includes a wireless communication unit or a wired communication unit.

An access control device 31 is connected to the network N4. The network N3 is connected to the access control device 31. The network N3 is a network forming an external service system 30 represented by a cloud service. The security of the network N3 is protected by the access control device 31. The external service providing device 32 is connected to the network N3. The access control device 31 controls login to an external service provided by the external service providing device 32.

The information processing system 1 uses a standard technology called API (Application Programming Interface) authorization called OAuth. The service providing system 50 corresponds to an OAuth consumer. The external service system 30 corresponds to an OAuth service provider. The external service system 30 publishes a Web API (Application Programming Interface), and the user can access the resource stored in the external service system 30 and access to the service that handles the resource, within his or her authority through the Web API. You can access it. Further, the print service providing apparatus 22 and the like of the service providing system 50, by using the authorization token based on the authority delegated by the user, are stored in the external service system 30 within the scope of the authority delegated by the user. It is possible to access existing resources and services that handle the resources.

The client terminal 11, mobile terminal 12, access control device 21, print service providing device 22, scan service providing device 23, management setting service providing device 24, and other service providing device 25 shown in FIG. It is realized by the system. The access control device 31 and the external service providing device 32 shown in FIG. 1 are realized by the computer system shown in FIG.

FIG. 2 is a hardware configuration diagram of the computer system 500. The computer system 500 includes an input device 501, a display device 502, an external I/F 503, a RAM (Random Access Memory) 504, a ROM (Read Only Memory) 505, a CPU (Central Processing Unit) 506, a communication I/F 507, and an HDD ( Hard Disk Drive) 508. These are connected to each other by a bus B. The input device 501 is a keyboard, a mouse, a touch panel, or the like, and is used by the user to input each operation signal. The display device 502 is a display that displays a processing result by the computer system 500. The communication I/F 507 is an interface that connects the computer system 500 to the networks N1 to N4. Accordingly, the computer system 500 can perform data communication via the communication I/F 507. The HDD 508 is a non-volatile storage device that stores programs, data, and the like. The stored programs and data include, for example, an OS (Operating System) that is basic software that controls the entire computer system 500, application software that provides various functions on the OS, and the like. The HDD 508 manages stored programs, data, etc. by a predetermined file system, DB (database), and the like.

The external I/F 503 is an interface with a recording medium 503a that is an external device. As a result, the computer system 500 can read and write the recording medium 503a via the external I/F 503. The recording medium 503a is a flexible disk, a CD (Compact Disk), a DVD (Digital Versatile Disk), an SD memory card (SD Memory card), a USB memory (Universal Serial Bus memory), or the like. The ROM 505 is a nonvolatile semiconductor memory (storage device) that can retain programs, data, and the like even when the power is turned off. The ROM 505 stores programs and data such as a BIOS (Basic Input/Output System) executed when the computer system 500 is activated, OS settings, and network settings. The RAM 504 is a volatile semiconductor memory (storage device) that temporarily holds programs and data. The CPU 506 is an arithmetic unit that realizes control and functions of the entire computer system 500 by reading programs and data from a storage device such as the ROM 505 and the HDD 508 onto the RAM 504 and executing processing.

The client terminal 11, mobile terminal 12, access control device 21, print service providing device 22, scan service providing device 23, management setting service providing device 24, and other service providing device 25 shown in FIG. 1 are shown in FIG. Various processes described later can be realized by the configuration. Further, the access control device 31 and the external service providing device 32 shown in FIG. 1 can realize various processes described later by the configuration shown in FIG.

The functions of the service providing system 50 are realized by the processing blocks shown in FIG. FIG. 3 is a processing block diagram of the service providing system 50. The service providing system 50 realizes a service application 51, a platform 52, a management data storage unit 53, and a platform API 54 by executing a program.

The service application 51 includes a print service application 61, a scan service application 62, a management setting service application 63, and one or more other service applications 64 as an example. The print service application 61 is an application that provides a print service. The scan service application 62 is an application that provides a scan service. The management setting service application 63 is an application that provides a management setting service. The other service application 64 is an application that provides some kind of service.

The platform API 54 is an interface for the service application 51 such as the print service application 61, the scan service application 62, the management setting service application 63, and the other service application 64 to use the platform 52. The platform API 54 is a predefined interface provided for the platform 52 to receive a request from the service application 51, and is composed of, for example, a function or a class. When the service providing system 50 is configured by being distributed to a plurality of information processing devices, the platform API 54 can use, for example, a Web API that can be used via a network.

The platform 52 includes a device communication unit 72, a data processing unit 74, a component information management unit 105, and an authentication service unit 104.

The authentication service unit 104 executes authentication based on a login request from an office device such as the client terminal 11 or the image forming apparatus 14. The office equipment is a generic term for the client terminal 11, the mobile terminal 12, the image forming apparatus 14, the projector 15, and other equipment 16. The device communication unit 72 executes communication with office devices, the external service system 30, and the like. The authentication service unit 104 also manages a session between the office device and the external service system 30 shown in FIG. The data processing unit 74 executes data processing based on the request from the service application 51.

The management data storage unit 53 includes an organization management information storage unit 81, a user information storage unit 82, an authorization setting information storage unit 84, an external service information storage unit 85, an authorization token information storage unit 86, a data management information storage unit 87, and data. The storage 88 is provided as an example.

The organization management information storage unit 81 stores organization management information. The user information storage unit 82 stores user management information. The authorization setting information storage unit 84 stores authorization setting information. The external service information storage unit 85 stores external service information. The authorization token information storage unit 86 stores authorization token information. The data management information storage unit 87 stores data management information. The data storage 88 stores other data and the like.

The service providing system 50 is, for example, a cloud platform having functions such as authentication and asynchronous conversion, a group of services that provide services such as print services using the cloud platform functions, and a management setting service that performs management settings for each service. Function. The cloud platform is composed of, for example, the platform 52, the management data storage unit 53, and the platform API 54. The service group includes, for example, the service application 51. The management setting service is configured by the management setting service application 63, for example. The authentication function of the cloud infrastructure is configured by, for example, the authentication service unit 104 and the authentication database. The authentication database includes an organization management information storage unit 81, a user information storage unit 82, an authorization setting information storage unit 84, an external service information storage unit 85, an authorization token information storage unit 86, and the like. The asynchronous conversion function provided in the cloud infrastructure is configured by, for example, the data processing unit 74, the data management information storage unit 87, and the data storage 88. The service group such as the service application 51 uses the functions of the cloud infrastructure of the service providing system 50, such as authentication and asynchronous conversion, to provide services. In addition, when the service group provides a service in cooperation with the function of the external service system 30 illustrated in FIG. 1, the service group acquires an authorization token for accessing the external service system 30 through the authentication function of the cloud platform. To do. The management setting performed by the management setting service application 63 includes the management setting for the authorization process. The management setting service application 63 has a UI (User Interface) for performing an authorization procedure. The management setting service application 63 cooperates with the authentication service unit 104 to register authorization setting information, which will be described later.

The external service system 30 shown in FIG. 1 is an external system of the service providing system 50 and provides cloud services and the like. In the present embodiment, the service (function) provided by the external service system 30 is called an external service. The external services include an online storage service provided as a cloud service, a scan document storage service, and a scan document management service. The external service system 30 also has a function as an authorization server that issues an authorization token in response to a request from the authentication service unit 104 of the service providing system 50. The external service system 30 has a Web API. The WebAPI of the external service system 30 is used to receive a request for processing using an authorization token and provide a service to the service application 51 of the service providing system 50.

In the service providing system 50 illustrated in FIG. 3, since the authentication service unit 104 includes the function as the authorization client, the organization management information, the user management information, the device management information, and the authorization setting commonly used by the plurality of service applications 51 are provided. Information, external service information, and authorization token information can be centrally managed, which improves security and reduces management costs. Further, in the service providing system 50, the management process of the authorization setting information, the external service information, the authorization information such as the authorization token, and the authorization process are centralized in the authentication service unit 104, so that the user can perform a single authorization procedure. It is possible to provide various mashup services for linking a plurality of services regardless of the service application 51.

The service providing system 50 saves information that needs to be permanently saved, such as organization management information, user management information, device management information, authorization setting information, and external service information, in the HDD 508 shown in FIG. 2, for example. Further, the service providing system 50 has a fixed expiration date such as authorization token information and has a shorter life cycle than other information such as organization management information, user management information, device management information, authorization setting information, and external service information. May be stored in the RAM 504 (on-memory) instead of the HDD 508. In this way, by storing the information having a short life cycle in the on-memory, the reading and writing of the authorization token information becomes faster, and the response becomes faster.

Details of the service application 51, management setting service application 63, authentication service unit 104, data processing unit 74, organization management information, user management information, device management information, authorization setting information, external service information, authorization token information, etc. The detailed description is omitted because it is disclosed in Patent Document 1. Details of the procedure for registering the authorization setting information, the procedure for storing the authorization token information, the procedure for using the external service, and the like are disclosed in Japanese Patent Application Laid-Open No. 2004-242, so detailed description will be omitted.

The characteristic functions of the present invention (functions for easily adding external services) will be described below. FIG. 4 is a diagram for explaining a function for adding the external service 103. Hereinafter, the "external service 103" may be referred to as an "external service".

The development site 100 is a UI that develops with the components that make up the workflow. FIG. 5 is a diagram showing a screen display example of the development site. As shown in FIG. 5, external service cooperation fixed information 90 and external service cooperation change information 91 are displayed on the screen of the development site.

The external service cooperation fixed information 90 is one of the external service cooperation information necessary to cooperate with the external service. The external service cooperation information is information that cooperates with the external service. The external service cooperation fixed information 90 includes an external service identifier, a client ID, a client secret, an authorization request endpoint, and the like. The external service identifier is an identifier that identifies an external service. The client ID and the client secret are credential information issued by the external service. The client ID is information for identifying the client. The client secret is secret information for guaranteeing the identity of the client ID, and is information that plays a role like a password. The authorization request endpoint is information regarding the API of the external service that is the endpoint. In addition, the external service cooperation fixed information 90 includes a token acquisition endpoint, a token destruction endpoint, and the like.

The external service cooperation variation information 91 is one of the external service cooperation information necessary to cooperate with the external service. The external service cooperation variation information 91 includes scope information, component information to be disclosed, and the like. Since the scope information cannot acquire all the authority of the linked external service, for example, some services such as Gmail (registered trademark) and Google Calendar (registered trademark) among the services of Google (registered trademark) Is information for specifying. The scope is, for example, information indicating a range for which permission is requested from a user who cooperates with an external service, such as permission to access Gmail (registered trademark) and permission to overwrite Google Calendar (registered trademark). The necessary scope information differs depending on the component that uses the information linked with the external service. Therefore, the component manages the scope information as the variation information. For the component information to be published, in order to prevent the credential information registered by the user in the external service from being used for all components on SI-Cloud, set the range (public range) that can be used by the components requested by each user. It is a parameter.

In FIG. 5, the scope information and the component information to be disclosed are shown as an example of the external service cooperation variation information 91. However, the external service cooperation variation information 91 includes an external service identifier and the like in addition to these pieces of information. May be. A specific example of the information included in the external service cooperation variation information 91 will be described later.

The component information management unit 105 manages information on components that make up the workflow. Some components use the function of the external service, and the component information management unit 105 manages the necessary scope information of the external service according to the needs of the component. The component information management unit 105 has information for coordinating with an external service registered in the component so that the component can be referenced by other components. The component information management unit 105 includes an external service cooperation component 1051, a component setting reception unit 1054, and external service cooperation change information 91. The component setting reception unit 1054 includes a reference component 1052 and a management component 1053.

The user site 102 is a site used by the end user, and provides the user with a UI for setting the linkage between the SI-Cloud account and the external service. FIG. 6 is a diagram showing a screen (my page) of external service cooperation displayed when the user site 102 is accessed. When “External service cooperation” is selected from the menu displayed on My Page, a display screen as shown on the right side of FIG. 5 appears. External services that can be linked are displayed on this display screen. The type of external service is, for example, GoogleDrive (registered trademark), ROPC, FTP, or the like. By clicking the "Collaborate" button displayed on the screen, the flow for acquiring the token from the external service to be linked is executed according to the OAuth flow.

The authentication service unit 104 holds SI-Cloud user ID management, an ID authentication function, and the like, manages external service setting information for linking with an external service, and further manages a user ID (one of user information). Manage federation information (external service and cooperation information) by linking to. The external service setting information corresponds to the external cooperation fixed information shown in FIG. Details of external cooperation fixed information and user information will be subdivided. In the authentication service unit 104, the result of cooperation with the external service is associated with the user who requested the cooperation, and is registered as federation information. The federation information is information for managing the information (user information) of the user who accessed the development screen of FIG. 5 by associating the token information for linking with the external service. Federation is a mechanism that allows you to use all the permitted services by using the authentication information after passing authentication once.

The authentication service unit 104 includes an authorization service unit 1041 and a data storage unit 1042. The authorization service unit 1041 has an OAuth logic in order to link the data of the external service identifier and the external service. The authorization service unit 1041 acquires the token from the external service using the external service cooperation information. The data storage unit 1042 stores federation information, external service linkage fixed information, and user information.

A specific example of federation information is shown in FIG. FIG. 7 is a diagram showing an example of federation information. The federation information includes a user ID, an external service identifier, an access token, a refresh token, and the like. In the user ID, for example, User0001, User0002, etc. are registered as information for identifying the user who uses the external service. In the external service identifier, for example, Google (registered trademark), office365 (registered trademark), or the like is registered as information for identifying the content of the external service. Each of the access token and the refresh token is registered for each external service used by the user registered in the user ID.

A specific example of the external service cooperation fixed information 90 shown in FIG. 4 is shown in FIG. FIG. 8 is a diagram showing an example of the external service cooperation fixed information 90. The information included in the external service cooperation fixed information 90 is the external service identifier, the client ID, the client secret, etc., as described above. In the external service identifier, for example, Google (registered trademark), office365 (registered trademark), or the like is registered as information for identifying the content of the external service. In the client ID, for example, client1 and client2 are registered as information for identifying the client that provides the external service. The password (Secret1, Secret2) etc. individually set by the client providing the external service is registered in the client secret.

FIG. 9 shows a specific example of the user information shown in FIG. FIG. 9 is a diagram showing an example of user information. The user information is information for identifying a user registered in SI-Cloud, and includes, for example, a user ID (User0001, User0002), a user's first and last name, and the like. The user information may include a password as well as the user ID and the user's first and last name.

A specific example of the external service cooperation variation information 91 shown in FIG. 4 is shown in FIG. FIG. 10 is a diagram showing an example of the external service cooperation variation information 91. The information included in the external service cooperation fixed information 90 includes an external service identifier, scope information, an owner component, a referable component, and the like. In the external service identifier, for example, Google (registered trademark), office365 (registered trademark), or the like is registered as information for identifying the content of the external service. In the scope information, for example, among a plurality of services provided by Google (registered trademark), services (Mail, store, etc.) that specify external cooperation are registered.

Next, the operation of the information processing system 1 will be described with reference to FIGS. 11 and 12. FIG. 11 is a sequence chart for explaining the component registration operation. In step S1, the developer registers the external service cooperation information on the component development screen of the development site 100. Thereby, the external service cooperation variation information is registered in the component information management unit 105 through the management component (step S2). Of the external service cooperation information, the external service cooperation fixed information is registered in the authentication service unit 104 from the management component (step S3). In step S4, the information indicating the permission is transmitted to the development site 100 that permits the reference, and the developer knows that the reference is permitted (step S5).

Next, in step S6, when the developer sets a component to publish the external service setting on the component development screen of the development site 100, the component to be published to the management component is set (step S7), and the management component is the reference component. Then, the external service cooperation variation information is permitted to be referred to (step S8), and the permission is notified to the component development screen (step S9).

FIG. 12 is a sequence chart for explaining an authorization operation for acquiring a token from an external service. In step S11, when the end user who uses the external service makes a cooperation request (login) at the user site 102, the cooperation information is acquired from the user site 102 to the component information management unit 105 in step S12. In step S13, the external service cooperation component 1051 refers to the external service cooperation change information 91, acquires the scope information in the external service cooperation change information 91 (step S14), and transmits the scope information to the user site 102. Yes (step S15).

In step S16, when the login information, the external service identifier, and the scope information are transmitted as the authorization request from the end user, the authentication service unit 104 identifies the user (step S17) and acquires the user information (step S18). ). In step S19, the authentication service unit 104 refers to the external service cooperation fixed information and acquires the setting information such as the external service identifier (step S20). As a result, the authorization request URL is generated (step S21), and the generated authorization request URL is transmitted to the user site (step S22). The authorization request URL describes an external service such as Google (registered trademark).

When the user redirects to the authorization request URL (step S23), the authorization request is sent to the external service 103 (step S24). As a result, the user is redirected to the external service 103 (step S25), and the user calls back to the authentication service unit (step S26). The callback includes a temporary code issued by Google (registered trademark), for example. The temporary code is information for obtaining an access token and a refresh token from Google (registered trademark) or the like.

The authentication service unit refers to the user information (step S27), and acquires login information that identifies the user from the user information (step S28). Further, the authentication service unit refers to the external service cooperation fixed information (step S29) and acquires the setting information (step S30). Further, the authentication service unit requests the external service 103 to transmit the token (step S31). Since the token includes a temporary code, the external service 103 issues an access token and a refresh token (step S32). When the linkage setting is completed in this way, in step S33, the authentication service unit stores the federation information (access token or refresh token for accessing an external service) in a form associated with the user managed by the authentication service ( Step S33).

FIG. 13 is a diagram showing a configuration example according to a modified example of the information processing system 1. 13 is different from the configuration example shown in FIG. 4 in that the component information management unit 105 is configured to hold the external service cooperation fixed information and the external service cooperation variable information as external service cooperation information 91A. It is a point. That is, the information necessary for token acquisition, that is, the external service cooperation information 91A that cooperates with the external service is held in the component information management unit 105. Since the generation of the federation information is performed by the authorization service unit 1041, the information necessary for token acquisition, that is, the external service cooperation information 91A that cooperates with the external service is transmitted to the authentication service unit 104 at the timing of the authorization request. The authentication service unit 104 manages this information as temporary information. Since the external service cooperation fixed information and the external service cooperation variable information are temporarily held in the authentication service unit 104 on the cloud, confidentiality is improved.

Next, the operation of the information processing system 1 having the configuration shown in FIG. 13 will be described with reference to FIGS. 14 and 15. FIG. 14 is a sequence chart for explaining the component registration operation according to the modification of the information processing system 1. In step S11, the developer registers the external service cooperation information 91A on the component development screen of the development site 100.

As a result, the external service cooperation information 91A is registered in the component information management unit 105 through the management component (step S21). As a result, the external service cooperation information 91A is stored as temporary information from the management component in the authentication service unit 104 (step S31).

In step S4, the information indicating the permission is transmitted to the development site 100 that permits the reference, and the developer knows that the reference is permitted (step S5). In step S6, when the developer sets a component to expose the external service setting on the component development screen of the development site 100, the component to be disclosed to the management component is set (step S7), and the management component is the reference component. Reference to the external service cooperation information 91A is permitted (step S81), and notification of the permission is notified to the component development screen (step S9).

FIG. 15 is a sequence chart for explaining the authorization operation for acquiring the token from the external service in the modification of the information processing system 1. In step S11, when the end user who uses the external service makes a cooperation request (login) at the user site 102, the cooperation information is acquired from the user site 102 to the component information management unit 105 in step S12.

In steps S130 and 140, the external service cooperation component 1051 acquires the external service cooperation information 91A, and transmits the acquired external service cooperation information 91A to the user site 102 (step S150).

In step S160, when the login information, the external service identifier, and the external service cooperation information are transmitted as the authorization request from the end user, the authentication service unit 104 identifies the user (step S17) and acquires the user information ( Step S18).

The authentication service unit 104 holds the user information and the external service cooperation information as temporary information (step S190), and generates an authorization request URL based on the user information (step S210). The generated authorization request URL is transmitted to the user site (step S22).

When the user redirects to the authorization request URL (step S23), the authorization request is sent to the external service 103 (step S24). As a result, the user is redirected to the external service 103 (step S250), and the user calls back to the authentication service unit (step S260). The authentication service unit refers to the user information (step S27), and acquires login information that identifies the user from the user information (step S28).

Furthermore, the authentication service unit refers to the temporary information (external service cooperation information) (steps S290 and S300), requests the external service 103 to send a token (step S31), and the external service 103 accesses the access token and refreshes. A token is issued (step S32). When the linkage setting is completed in this way, in step S33, the authentication service unit stores the federation information (access token or refresh token for accessing an external service) in a form associated with the user managed by the authentication service ( Step S33).

As described above, the information processing system 1 according to the embodiment of the present invention includes a component that receives registration of external service cooperation information that is information that cooperates with an external service, and an external service cooperation component that manages the external service cooperation information. 1051 and an authorization service unit that acquires a token from an external service using the external service cooperation information. Components that accept registration of external service cooperation information are a reference component 1052 and a management component 1053. The external service cooperation information is the external service cooperation fixed information 90 and the external service cooperation change information 91. With this configuration, it is possible to set (register) the external service cooperation information from the UI of the developer site by using the WebAPI of the external service system 30. Therefore, the developer can immediately add the external service link information (link setting with the external service) based on the information received by the WebAPI, and can immediately develop the component that links with the external service. Becomes

The information processing program according to the embodiment uses a computer to receive registration of external service cooperation information, which is information that cooperates with an external service, a step of managing the external service cooperation information, and the external service cooperation information. , Obtaining a token from an external service, and executing the steps. According to the information processing program according to the embodiment, it becomes possible to immediately add external service cooperation information, and it is possible to immediately develop a component that cooperates with an external service.

An information processing method according to an embodiment is a computer-implemented information processing method, which includes a step of receiving registration of external service cooperation information, which is information that cooperates with an external service, and a step of managing external service cooperation information. And a step of using the external service cooperation information to obtain a token from the external service. According to the information processing method according to the embodiment, it is possible to immediately add external service cooperation information, and it is possible to immediately develop a component that cooperates with an external service.

1 information processing system, 11 client terminal, 12 mobile terminal, 14 image forming device, 15 projector, 16 device, 21 access control device, 22 print service providing device, 23 scan service providing device, 24 management setting service providing device, 25 etc. Service providing device, 30 external service, 30 external service system, 31 access control device, 32 external service providing device, 50 service providing system, 51 service app, 52 platform, 53 management data storage unit, 54 platform API, 61 print service app , 62 scan service application, 63 management setting service application, 64 service application, 72 device communication section, 74 data processing section, 81 organization management information storage section, 82 user information storage section, 84 authorization setting information storage section, 85 external service information Storage unit, 86 Authorization token information storage unit, 87 Data management information storage unit, 88 Data storage, 90 External service cooperation fixed information, 91 External service cooperation variable information, 100 Development site, 102 User site, 103 External service, 104 Authentication service Part, 105 component information management part, 500 computer system, 501 input device, 502 display device, 503 external I/F, 503a recording medium, 504 RAM, 505 ROM, 506 CPU, 507 communication I/F, 508 HDD, 1041 authorization Service unit, 1042 data storage unit, 1051 external service cooperation component, 1052 reference component, 1053 management component, 1054 component setting reception unit.

JP, 2014-92823, A

Claims (9)

A component setting reception unit that receives registration of external service cooperation information that is information that cooperates with an external service,
An external service cooperation component that manages the external service cooperation information,
An authorization service unit that acquires a token from the external service using the external service cooperation information,
An information processing system including. The information processing system according to claim 1, wherein the external service cooperation component sets the external service cooperation information in a user site. The information processing system according to claim 1 or 2, wherein the component setting reception unit publishes the external service cooperation information to another component. The information processing system according to any one of claims 1 to 3, further comprising a user site that is a UI for an end user to cooperate with an external service. The information processing system according to any one of claims 1 to 4, wherein the authorization service unit manages the access token and the refresh token acquired from the external service as federation information by associating the federation information with user information. .. 5. The external service cooperation information includes variable information whose contents change when the authorization service unit acquires a token from the external service, and fixed information whose contents do not change, according to any one of claims 1 to 4. Information processing system. The information processing system according to any one of claims 1 to 6, wherein the authorization service unit manages external service cooperation information received at the time of authorization request as temporary information. On the computer,
A step of accepting registration of external service cooperation information, which is information that cooperates with an external service,
Managing the external service cooperation information,
Acquiring a token from the external service using the external service cooperation information,
An information processing program for executing. An information processing method executed by a computer,
A step of accepting registration of external service cooperation information, which is information that cooperates with an external service,
Managing the external service cooperation information,
Acquiring a token from the external service using the external service cooperation information,
Information processing method including.

Images