US 10,097,562 B2Granted

Service token handling

AssigneeSap SE

InventorsApoorv Bhargava, Aswin Kumar Jayaraman, Raghavendra Rao M G, Naveed Mohammed, Markus Schmidt-Karaca

Life of this patent

Estimating the term…

Loading patent…

Abstract

A system includes reception, at a server and in a first browser session, of a request from a client for a token to access a first software service, determination of a token stored in a server memory of the server and associated with the first service and the client, determination, at the server, of whether a validity period of the token is within a predetermined period of expiration, and, if it is determined that the validity period of the token is within a predetermined period of expiration, transmission of a request for a new token to access the first software service from a token provider associated with the first service, reception of the new token from the token provider, and provision of the new token to the client in the first browser session.

Claims15

Dependent claims

A system comprising:

a memory storing processor-executable program code;
and
a processor to execute the processor-executable program code in order to cause the computing system to:
receive, at a server and in a first browser session, a request from a client application for a token to access a first software service provided by the server based on an application executing on the server;
determine a token is stored in a server memory of the server and is associated
with the first software service and the client application;
determine, by the server, whether a validity period for the token is within a predetermined period of expiration of the token;
in the instance it is determined that the validity period of the token is within a predetermined period of expiration of the token:
transmit, by the server, a request for a new token to access the first software service from a token provider associated with the first software service;
receive the new token to access the first software service from the token provider;
and
provide the new token to the client application in the first browser session, the client application to call the first software service provided by the server using the new token;
and
in parallel with the receiving of the request from the client application:
receive, at the server and in a second browser session, a request from a second client application for a token to access the first software service;
determine a second token stored in the server memory and associated with the first software service and the second client application;
determine, at the server, whether a second validity period of the second token is within a second predetermined period of expiration;
and
in an instance it is determined that the second validity period of the second token is within a second predetermined period of expiration:
transmit a second request for a second new token to access the first software service from the token provider associated with the first software service;
receive the second new token from the token provider;
and
provide the second new token to the second client application in the second browser session.

20 more elements

A computer-implemented method, the method comprising:

receiving, at a server and in a first browser session, a request from a client application for a token to access a first software service provided by the server based on an application executing on the server;
determining, by the server, a token is stored in a server memory of the server and is associated with the first service and the client application;
determining, by the server, whether a validity period of the token is within a predetermined period of expiration of the token;
whether it is determined that the validity period of the token is within a predetermined period of expiration of the token:
transmitting a request for a new token to access the first software service from a token provider associated with the first service;
receiving the new token to access the first software service from the token provider;
and
providing the new token to the client application in the first browser session, the client application to call the first software service provided by the server using the new token;
and
in parallel with the receiving of the request from the client application:
receiving, at the server and in a second browser session, a request from a second client application for a token to access the first software service;
determining a second token stored in the server memory and associated with the first software service and the second client application;
determining, at the server, whether a second validity period of the second token is within a second predetermined period of expiration;
and
in an instance it is determined that the second validity period of the second token is within a second predetermined period of expiration:
transmitting a second request for a second new token to access the first software service from the token provider associated with the first software service;
receiving the second new token from the token provider;
and
providing the second new token to the second client application in the second browser session.

16 more elements

A non-transitory computer-readable medium storing program code, the program code executable by a processor of a computing system to cause the computing system to:

receive, at a server and in a first browser session, a request from a client application for a token to access a first software service provided by the server based on an application executing on the server;
determine a token is stored in a server memory of the server and is associated with the first software service and the client application;
determine, by the server, whether a validity period for the token is within a predetermined period of expiration of the token;
in the instance it is determined that the validity period of the token is within a predetermined period of expiration of the token:
transmit a request for a new token to access the first software service from a token provider associated with the first software service;
receive the new token to access the first software service from the token provider;
and
provide the new token to the client application in the first browser session, the client application to call the first software service provided by the server using the new token;
and
in parallel with the receiving of the request from the client application:
receive, at the server and in a second browser session, a request from a second client application for a token to access the first software service;
determine a second token stored in the server memory and associated with the first software service and the second client application;
determine, at the server, whether a second validity period of the second token is within a second predetermined period of expiration:
and
in an instance it is determined that the second validity period of the second token is within a second predetermined period of expiration:
transmit a second request for a second new token to access the first software service from the token provider associated with the first software service:
receive the second new token from the token provider:
and
provide the second new token to the second client application in the second browser session.

16 more elements

Dependencies are inferred from the claim text.

Facts

Application: 15/148,165Filed 6 May 2016
Published: US 2017/0324749 A19 Nov 2017
Granted: 9 Oct 2018
Term ends: Not estimatedThe source records don’t support an estimate.

Classification6 codes

H04L 63/108
For controlling access to devices or network resources: when the policy decisions are valid for a limited amount of time
H04L 63/062
For supporting key management in a packet data network: for key distribution, e.g. centrally by trusted party
H04L 63/068
For supporting key management in a packet data network: using time-dependent keys, e.g. periodically changing keys
H04L 63/123
Applying verification of the received information: received data contents, e.g. message integrity