# US 2022/0021539 A1 · System and method for implementing a two-sided token for open authentication

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

- Number: US 2022/0021539 A1
- Document ID: US20220021539A1
- Status: Published application
- Kind: A1
- Application number: 17/490,707
- Filed: 2021-09-30
- Published: 2022-01-20
- Earliest claimed: 2019-09-07
- Assignees: Paypal, Inc.
- Applicants: Paypal, Inc.
- Inventors: Gyanesh Pandey; Gautam Madaan
- Web page: https://patentgrep.com/patent/US20220021539A1

## CPC

- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- H04L 63/102: {Entity profiles}
- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 20/40: Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- H04L 9/0637: {Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]}
- H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates}
- H04L 9/083: {involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]}
- H04L 9/3273: {for mutual authentication (network architectures or network communication protocols for achieving mutual authentication in a packet data network H04L63/0869)}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A system and method for implementing a two-side token for OAUTH are described. A first request for access by a partner app server to user account information owned by a host server is received at a host auth server. Upon receiving authorization to share the user account information, a response is returned to the partner app sever. The response includes an access token. In response to returning the response to the partner app server, an event is written to an event queue. The event provides an indication that the request for access was received and that the corresponding response with the access token was returned. The event, when read by a host app server, instructs the host app server to submit a second request to a partner auth server for a reciprocal access token.

## Claims

### Claim 1

A host authorization server system for implementing a two-side token for open authorization (OAUTH) comprising:
a non-transitory memory storing instructions; and
one or more hardware processors coupled to the non-transitory memory and configured to read the instructions from the non-transitory memory to cause the system to perform operations comprising:
determining, in response to a first request from a partner application server for access to a first user account information for a user account maintained by a host server, an authorization to share the first user account information by the host server, wherein the first user account information includes multiple levels of access;
returning, upon determining the authorization to share the first user account information, an access token to the partner application server, wherein the access token is usable by the partner application server to access the first user account information at a first level of the multiple levels of access; and
causing, in response to returning the access token to the partner application server, a submission, from a host application server associated with the host authorization server to a partner authorization server associated with the partner application server, a second request for a reciprocal access token, wherein the reciprocal access token is usable by the host application server to access a second user account information for the user account maintained by a partner server at a second level of the multiple levels of access.

### Claim 2 (depends on 1)

The host authorization server system of claim 1, wherein causing the submission of the second request for a reciprocal access token comprises writing an event to an event queue, wherein the event, when read by the host application server, causes the second request for the reciprocal access token to be submitted to the partner authorization server.

### Claim 3 (depends on 2)

The host authorization server system of claim 2, wherein the event provides an indication that the first request for access was received and that the corresponding response with the access token was returned.

### Claim 4 (depends on 1)

The host authorization server system of claim 1, wherein the second level of the multiple levels of access is different from the first level of the multiple levels of access.

### Claim 5 (depends on 4)

The host authorization server system of claim 4, wherein the multiple levels of access correspond to multiple levels of security sensitivity of the first and second user account information, the multiple levels of security usable to determine an amount of the first user account information accessible to the partner application server, and an amount of the second user information accessible to the host application server.

### Claim 6 (depends on 1)

The host authorization server system of claim 1, wherein each of the first and second requests include at least one of a client identification, a client secret, an indication of common scopes, and an indication for two-way authorization,

### Claim 7 (depends on 6)

The host authorization server system of claim 6, wherein the first level of the multiple levels of access is defined by a first common scope of the first request, and wherein the second level of the multiple levels of access is defined by a second common scope of the second request.

### Claim 8 (depends on 7)

The host authorization server system of claim 7, wherein the first and second common scopes are asymmetrical.

### Claim 9 (depends on 7)

The host authorization server system of claim 7, wherein the common scopes is determinable by an owner of the user account.

### Claim 10

A method for implementing a two-side token for open authorization (OAUTH) comprising:
determining, in response to a first request from a partner application server for access to a first user account information for a user account maintained by a host server, an authorization to share the first user account information by the host server, wherein the first user account information includes multiple levels of access;
returning, upon determining the authorization to share the first user account information, a response to the partner application sever indicating an authorization success;
writing an access token to a host node of a host-partner shared blockchain, wherein the access token, upon being written to the host node of the host-partner shared blockchain, is synced to a partner node of the host-partner shared blockchain, and wherein the access token, upon being synced to the partner node of the host-partner shared blockchain, is made accessible to the partner application server, the access token being usable by the partner application server to access the first user account information at a first level of the multiple levels of access;
causing, in response to writing the access token to the host node, a submission, from a host application server associated with the host authorization server to a partner authorization server associated with the partner application server, a second request for a reciprocal access token, wherein the reciprocal access token is usable by the host application server to access a second user account information for the user account maintained by a partner server at a second level of the multiple levels of access.

### Claim 11 (depends on 10)

The method of claim 10, wherein causing the submission of the second request for a reciprocal access token comprises writing an event to an event queue, wherein the event, when read by the host application server, causes the second request for the reciprocal access token to be submitted to the partner authorization server.

### Claim 12 (depends on 11)

The method of claim 11, wherein the event provides an indication that the first request for access was received and that the corresponding response indicating the authorization success was returned.

### Claim 13 (depends on 10)

The method of claim 10, wherein the partner authorization server, in response to receiving the second request, writes a reciprocal access token to the partner node of the host-partner shared blockchain.

### Claim 14

The method of 13, wherein the reciprocal access token, upon being written to the partner node of the host-partner shared blockchain, is synced to a host node of the host-partner shared blockchain, and wherein the reciprocal access token, upon being synced to the host node of the host-partner shared blockchain, is accessible to the host app server.

### Claim 15 (depends on 10)

The method of claim 10, wherein the second level of the multiple levels of access is different from the first level of the multiple levels of access.

### Claim 16 (depends on 15)

method of claim 15, wherein the multiple levels of access correspond to multiple levels of security sensitivity of the first and second user account information, the multiple levels of security usable to determine an amount of the first user account information accessible to the partner application server, and an amount of the second user information accessible to the host application server.

### Claim 17

A non-transitory machine-readable medium having stored thereon machine-readable instructions executable to cause performance of operations comprising:
determining, in response to a first request from a partner application server for access to a first user account information for a user account maintained by a host server, an authorization to share the first user account information by the host server, wherein the first user account information includes multiple levels of access;
returning, upon determining the authorization to share the first user account information, an access token to the partner application server, wherein the access token is usable by the partner application server to access the first user account information at a first level of the multiple levels of access; and
causing, in response to returning the access token to the partner application server, a submission, from a host application server associated with the host authorization server to a partner authorization server associated with the partner application server, a second request for a reciprocal access token, wherein the reciprocal access token is usable by the host application server to access a second user account information for the user account maintained by a partner server at a second level of the multiple levels of access.

### Claim 18 (depends on 17)

The non-transitory machine-readable medium of claim 17, wherein causing the submission of the second request for a reciprocal access token comprises writing an event to an event queue, wherein the event, when read by the host application server, causes the second request for the reciprocal access token to be submitted to the partner authorization server.

### Claim 19 (depends on 18)

The non-transitory machine-readable medium of claim 18, wherein the event provides an indication that the first request for access was received and that the corresponding response with the access token was returned.

### Claim 20 (depends on 17)

The non-transitory machine-readable medium of claim 17, wherein the second level of the multiple levels of access is different from the first level of the multiple levels of access.
