Securing asynchronous client server transactions

• US 8,819,787 B2
• Filed: 05/07/2013
• Issued: 08/26/2014
• Est. Priority Date: 12/15/2009
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bade, Steven A, Moss, Harold, Zurko, Mary Ellen
• Primary Examiner(s): Chea, Philip
• Assistant Examiner(s): DOLLY, KENDALL LYNN
• Application Number:
  US13/888,502
• Publication Number:
  US 20130246515A1
• Time in Patent Office: 476 Days
• Field of Search: 709/203, 726/4, 726 26- 29, 380231-234
• US Class Current: 726/4
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06F 21/30 Authentication, i.e. establishing the identity or authorisation of security principals
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 63/1466 Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 9/32 including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
• CPC Class Codes: H04W 12/06 Authentication

Abstract

A method for securing asynchronous client server transactions is provided in the illustrative embodiments. A request including an application identifier and a version of a second application is received at a first application. A service identifier is generated if a session with the second application is valid. A registry is generated at the first application. A catalog is generated based on the registry and the service identifier and the catalog are sent to the second application. A sub-request including the service identifier is received as part of an asynchronous client server transaction. Validity of the sub-request is determined by determining whether the service identifier has expired, whether the sub-request requests a service that is permissible according to the catalog, whether the service identifier is used in conjunction with the second application, or a combination thereof. If the sub-request is valid, the service is provided.

Claims

1. A computer implemented method for securing an asynchronous client server transaction, the computer implemented method comprising:

receiving a request at a first application executing in a data processing system, the request including an application identifier and a version associated with a second application;

generating a service identifier responsive to a session with the second application being valid, the session comprising the asynchronous client server transaction, and wherein the service identifier is uniquely associated with the asynchronous client server transaction;

generating a registry at the first application, the registry including information about a set of services available to execute on the data processing system and data available at the data processing system, wherein the second application is permitted to use the set of services and the data;

sending the service identifier and the information about the set of services and the data from the registry to the second application;

receiving a sub-request, the sub-request being a part of the asynchronous client server transaction, the sub-request including the service identifier;

determining a validity of the sub-request by determining whether the service identifier is used in conjunction with the second application and whether the sub-request requests a service identified in the information; and

providing, responsive to the sub-request being valid, the service in response to the sub-request.

2. The computer implemented method of claim 1 further comprising:

determining a validity of the sub-request by determining a combination of (i) whether the service identifier has expired, and (ii) whether the sub-request requests a service that is permissible for use by the second application.

3. The computer implemented method of claim 2, wherein the determining the validity further uses in the combination (iv) determining whether the information is outdated.

4. The computer implemented method of claim 2, wherein the determination whether the service identifier is used in conjunction with the second application comprises determining whether the service identifier is used together with the application identifier and the application version of the second application.

5. The computer implemented method of claim 2, further comprising:

providing, responsive to the sub-request being invalid, one of (i) a renewed service identifier, and (ii) a renewed information.

6. The computer implemented method of claim 5, wherein the renewed service identifier is one of (i) a new service identifier, (ii) the service identifier including a modified security feature, and (iii) the service identifier corresponding to a modification of the security feature validation criterion at the first application, and wherein the providing occurs before the asynchronous client server transaction is concluded.

7. The computer implemented method of claim 5, wherein the renewed information is one of (i) a new information, (ii) an update to the information, and (iii) a modification to an expiration parameter of the information, and wherein the providing occurs before the asynchronous client server transaction is concluded.

8. The computer implemented method of claim 2, further comprising:

determining whether the service requires additional authentication, forming a determination of additional authentication;

receiving additional authentication information responsive to the determination of additional authentication being true; and

determining whether the additional authentication information is valid, wherein the service is provided responsive to the additional authentication information being valid.

9. The computer implemented method of claim 2, wherein the determination whether the service is permissible according to the information by determining whether the service is permissible using the registry.

10. The computer implemented method of claim 1, further comprising:

generating an original service identifier, wherein the service identifier is a transformed version of the original service identifier.

11. A computer implemented method for securing an asynchronous client server transaction, the computer implemented method comprising:

receiving, from a first application executing on a first data processing system, at a second application executing in a second data processing system, in a session comprising the asynchronous client server transaction, a service identifier and a catalog responsive to sending an application identifier and an application version associated with the second application, the catalog including a transformed subset of a registry associated with the first application, wherein the service identifier is uniquely associated with the asynchronous client server transaction, the catalog comprising information about a set of services available to execute on the first data processing system and data available at the first data processing system, wherein the second application is permitted to use the set of services and the data;

dynamically constructing a sub-request, the sub-request being a part of the asynchronous client server transaction, the sub-request including the service identifier, and the sub-request further including a request for a service identified in the catalog;

determining a validity of the sub-request; and

receiving, responsive to the sub-request being valid according to the first application, data associated with the service.

12. The computer implemented method of claim 11, wherein the sub-request further includes the application identifier and the application version associated with the second application.

13. The computer implemented method of claim 11, further comprising:

receiving, responsive to the sub-request being invalid, one of (i) a renewed service identifier, and (ii) a renewed catalog, wherein the sub-request is invalid due to a determination that one of (i) the service identifier is invalid, (ii) the service is not within the catalog, and (iii) the catalog is outdated; and

dynamically constructing a second sub-request using one of (i) the renewed service identifier, and (ii) the renewed catalog.