Secure transfer of web application client persistent state information into a new domain

• US 20160014122A1
• Filed: 08/24/2015
• Published: 01/14/2016
• Est. Priority Date: 07/08/2014
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Pieczul, Olgierd S., Pajecki, Mariusz, Pogorzelska-Pieczul, Isabela, Banatwala, Mustansir
• Granted Patent: US 9,509,691 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/0853 using an additional device, e.g. smartcard, SIM or a different communication terminal cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/166 at the transport layer
• CPC Class Codes: H04L 63/168 above the transport layer
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 67/563 Data redirection of data network streams

Abstract

A technique to reassign one or more stored elements of web application client state information is provided in an HTTP-based client upon receipt of an HTTP redirect in response to a request-URI. One or more stored elements associated to the request-URI are saved in or in association with the client. Upon receipt of an HTTP 301 (permanent) redirect, the client automatically reassigns (re-associates) the one or more stored elements to the redirect domain when the redirect can be verified as authentic (e.g., to originate from the application to which the client is attempting to connect).

Claims

1. A method to securely reassign web application client state information associated with an application server domain, comprising:

connecting to an application server domain associated with a request-URI;

responsive to receipt of a protocol-compliant redirect associated with the application server domain, the protocol-compliant redirect pointing to a new application server domain, determining whether the protocol-compliant redirect is authentic; and

responsive to a determination that the protocol-compliant redirect is authentic, reassigning the web application client state information to the new application server domain;

wherein the connecting, determining and reassignment operations are carried out in software executing in a hardware element.

2. The method as described in claim 1 wherein the web application client state information is one of:

user identifying information, one or more form elements associated with a page located at the application server domain, and a cookie generated by the application server domain.

3. The method as described in claim 1 wherein the protocol-compliant redirect is an HTTP permanent redirect.

4. The method as described in claim 1 wherein the protocol-compliant redirect is authentic if it can be verified to have originated from the application server domain to which a request-URI was directed.

5. The method as described in claim 1 wherein the determination verifies that the request-URI and the protocol-compliant redirect are communicated over a SSL-secured communication link.

6. The method as described in claim 1 wherein the determination verifies that the request-URI and the protocol-compliant redirect are communicated over a trusted communication link.

7. The method as described in claim 1 wherein the determination includes issuing a prompt to determine whether reassignment should occur;

and

determining that an affirmative response to the prompt has been received.