# US 2018/0324173 A1 · Stateful session manager

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

- Number: US 2018/0324173 A1
- Document ID: US20180324173A1
- Status: Published application
- Kind: A1
- Application number: 15/585,281
- Filed: 2017-05-03
- Published: 2018-11-08
- Earliest claimed: 2017-05-03
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: VIJAY KUMAR ANANTHAPUR BACHE; VIJAY EKAMBARAM; SARAVANAN SADACHARAM
- Web page: https://patentgrep.com/patent/US20180324173A1

## CPC

- H04L 63/0815: {providing single-sign-on or federations}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Computer processors are configured to verify a unique user identification credential for a requesting user of a first client in response to receiving request for access to a microservice process from the user via the first client; create a client identification token in response to verifying a unique user identification credential for the user, and a session identification token for the request; pass the session identification token to the requesting client mapped to the client identification token; enable requested access by the first client to the requested microservice process in association with the session identification token in a session that is persisted to a session repository identified by the session identification token; and cause the requesting client to replicate the persisted session in association with the session identification token.

## Claims

### Claim 1

A computer-implemented method for federated session management, comprising executing on a computer processor:
in response to receiving a first request for access to a microservice process from a user via a first client, verifying a unique user identification credential for the user for the requesting first client;
in response to verifying the unique user identification credential for the user for the requesting first client, creating a client identification token;
creating a session identification token for the request;
mapping the session identification token to the client identification token;
passing the session identification token to the requesting client mapped to the client identification token;
enabling requested access by the first client to the requested microservice process in association with the session identification token in a session that is persisted to a session repository identified by the session identification token; and
causing the requesting client to replicate the persisted session in association with the session identification token.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
integrating computer-readable program code into a computer system comprising a processor, a computer readable memory in circuit communication with the processor, and a computer readable storage medium in circuit communication with the processor; and
wherein the processor executes program code instructions stored on the computer-readable storage medium via the computer readable memory and thereby performs the steps of verifying the unique user identification credential for the user for the requesting first client in response to receiving the first request for access to the microservice process from the user via the first client, creating the client identification token in response to verifying the unique user identification credential for the user for the requesting first client, creating the session identification token for the request, mapping the session identification token to the client identification token, passing the session identification token to the requesting client mapped to the client identification token, enabling the requested access by the first client to the requested microservice process in association with the session identification token in the session that is persisted to the session repository identified by the session identification token, and causing the requesting client to replicate the persisted session in association with the session identification token.

### Claim 3 (depends on 2)

The method of claim 2, wherein the computer-readable program code is provided as a service in a cloud environment.

### Claim 4 (depends on 1)

The method of claim 1, wherein the step of mapping the session token to the client token comprises mapping the session token to another client token that was previously created for the user via the use of another, different client request for access to the microservice process from the user.

### Claim 5 (depends on 4)

The method of claim 4, wherein the step of mapping the session token to the client token comprises mapping the session token to a single sign-on identification credential of the user, wherein the client token and the another client token are mapped to the single sign-on identification credential.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
in response to a receiving another, second request for access to the microservice process from a user via a client identified by a client identification token that is mapped to the session identification token, wherein the second request is subsequent to the first request, restoring the persisted session and enabling requested access by the client of the second request to the requested microservice process pursuant to the persisted session.

### Claim 7 (depends on 6)

The method of claim 6, wherein the steps of passing the session identification token to the requesting client mapped to the client identification token and causing the requesting client to replicate the persisted session in association with the session identification token are performed via security assertion markup language protocols.

### Claim 8 (depends on 6)

The method of claim 6, further comprising:
causing a client-side federated session manager application of the requesting client to update the replicated session in response to changes in session data at the requesting client during the enabled requested access by the first client to the requested microservice process in association with the session identification token.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
updating session data of the session persisted to the session repository and identified by the session identification token with updates made to the replicated session at client-side by the first requesting client; and
passing the updated session data of the session persisted to the session repository and identified by the session identification token to the second client to cause the second client to correspondingly update data of the persisted session replicated at the second client in association with the session identification token.

### Claim 10 (depends on 6)

The method of claim 6, wherein the step of verifying the unique user identification credential for the user for the requesting client is selected from the group consisting of lightweight data access protocol, automated deployment services and kerberos processes.

