Identification of invalid requests

Patent metadata

Field	Value
Publication number	US-2022012332-A1
Application number	US-202016924556-A
Country	US
Kind code	A1
Filing date	Jul 9, 2020
Priority date	Jul 9, 2020
Publication date	Jan 13, 2022
Grant date	—

Abstract

Aspects of the present invention disclose a method for handling incoming microservice requests at an application server. The method includes one or more processors identifying a microservice request of a user at an application server. The method further includes querying a database associated with the application server for a feedback history corresponding to the microservice request. The method further includes collecting a response corresponding to the microservice request of the user. The method further includes generating a rule corresponding to the microservice request based at least in part on the response corresponding to the microservice request.

First claim

What is claimed is:

1 . A method for handling incoming microservice requests at an application server, the method comprising:
identifying, by one or more processors, a first microservice request of a user at an application server; querying, by one or more processors, a database associated with the application server for a feedback history corresponding to the first microservice request; collecting, by one or more processors, a response corresponding to the first microservice request of the user; and generating, by one or more processors, a rule corresponding to the microservice request based at least in part on the response corresponding to the first microservice request.

2 . The method of claim 1 , further comprising:
in response to receiving a second microservice request, determining, by one or more processors, that the generated rule of the database corresponds to the second microservice request; and returning, by one or more processors, the response of the generated rule.

3 . The method of claim 1 , further comprising:
in response to receiving a second microservice request, determining, by one or more processors, that the second microservice request exceeds a defined request limit of the generated rule; and blocking, by one or more processors, further iterations of microservice requests of the user corresponding to the generated rule.

4 . The method of claim 1 , further comprising:
determining, by one or more processors, that the feedback history of the database associated with the application server is expired; and removing, by one or more processors, the generated rule corresponding to the feedback history from the database.

5 . The method of claim 1 , further comprising:
updating, by one or more processors, the feedback history corresponding to the microservice request of the database based at least in part on the generated rule, wherein updating the feedback history further comprises:
incrementing, by one or more processors, a counter corresponding to the first microservice request, wherein the counter is incremented in response to receiving the first microservice request at the application server; and
resetting, by one or more processors, an expiration date corresponding to the first microservice request, wherein the expiration date is a defined time period that the feedback history is valid.

6 . The method of claim 1 , wherein identifying the first microservice request of the user at the application server, further comprises:
requesting, by one or more processors, tracing of the first microservice request; and extracting, by one or more processors, input parameters corresponding to the first microservice request.

7 . The method of claim 1 , wherein querying the database associated with the application server for the feedback history corresponding to the first microservice request, further comprises:
transmitting, by one or more processors, a request for information to the database, wherein the information includes one or more feedback histories and corresponding expiration dates; determining, by one or more processors, whether a first feedback history of the one or more feedback histories of the database include textual data that is a match with input parameters corresponding to the first microservice request; and in response to determining the match, determining, by one or more processors, whether an expiration date of the first feedback history has expired.

8 . The method of claim 1 , wherein generating the rule corresponding to the first microservice request based at least in part on the response corresponding to the first microservice, further comprises:
correlating, by one or more processors, the first microservice request with a corresponding collected response; defining, by one or more processors, a request limit corresponding to the first microservice request; and setting, by one or more processors, an expiration date corresponding to the first microservice request, wherein the information is the feedback history.

9 . A computer program product for handling incoming microservice requests at an application server, the computer program product comprising:
one or more computer readable storage media and program instructions stored on the one or more computer readable storage media, the program instructions comprising: program instructions to identify a first microservice request of a user at an application server; program instructions to query a database associated with the application server for a feedback history corresponding to the first microservice request; program instructions to collect a response corresponding to the first microservice request of the user; and program instructions to generate a rule corresponding to the first microservice request based at least in part on the response corresponding to the first microservice request.

10 . The computer program product of claim 9 , further comprising program instructions, stored on the one or more computer readable storage media, to:
in response to receiving a second microservice request, determine that the generated rule of the database corresponds to the second microservice request; and return the response of the generated rule.

11 . The computer program product of claim 9 , further comprising program instructions, stored on the one or more computer readable storage media, to:
in response to receiving a second microservice request, determine that the a second microservice request exceeds a defined request limit of the generated rule; and block further iterations of microservice requests of the user corresponding to the generated rule.

12 . The computer program product of claim 9 , further comprising program instructions, stored on the one or more computer readable storage media, to:
determine that the feedback history of the database associated with the application server is expired; and remove the generated rule corresponding to the feedback history from the database.

13 . The computer program product of claim 9 , further comprising program instructions, stored on the one or more computer readable storage media, to:
update the feedback history corresponding to the first microservice request of the database based at least in part on the generated rule, wherein updating the feedback history further comprises:
increment a counter corresponding to the first microservice request, wherein the counter is incremented in response to receiving the microservice request at the application server; and
reset an expiration date corresponding to the first microservice request, wherein the expiration date is a defined time period that the feedback history is valid.

14 . The computer program product of claim 9 , wherein program instructions to identify the first microservice request of the user at the application server, further comprise program instructions to:
request tracing of the first microservice request; and extract input parameters corresponding to the first microservice request.

15 . The computer program product of claim 9 , wherein program instructions to query the database associated with the application server for the feedback history corresponding to the first microservice request, further comprise program instructions to:
transmit a request for information to the database, wherein the information includes one or more feedback histories and corresponding expiration dates; determine whether a first feedback history of the one or more feedback histories of the database include textual data that is a match with input parameters corresponding to the first micro

Assignees

• IBM

Inventors

• Dürr Thomas
• Smolny Martin
• Beck Michael
• Rapp Sandra

Classifications

• H04L63/1416

  Event detection, e.g. attack signature detection · CPC title

• H04L63/1458

  Denial of Service · CPC title

• G06F2221/034

  Test or assess a computer or a system · CPC title

• G06F21/554 Primary

  involving event detection and direct action · CPC title

• G06F16/2379

  Updates performed during online database operations; commit processing · CPC title