# US 2019/0379675 A1 · Web application session security

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

- Number: US 2019/0379675 A1
- Document ID: US20190379675A1
- Status: Published application
- Kind: A1
- Application number: 16/002,372
- 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/US20190379675A1

## CPC

- H04L 63/126: {the source of the received data}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/0884: {by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity}
- H04L 63/1466: {Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/146: Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- 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 identifier routine executing at a computing device may receive a first request message comprising a session identifier field, the session identifier field comprising a client session identifier describing a communication session between the web application executing at the computing device and the server computing device. The session identifier routine may transform the client session identifier to a server session identifier using session identifier transformation data accessed from session vault persistence at the computing device. The session identifier routine may write the server session identifier to the session identifier field of the first request message and initiate sending the request message including the server session identifier 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 identifier routine executing at the client computing device, a first request message comprising a session identifier field, the session identifier field comprising a client session identifier describing a communication session between a web application executing at the computing device and a server computing device;
accessing, by the session identifier routine, session identifier transformation data from a session vault persistence of the client computing device;
transforming, by the session identifier routine, the client session identifier to a server session identifier using the session identifier transformation data;
writing, by the session identifier routine, the server session identifier to the session identifier field of the first request message; and
initiating, by the session identifier routine, sending the first request message including the server session identifier to the server computing device.

### Claim 2 (depends on 1)

The system of claim 1, wherein the client computing device is further programmed to perform operations comprising, before writing the server session identifier to the session identifier 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 client computing device is further programmed to perform operations comprising, before writing the server session identifier to the session identifier field of the first request message, 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 client computing device is further programmed to perform operations comprising, before writing the server session identifier to the session identifier 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 client computing device is further programmed to perform operations comprising:
receiving, by the session identifier routine, a second request message;
determining, by the session identifier routine, that the second request message does not include a client session identifier; and
initiating, by the session identifier routine, sending the second request message to the server computing device.

### Claim 6 (depends on 1)

The system of claim 1, wherein the transforming of the client session identifier to the server session identifier comprises concatenating at least a portion of the client session identifier and at least a portion of the session identifier transformation data.

### Claim 7 (depends on 1)

The system of claim 1, wherein the client computing device is further programmed to perform operations comprising:
receiving, by the session identifier routine and from the server computing device, a response message comprising a session identifier field, the session identifier field of the response message comprising the server session identifier;
transforming, by the session identifier routine, the server session identifier to the client session identifier;
writing, by the session identifier routine, the client session identifier to the session identifier field of the response message; and
sending the response message to the web application with the client session identifier at the session identifier field of the response message.

### Claim 8 (depends on 7)

The system of claim 7, wherein the transforming of the server session identifier to the client session identifier comprises splitting the server session identifier into a plurality of session identifier fragments.

### Claim 9 (depends on 8)

The system of claim 8, wherein the client session identifier comprises a first portion of the plurality of session identifier fragments and the session identifier transformation data comprises a second portion of the plurality of session identifier fragments.

### Claim 10

A method of secure communication between a web application and a server computing device, the method comprising:
receiving, by a session identifier routine executing at a computing device, a first request message comprising a session identifier field, the session identifier field comprising a client session identifier describing a communication session between the web application executing at the computing device and the server computing device;
accessing, by the session identifier routine, session identifier transformation data from a session vault persistence of the computing device;
transforming, by the session identifier routine, the client session identifier to a server session identifier using the session identifier transformation data;
writing, by the session identifier routine, the server session identifier to the session identifier field of the first request message; and
initiating, by the session identifier routine, sending the first request message including the server session identifier to the server computing device.

### Claim 11 (depends on 10)

The method of claim 10, further comprising, before writing the server session identifier to the session identifier field of the first request message, determining that the first request message is not a cross-origin request message.

### Claim 12 (depends on 10)

The method of claim 10, further comprising, before writing the server session identifier to the session identifier field of the first request message, determining that the first request message is not an entry-page request message.

### Claim 13 (depends on 10)

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

### Claim 14 (depends on 10)

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

### Claim 15 (depends on 10)

The method of claim 10, wherein the transforming of the client session identifier to the server session identifier comprises concatenating at least a portion of the client session identifier and at least a portion of the session identifier transformation data.

### Claim 16 (depends on 10)

The method of claim 10, further comprising:
receiving, by the session identifier routine and from the server computing device, a response message comprising a session identifier field, the session identifier field of the response message comprising the server session identifier;
transforming, by the session identifier routine, the server session identifier to the client session identifier;
writing, by the session identifier routine, the client session identifier to the session identifier field of the response message; and
sending the response message to the web application with the client session identifier at the session identifier field of the response message.

### Claim 17 (depends on 16)

The method of claim 16, wherein the transforming of the server session identifier to the client session identifier comprises splitting the server session identifier into a plurality of session identifier fragments.

### Claim 18 (depends on 17)

The method of claim 17, wherein the client session identifier comprises a first portion of the plurality of session identifier fragments and the session identifier transformation data comprises a second portion of the plurality of session identifier fragments.

### Claim 19

A machine-readable medium comprising instructions stored thereon that, when executed by at least one processor, causes the at least one processor to execute operations comprising:
receiving, by a session identifier routine executing at a computing device, a first request message comprising a session identifier field, the session identifier field comprising a client session identifier describing a communication session between the web application executing at the computing device and a server computing device;
accessing, by the session identifier routine, session identifier transformation data from a session vault persistence of the computing device;
transforming, by the session identifier routine, the client session identifier to a server session identifier using the session identifier transformation data;
writing, by the session identifier routine, the server session identifier to the session identifier field of the first request message; and
initiating, by the session identifier routine, sending the first request message including the server session identifier to the server computing device.

### Claim 20 (depends on 19)

The medium of claim 19, further comprising instructions stored thereon that, when executed by at least one processor, causes the at least one processor to execute operations comprising:
receiving, by the session identifier routine and from the server computing device, a response message comprising a session identifier field, the session identifier field of the response message comprising the server session identifier;
transforming, by the session identifier routine, the server session identifier to the client session identifier;
writing, by the session identifier routine, the client session identifier to the session identifier field of the response message; and
sending the response message to the web application with the client session identifier at the session identifier field of the response message.