### Claim 11

A system, comprising:
a processor;
a computer readable memory in circuit communication with the processor; and
a computer readable storage medium in circuit communication with the processor;
wherein the processor executes program instructions stored on the computer-readable storage medium via the computer readable memory and thereby:
verifies a unique user identification credential for a requesting user for a requesting first client in response to receiving a first request for access to a microservice process from the requesting user via the first client;
creates a client identification token in response to verifying the unique user identification credential for the user for the requesting first client;
creates a session identification token for the request;
maps the session identification token to the client identification token;
passes the session identification token to the requesting client mapped to the client identification token;
enables requested access by the first client to the requested microservice process in association with the session identification token in a session that is persisted to a session repository identified by the session identification token; and
causes the requesting client to replicate the persisted session in association with the session identification token.

### Claim 12 (depends on 11)

The system of claim 11, wherein the processor executes the program instructions stored on the computer-readable storage medium via the computer readable memory and thereby maps the session token to the client token comprises by mapping the session token to another client token that was previously created for the user via the use of another, different client request for access to the microservice process from the user.

### Claim 13 (depends on 12)

The system of claim 12, wherein the processor executes the program instructions stored on the computer-readable storage medium via the computer readable memory and thereby maps the session token to the client token by mapping the session token to a single sign-on identification credential of the user, wherein the client token and the another client token are mapped to the single sign-on identification credential.

### Claim 14 (depends on 11)

The system of claim 11, wherein the processor executes the program instructions stored on the computer-readable storage medium via the computer readable memory and thereby:
restores the persisted session and enables requested access by a client of a second request to the requested microservice process pursuant to the persisted session, in response to a receiving another, second request for access to the microservice process from a user via the client of a second request that is identified by the client identification token that is mapped to the session identification token, wherein the second request is subsequent to the first request.

### Claim 15 (depends on 14)

The system of claim 14, wherein the processor executes the program instructions stored on the computer-readable storage medium via the computer readable memory and thereby passes the session identification token to the requesting client mapped to the client identification token and causes the requesting client to replicate the persisted session in association with the session identification token via security assertion markup language protocols.

### Claim 16 (depends on 14)

The system of claim 14, wherein the processor executes the program instructions stored on the computer-readable storage medium via the computer readable memory and thereby causes a client-side federated session manager application of the requesting client to update the replicated session in response to changes in session data at the requesting client during the enabled requested access by the first client to the requested microservice process in association with the session identification token.

### Claim 17

A computer program product for federated session management, the computer program product comprising:
a computer readable storage medium having computer readable program code embodied therewith, wherein the computer readable storage medium is not a transitory signal per se, the computer readable program code comprising instructions for execution by a processor that cause the processor to:
verify a unique user identification credential for a requesting user for a requesting first client in response to receiving a first request for access to a microservice process from the requesting user via the first client;
create a client identification token in response to verifying the unique user identification credential for the user for the requesting first client;
create a session identification token for the request;
map the session identification token to the client identification token;
pass the session identification token to the requesting client mapped to the client identification token;
enable requested access by the first client to the requested microservice process in association with the session identification token in a session that is persisted to a session repository identified by the session identification token; and
cause the requesting client to replicate the persisted session in association with the session identification token.

### Claim 18 (depends on 17)

The computer program product of claim 17, wherein the computer readable program code instructions for execution by the processor further cause the processor to map the session token to the client token comprises by mapping the session token to another client token that was previously created for the user via the use of another, different client request for access to the microservice process from the user.

### Claim 19 (depends on 18)

The computer program product of claim 18, wherein the computer readable program code instructions for execution by the processor further cause the processor to map the session token to the client token by mapping the session token to a single sign-on identification credential of the user, wherein the client token and the another client token are mapped to the single sign-on identification credential.

### Claim 20 (depends on 17)

The computer program product of claim 17, wherein the computer readable program code instructions for execution by the processor further cause the processor to restore the persisted session and enable requested access by a client of a second request to the requested microservice process pursuant to the persisted session, in response to a receiving another, second request for access to the microservice process from a user via the client of a second request that is identified by the client identification token that is mapped to the session identification token, wherein the second request is subsequent to the first request.
