System, Product and Method for Providing Secured Access to Data

1 . A computer program product comprising a non-transitory computer readable storage medium retaining program instructions configured to cause a processor to perform actions, which program instructions implement:

receiving, by a server, from a requester, a request and a token associated with a client;

determining whether that the token is valid, wherein said determining whether the token is valid comprises determining whether the token corresponds to a stored token provided by the server to the client at most a predetermined time period prior to said receiving;

subject to a determination that the token is valid:

providing to the requester a new token to be stored by the client and used in future communications;

storing the new token;

invalidating the token; and

providing the requester with access to client data stored with a third party, wherein said access is enabled by a temporary code to be used in communication with the third party; and

subject to a determination that the token is invalid: issuing an attack alert to the client.

2 . The computer program product of claim 1 , wherein the temporary code is to be provided by the client when communicating with the third party, whereby the client is enabled to access the third party directly without divulging a persistent access code to the third party that is usable in future connection sessions.

3 . The computer program product of claim 1 , wherein the temporary code is to be used by a proxy communicating with the third party on behalf of the client.

4 . The computer program product of claim 1 , wherein the predetermined time period is between two hours and five minutes.

5 . The computer program product of claim 1 , wherein the client is configured to initiate token update in a periodic manner at least once during the predetermined time period, wherein the token update comprises: providing a valid token to the server, invalidation, by the server, of the valid token, issuing, by the server, a second valid token, and transmitting the second valid token to the client.

6 . The computer program product of claim 1 , wherein the client is an application using a Software Development Kit (SDK) to access the server.

7 . The computer program product of claim 1 , wherein the program instructions further implement:

upon client configuration with the server in relation with the third party, providing by the server to the client an initializer token, the initializer token to be used as the token on a first communication with the server, regarding the third party; and

storing the initializer token.

8 . The computer program product of claim 1 , wherein the program instructions further implement:

providing an initializer token to the client by a parent process configuring the client in relation with the third party, the initializer token to be used as the token on a first communication with the server, regarding the third party.

9 . The computer program product of claim 1 , wherein the client is implemented on a computing platform selected from the group consisting of: a cloud computing platform, and an on-premise computing platform.

10 . The computer program product of claim 1 , wherein the server is implemented on a computing platform selected from the group consisting of: a cloud computing platform, and an on-premise computing platform.

11 . A method for authenticating a client by a server, comprising:

receiving, by a server, from a requester, a request and a token associated with a client, the request related to accessing client data stored with a third party;

upon determining that the token does not correspond to a last token provided by the server to the client, or that the last token was provided by the server to the client more than a predetermined time period prior to said receiving issuing an attack alert to the client.

12 . A method for authenticating a client by a server, comprising:

receiving, by a server, from a requester, a request and a token associated with a client;

determining whether that the token is valid, wherein said determining whether the token is valid comprises determining whether the token corresponds to a stored token provided by the server to the client at most a predetermined time period prior to said receiving;

subject to a determination that the token is valid:

providing to the requester a new token to be stored by the client and used in future communications;

storing the new token;

invalidating the token; and

providing the requester with access to client data stored with a third party, wherein said access is enabled by a temporary code to be used in communication with the third party; and

subject to a determination that the token is invalid: issuing an attack alert to the client.

13 . The method of claim 12 , wherein the temporary code is to be provided by the client when communicating with the third party, whereby the client is enabled to access the third party directly without divulging a persistent access code to the third party that is usable in future connection sessions.

14 . The method of claim 12 , wherein the predetermined time period is between two hours and five minutes.

15 . The method of claim 12 , wherein the client is configured to initiate token update in a periodic manner at least once during the predetermined time period, wherein the token update comprises: providing a valid token to the server, invalidation, by the server, of the valid token, issuing, by the server, a second valid token, and transmitting the second valid token to the client.

16 . The method of claim 12 , further comprising:

upon client configuration with the server in relation with the third party, providing by the server to the client an initializer token, the initializer token to be used as the token on a first communication with the server, regarding the third party; and

storing the initializer token.

17 . The method of claim 12 , further comprising:

providing an initializer token to the client by a parent process configuring the client in relation with the third party, the initializer token to be used as the token on a first communication with the server, regarding the third party.

18 . A computerized apparatus having a processor, the processor being adapted to perform the steps of:

receiving, by a server, from a requester, a request and a token associated with a client;

determining whether that the token is valid, wherein said determining whether the token is valid comprises determining whether the token corresponds to a stored token provided by the server to the client at most a predetermined time period prior to said receiving;

subject to a determination that the token is valid:

providing to the requester a new token to be stored by the client and used in future communications;

storing the new token;

invalidating the token; and

providing the requester with access to client data stored with a third party, wherein said access is enabled by a temporary code to be used in communication with the third party; and

subject to a determination that the token is invalid: issuing an attack alert to the client.

19 . The apparatus of claim 18 , wherein the processor is further adapted to perform the steps of:

receiving, by a server, from a requester, a request and a token associated with a client, the request related to accessing client data stored with a third party;

upon determining that the token does not correspond to a last token provided by the server to the client, or that the last token was provided by the server to the client more than a predetermined time period prior to said receiving issuing an attack alert to the client.

20 . The apparatus of claim 18 , wherein

the client is implemented on a computing platform selected from the group consisting of: a cloud computing platform, and an on-premise computing platform and wherein

the server is implemented on a computing platform selected from the group consisting of: a cloud computing platform, and an on-premise computing platform.