Secured rest execution inside headless web application

A non-transitory computer-readable storage medium carrying program instructions thereon, the instructions when executed by one or more processors cause the one or more processors to perform operations comprising:

• storing, by a security gateway running on one or more servers, first credentials enabling access to a first data provider and second credentials enabling access to a second data provider;
• receiving a request message from a client application;
• determining security information required to fulfill the request message, by additional operations comprising:
• comparing the request message with respective data descriptions of data available from the first data provider and the second data provider, and
• selecting the first credentials or the second credentials, based on the comparing;
• determining fulfillment data from the first data provider or the second data provider that satisfies the request message, based, at least in part, on web application context information from the client application indicating a type of currently displayed information for a web application used by the client application;
• retrieving the fulfillment data by using the security information;
• and
• providing the fulfillment data to the client application.

An apparatus comprising:

• one or more processors;
• and
• logic encoded in one or more non-transitory computer-readable storage media for execution by the one or more processors and when executed operable to perform operations comprising:
• storing, by a security gateway running on one or more servers, first credentials enabling access to a first data provider and second credentials enabling access to a second data provider;
• receiving a request message from a client application;
• determining security information required to fulfill the request message, by additional operations comprising:
• comparing the request message with respective data descriptions of data available from the first data provider and the second data provider, and
• selecting the first credentials or the second credentials, based on the comparing;
• determining fulfillment data from the first data provider or the second data provider that satisfies the request message, based, at least in part, on web application context information from the client application indicating a type of currently displayed information for a web application used by the client application;
• retrieving the fulfillment data by using the security information;
• and
• providing the fulfillment data to the client application.