# US 2022/0191188 A1 · Single sign-on enabled oauth token

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

- Number: US 2022/0191188 A1
- Document ID: US20220191188A1
- Status: Published application
- Kind: A1
- Application number: 17/684,949
- Filed: 2022-03-02
- Published: 2022-06-16
- Earliest claimed: 2018-05-31
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporation
- Inventors: Mayank Maria; Aarathi Balakrishnan; Dharmvir Singh; Madhu Martin; Vikas Pooven Chathoth; Vamsi Motukuru
- Web page: https://patentgrep.com/patent/US20220191188A1

## CPC

- H04L 63/0815: {providing single-sign-on or federations}
- G06F 21/41: where a single sign-on provides access to a plurality of computers
- 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)}
- H04L 63/108: {when the policy decisions are valid for a limited amount of time}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Techniques are described for providing session management functionalities using an access token (e.g., an Open Authorization (OAuth) access token). Upon successful user authentication, a session (e.g., a single sign-on session) is created for the user along with a user identity token that includes information identifying the session. The user identity token is presentable in an access token request sent to an access token issuer authority (e.g., an OAuth server). Upon receiving the access token request, the user identity token is parsed to identify and validate the session against information stored for the session. The validation can include various session management-related checks. If the validation is successful, the token issuer authority generates the access token. In this manner, the access token that is generated is linked to the session. The access token can then be used by an application to gain access to a protected resource.

## Claims

### Claim 1

A computer-implemented method comprising:
receiving, by an application, from an access management system, a user identity token, the user identity token including information identifying a user and a session identifier associated with an SSO session;
storing, by the application, the user identity token;
sending, by the application, to the access management system, an access token request, the access token request including the session identifier associated with the SSO session, wherein the access management system retrieves session information associated with the SSO session based on the session identifier, and determines that the SSO session is valid based on the session information;
receiving, by the application, from the access management system, if the SSO session is valid, an access token that enables the application to access to a protected resource, the access token being different from the user identity token; and
using, by the application, the access token to access the protected resource.

### Claim 2 (depends on 1)

The method of claim 1, wherein the access management system determines the SSO session is valid by determining a session expiration time based on the session information, and by determining that the session expiration time has not yet been reached.

### Claim 3 (depends on 1)

The method of claim 1, wherein the access management system determines the SSO session is valid by determining a timeout duration based on the session information, and by determining that the SSO session has not timed out based upon the timeout duration.

### Claim 4 (depends on 1)

The method of claim 1, wherein the access token request includes the user identity token.

### Claim 5 (depends on 1)

The method of claim 1, wherein the access management system determines the SSO session is valid by identifying the user associated with the SSO session based on the session information, and by determining that the user identified in the user identity token matches the user associated with the SSO session.

### Claim 6 (depends on 1)

The method of claim 1, wherein the user identity token is a JavaScript Object Notation (JSON) Web Token.

### Claim 7 (depends on 1)

The method of claim 1, wherein the access token is an Open Authorization (OAuth) access token.

### Claim 8 (depends on 1)

The method of claim 1, wherein the using the access token to access the protected resource includes providing the access token in an access request.

### Claim 9 (depends on 1)

The method of claim 1, wherein the access management system generates the access token based on the user identity token, thereby causing the access token to be linked to the SSO session.

### Claim 10 (depends on 1)

The method of claim 1, wherein the access management system includes an access manager and an OAuth server, the user identity token is generated by the access manager, and the access token is generated by the OAuth server.

### Claim 11 (depends on 1)

The method of claim 1, wherein the application is a Web-based application being executed by a computer, and further comprising:
using, by the application, the protected resource to provide application functionality.

### Claim 12 (depends on 1)

The method of claim 1, wherein the application is a data analytics program, and further comprising:
processing the protected resource to generate graphical output for display on a Web browser.

### Claim 13

A computer system comprising:
one or more processors; and
a memory coupled to the one or more processors, the memory storing instructions that, when executed by the one or more processors, cause the one or more processors to:
receive, from an access management system, a user identity token, the user identity token including information identifying a user and a session identifier associated with an SSO session;
store the user identity token;
send, to the access management system, an access token request, the access token request including the session identifier associated with the SSO session, wherein the access management system retrieves session information associated with the SSO session based on the session identifier, and determines that the SSO session is valid based on the session information;
receive, from the access management system, if the SSO session is valid, an access token that enables access to a protected resource, the access token being different from the user identity token; and
use the access token to access the protected resource.

### Claim 14 (depends on 13)

The computer system of claim 13, wherein the user identity token is received in a header of a token response or in a session cookie.

### Claim 15 (depends on 13)

The computer system of claim 13, wherein the access management system determines the SSO session is valid by determining that a session expiration time has not yet been reached, by determining that the SSO session has not timed out based upon a timeout duration, or by determining that the user identified in the user identity token matches the user associated with the SSO session.

### Claim 16 (depends on 13)

The computer system of claim 13, wherein the access token request includes the user identity token, the user identity token is a JavaScript Object Notation (JSON) Web Token, and the access token is an Open Authorization (OAuth) access token.

### Claim 17

A non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors of a computer system, cause the one or more processors to perform processing comprising:
receiving, from an access management system, a user identity token, the user identity token including information identifying a user and a session identifier associated with an SSO session;
storing the user identity token;
sending, to the access management system, an access token request, the access token request including the session identifier associated with the SSO session, wherein the access management system retrieves session information associated with the SSO session based on the session identifier, and determines that the SSO session is valid based on the session information;
receiving, from the access management system, if the SSO session is valid, an access token that enables access to a protected resource, the access token being different from the user identity token; and
using the access token to access the protected resource.

### Claim 18 (depends on 17)

The non-transitory computer-readable storage medium of claim 17, wherein the access management system determines the SSO session is valid by determining a session expiration time based on the session information and determining that the session expiration time has not yet been reached, or by determining a timeout duration based on the session information and determining that the SSO session has not timed out based upon the timeout duration.

### Claim 19 (depends on 17)

The non-transitory computer-readable storage medium of claim 17, the processing further comprising:
before sending the access token request, receiving, from the user, a request to access the protected resource.

### Claim 20 (depends on 17)

The non-transitory computer-readable storage medium of claim 17, the processing further comprising:
receiving, from the access management system, a request for user credentials;
outputting a login page on a web browser, the login page including one or more credential input fields;
receiving, from the user, the user credentials via the login page; and
sending, to the access management system, the user credentials, where the access management system authenticates the user based on the user credentials and creates the SSO session for the user in response to a successful authentication.
