# US 2019/0379744 A1 · Web application session security with protected session identifiers

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0379744 A1
- Document ID: US20190379744A1
- Status: Published application
- Kind: A1
- Application number: 16/002,399
- Filed: 2018-06-07
- Published: 2019-12-12
- Earliest claimed: 2018-06-07
- Assignees: Sap SE
- Applicants: Sap SE
- Inventors: Martin Johns
- Web page: https://patentgrep.com/patent/US20190379744A1

## CPC

- H04L 67/141: Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70)
- H04L 63/101: {Access control lists [ACL]}
- H04L 63/168: {above the transport layer}
- H04L 67/146: Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Various examples are directed to systems and methods for secure communication sessions between a web application and a server. A session vault routine executing at a computing device may receive a first request message directed to a server computing device. The first request message may comprise a client session identifier at a session identifier field of the first request message. The session vault routine may access supplemental session identifier data from a session vault persistence at the data storage. The session vault routine may write the supplemental session identifier data to a second field of the first request message, and initiate sending the first request message to the server computing device.

## Claims

### Claim 1

A secure communication system comprising:
a client computing device comprising a processor and a data storage associated with the processor, wherein the client computing device is programmed to perform operations comprising:
receiving, by a session vault routine executing at the client computing device, a first request message directed to a server computing device, wherein the first request message comprises a client session identifier at a session identifier field of the first request message;
accessing, by the session vault routine, supplemental session identifier data from a session vault persistence at the data storage;
writing the supplemental session identifier data to a second field of the first request message; and
initiating, by the session vault routine, sending the first request message to the server computing device with the client session identifier at the session identifier field of the first request message and the supplemental session identifier data at the second field of the first request message.

### Claim 2 (depends on 1)

The system of claim 1, wherein the session vault routine is further programmed to perform operations comprising, before writing the supplemental session identifier data to the second field of the first request message, determining that the first request message is not a cross-origin request message.

### Claim 3 (depends on 1)

The system of claim 1, wherein the session vault routine is further programmed to perform operations comprising:
writing the supplemental session identifier data to the second field of the first request message; and
determining that the first request message is not an entry-page request message.

### Claim 4 (depends on 1)

The system of claim 1, wherein the session vault routine is further programmed to perform operations comprising, before writing the supplemental session identifier data to the second field of the first request message, determining that an origin of the first request message is described by white list data.

### Claim 5 (depends on 1)

The system of claim 1, wherein the session vault routine is further programmed to perform operations comprising:
receiving, by the session vault routine, a second request message;
determining, by the session vault routine, that the second request message does not include the client session identifier; and
initiating, by the session vault routine, sending the second request message to the server computing device.

### Claim 6 (depends on 1)

The system of claim 1, wherein the session vault routine is further programmed to perform operations comprising:
receiving, by the session vault routine and from the server computing device, a response message comprising a session identifier field and a second field, wherein the session identifier field of the response message comprises the client session identifier and the second field comprises the supplemental session identifier data;
removing the supplemental session identifier data from the response message; and
initiating sending of the response message to a web application executing at the client computing device without the supplemental session identifier data.

### Claim 7 (depends on 1)

The system of claim 1, further comprising:
the server computing device, wherein the server computing device is programmed to perform operations comprising:
receiving, by a filter executing at the server computing device, the first request message with the client session identifier at the session identifier field of the first request message and the supplemental session identifier data at the second field of the first request message;
generating, by the filter, a server session identifier using the client session identifier and the supplemental session identifier data;
writing, by the filter, the server session identifier to the session identifier field of the first request message; and
initiating, by the filter, sending the first request message to a server routine with the server session identifier at the session identifier field of the first request message.

### Claim 8 (depends on 7)

The system of claim 7, wherein the generating of the server session identifier comprises concatenating the client session identifier and at least a portion of the supplemental session identifier data.

### Claim 9 (depends on 7)

