Token management for asynchronous request-reply
AssigneeMicrosoft Technology Licensing, LLC
InventorsPrasham Rajeshbhai Ajmera, Izydor Gryko, Richard Jose Mejia Valencia
Life of this patent
Estimating the term…
Abstract
Token expiration is managed for requests in an asynchronous request-reply pattern of communication. If a token in a request expires, an operation to be performed utilizes a new token to execute the operation. The new token is obtained from a status check sent to a different location than the initial request.
Claims19
A system operable to manage execution of a request that outlasts token expiration in an asynchronous request-reply pattern, the system comprising:
- at least one hardware processor;
- a work process application program interface (API) executed by the at least one hardware processor to:
- receive a request from a client to perform an operation, wherein the request includes a token with an expiration;
- create a tracking key for the request;
- post the request for processing;
- and
- transmit a response to the client in response to accepting the request, wherein the response includes a reply-after time period, the tracking key, and a location to poll for a status of the request after expiration of the reply-after time period, wherein the location to poll for the status of the request is different from a location of the work process API;
- and
- a status checker API executed by the at least one hardware processor to:
- wait for a status check of the request from the client upon a determination that the token has expired;
- receive the status check for the request from the client based on the reply-after time period and the location to poll, wherein the status check includes a new token and the tracking key;
- check the status of the request using the tracking key;
- extract the new token from the status check based on the new token being needed to execute the request;
- requeue the request with the new token without issuing a certificate;
- and
- send a reply to the status check with a current status of the request.
A computer-implemented method to manage execution of a request that outlasts token expiration in an asynchronous request-reply pattern, the method comprising:
- receiving a request from a client to perform an operation at a work process application program interface (API), wherein the request includes a token with an expiration;
- creating a tracking key for the request;
- posting the request for processing;
- transmitting a response to the client indicating the response is accepted for processing,
- the response including a reply-after time period, the tracking key, and a location to poll for a status of the request after expiration of the reply-after time period,
- wherein the location to poll for the status of the request is different than a location of the work process API;
- determining that the token transmitted with the request has expired;
- waiting for a status check of the request from the client upon a determination that the token has expired;
- receiving the status check for the request from the client at the location to poll based on the reply-after time period, wherein the status check includes a new token and the tracking key;
- checking the status of the request using the tracking key;
- extracting the new token from the status check based at least on the token having expired;
- requeuing the request with the new token without issuing a certificate;
- and
- transmitting, to the client, a reply to the status check with a current status of the request.
Dependencies are inferred from the claim text.