Extensible single point orchestration system for application program interfaces

Patent metadata

Field	Value
Publication number	US-10372518-B2
Application number	US-201816007996-A
Country	US
Kind code	B2
Filing date	Jun 13, 2018
Priority date	Mar 17, 2017
Publication date	Aug 6, 2019
Grant date	Aug 6, 2019

Abstract

An extensible single point orchestration system receives service requests from applications. In dependence upon the service request a single third party provider service or multiple third party provider services is identified. When the single third party provider service is identified, the system dynamically adapts a core capability service, using a stored configuration entity, so as to set an appropriate message format and transmit a service call message to an external API of the identified single third party provider service. When multiple third party provider services are identified, the system dynamically adapts the core capability service, using another stored configuration entity, so as to set a respective appropriate message format for parallel data transmission of service call messages to each of the respective identified third party provider services and transmits the service call messages to respective external APIs of each of the third party provider services.

First claim

We claim:

1. An extensible single point orchestration system for application program interfaces (APIs) comprising:
a processor configured to receive a service request from an application, the service request comprising a request for services and a developer API key;
the processor configured to execute a context service to generate, based on the service request, an identifier of one of a plurality of configuration entities stored in memory, a plurality of parameters, and a service type indication, the service type indication comprising an aggregation service type or a selection service type;
the processor configured to apply a first stored configuration entity identified with the identifier to a first core capability service, in response to the service type indication being the aggregation service type, and dynamically adapt the first core capability service to generate a plurality of different API specific service call messages, the different API specific service call messages comprising respective API keys for each of a plurality of different external third party provider services and at least some of the parameters, the respective API keys injected into the different API specific service call messages based on the developer API key included in the service request; and
the processor configured to apply a second stored configuration entity identified with the identifier to a second core capability service, in response to the service type indication being the selection service type, and dynamically adapt the second core capability service to generate an API specific service call message, the API specific service call message comprising an API key of only one of the plurality of different external third party provider services and at least some of the parameters, the API key injected into the API specific service call message based on the developer API key included in the service request.

2. The extensible single point orchestration system of claim 1 , wherein the respective API keys for each of the plurality of different external third party provider services and the API key of the only one of the plurality of different external third party provider services are sub-keys of the developer API key.

3. The extensible single point orchestration system of claim 1 , wherein each of the respective API keys for each of the plurality of different external third party provider services are associated with a respective external API of each of the plurality of different external third party provider services, and the API key of the only one of the plurality of different external third party provider services is associated with only an external API of the only one of the plurality of different external third party provider services.

4. The extensible single point orchestration system of claim 1 , wherein the processor is configured to dynamically inject each of the respective API keys into the different API specific service call messages by replacement of the developer API key included in the service request.

5. The extensible single point orchestration system of claim 1 , wherein the processor is further configured to execute a selection service to proxy the respective different API specific service call messages with the injected respective API key to respective external APIs of the plurality of different external third party provider services and proxy the API specific service call message with the injected API key to an external API of the only one of the plurality of different external third party provider services.

6. The extensible single point orchestration system of claim 1 , wherein the respective API keys for each of the plurality of different external third party provider services and the API key of only one of the plurality of different external third party provider services are stored in the memory in association with the application and the developer API key.

7. The extensible single point orchestration system of claim 1 , wherein the service request is directed to a plurality of service providers for aggregation services or the service request is directed to a particular service provider for selection services.

8. An extensible key management system comprising:
a processor executable to:
proxy a service call message received from an application, the service call message for an external application program interface (API) of a third party provider service;

parse the service call message;
identify a developer API key included in the service call message, the developer API key associated with the application;
retrieve a sub-key for the external API, the sub-key previously stored in association with the developer API key, the application and the external API of the third party provider service;
replace the developer API key with the sub-key for the external API; and
proxy the service call message with the sub-key to the external API of the third party provider service.

9. The extensible key management system of claim 8 , wherein the processor is further executable to:
identify a service type of the service call message as a key management type; and
identify a storage location of the sub-key in an API key storage, the API key storage comprising a plurality of sub-keys stored in association with respective identifiers of applications and external APIs with which the sub-keys are respectively used.

10. The extensible key management system of claim 9 , wherein the processor is further executable to:
identify inputs received in a developer services portal as an initiation of an association of an API proxy with the application; and
automatically obtain the sub-key for the external API of the third party provider service in response to identification of the inputs received.

11. The extensible key management system of claim 10 , wherein the processor is further executable to:
automatically link the API proxy to a context service such that the context service is selected in response to receipt of the service call message at the API proxy, the context service executable by the processor to parse the service call message and identify a developer API key included in the service call message.

12. The extensible key management system of claim 11 , wherein the context service is a plurality of context services and wherein the processor is further executable to:
select the context service from among the plurality of context services based on an association between the context service and an API proxy, the API proxy executable by the processor to proxy the service call message.

13. The extensible key management system of claim 9 , wherein the processor is further executable to:
automatically invoke a key management service within a developer services portal to automatically add the sub-key of the external API via an API gateway platform, and the key management service is invoked by the processor via the API gateway platform in response to the service call message from the application.

14. A non-transitory computer readable medium that includes instructions executable by a processor, the computer readable medium comprising:
instructions executable by the processor to associate an application with a first application program interface (API) proxy for a first external API of a first third party provider service;
instructions executable by the processor to associate the application with a second API proxy for a second external API of a second third party provider service;
instructions executable by the processor to obtain a first sub-key for the first external API when the application is associated with the first API proxy;
instructions exec

Assignees

• Accenture Global Solutions Ltd

Inventors

• O'Kennedy Steven
• Dickerson James Daniel
• Light Jeremy
• Swiecki Bogumil
• Harris Ian James
• Mallick Amit K

Classifications

• G06F9/547 Primary

  Remote procedure calls [RPC]; Web services · CPC title

• H04L63/0823

  using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263) · CPC title

• H04L63/0281

  Proxies · CPC title

• H04L9/083

  involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP] · CPC title

• H04L63/062

  for key distribution, e.g. centrally by trusted party (cryptographic mechanisms or cryptographic arrangements for key distribution involving a central third party H04L9/0819) · CPC title