The system of claim 7, wherein the server computing device is also programmed to perform operations comprising:
receiving, by the filter, a response message from the server routine, wherein the response message comprises the server session identifier at a session identifier field of the response message;
transforming the server session identifier to produce the client session identifier and the supplemental session identifier data;
writing the client session identifier to the session identifier field of the response message;
writing the supplemental session identifier data to a second field of the response message; and
initiating, by the filter, sending the response message to a web application executing at the client computing device with the client session identifier at the session identifier field and the supplemental session identifier data at the second field.

### Claim 10 (depends on 9)

The system of claim 9, wherein the client session identifier comprises a first fragment of the server session identifier and the supplemental session identifier data comprises a second fragment of the server session identifier.

### Claim 11

A method of secure communication between a web application and a server, comprising:
receiving, by a session vault routine executing at a client computing device, a first request message directed to a server computing device, wherein the first request message comprises a client session identifier at a session identifier field of the first request message;
accessing, by the session vault routine, supplemental session identifier data from a session vault persistence at a data storage of the client computing device;
writing the supplemental session identifier data to a second field of the first request message; and
initiating, by the session vault routine, sending the first request message to the server computing device with the client session identifier at the session identifier field of the first request message and the supplemental session identifier data at the second field of the first request message.

### Claim 12 (depends on 11)

The method of claim 11, further comprising, before writing the supplemental session identifier data to the second field of the first request message, determining, by the session vault routine, that the first request message is not a cross-origin request message.

### Claim 13 (depends on 11)

The method of claim 11, further comprising, before writing the supplemental session identifier data to the second field of the first request message, determining, by the session vault routine, that the first request message is not an entry-page request message.

### Claim 14 (depends on 11)

The method of claim 11, further comprising, before writing the supplemental session identifier data to the second field of the first request message, determining, by the session vault routine, that an origin of the first request message is described by white list data.

### Claim 15 (depends on 11)

The method of claim 11, further comprising:
receiving, by the session vault routine, a second request message;
determining, by the session vault routine, that the second request message does not include the client session identifier; and
initiating, by the session vault routine, sending the second request message to the server computing device.

### Claim 16 (depends on 11)

The method of claim 11, further comprising:
receiving, by the session vault routine and from the server computing device, a response message comprising a session identifier field and a second field, wherein the session identifier field of the response message comprises the client session identifier and the second field comprises the supplemental session identifier data;
removing the supplemental session identifier data from the response message; and
initiating sending of the response message to a web application executing at the client computing device without the supplemental session identifier data.

### Claim 17

A machine-readable medium comprising instructions stored thereon that, when executed by a computing device, causes the computing device to execute operations comprising:
receiving, by a session vault routine executing at the computing device, a first request message directed to a server computing device, wherein the first request message comprises a client session identifier at a session identifier field of the first request message;
accessing, by the session vault routine, supplemental session identifier data from a session vault persistence at a data storage of the computing device;
writing the supplemental session identifier data to a second field of the first request message; and
initiating, by the session vault routine, sending the first request message to the server computing device with the client session identifier at the session identifier field of the first request message and the supplemental session identifier data at the second field of the first request message.

### Claim 18 (depends on 17)

The medium of claim 17, further comprising instructions stored thereon that, when executed by a computing device, causes the computing device to execute operations comprising, before writing the supplemental session identifier data to the second field of the first request message, determining, by the session vault routine, that the first request message is not a cross-origin request message.

### Claim 19 (depends on 17)

The medium of claim 17, further comprising instructions stored thereon that, when executed by a computing device, causes the computing device to execute operations comprising:
receiving, by the session vault routine, a second request message;
determining, by the session vault routine, that the second request message does not include the client session identifier; and
initiating, by the session vault routine, sending the second request message to the server computing device.

### Claim 20 (depends on 17)

The medium of claim 17, further comprising instructions stored thereon that, when executed by a computing device, causes the computing device to execute operations comprising:
receiving, by the session vault routine and from the server computing device, a response message comprising a session identifier field and a second field, wherein the session identifier field of the response message comprises the client session identifier and the second field comprises the supplemental session identifier data;
removing the supplemental session identifier data from the response message; and
initiating sending of the response message to a web application executing at the computing device without the supplemental session identifier data.
