# US 11,122,056 B2 · Systems and methods for binding authorization to a proxy using a get/authorize URL through a native application

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

- Number: US 11,122,056 B2
- Document ID: US11122056B2
- Status: Granted
- Kind: B2
- Application number: 16/545,153
- Filed: 2019-08-20
- Published: 2020-02-20
- Granted: 2021-09-14
- Earliest claimed: 2018-08-20
- Assignees: JPMorgan Chase Bank, N.A.
- Applicants: Jpmorgan Chase Bank, N.A.
- Inventors: Gayathri Sundar; Howard Spector; Rajitha Dissanayake
- Web page: https://patentgrep.com/patent/US11122056B2

## CPC

- H04L 63/108: {when the policy decisions are valid for a limited amount of time}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- G06F 16/00: Information retrieval; Database structures therefor; File system structures therefor
- G06F 21/00: Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F 21/335: {for accessing specific resources, e.g. using Kerberos tickets}
- H04L 63/0281: {Proxies}
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- H04L 67/53: using third party service providers
- H04L 67/56: Provisioning of proxy services (store-and-forward switching systems in data switching networks H04L12/54)
- H04L 67/563: Data redirection of data network streams
- H04W 12/06: Authentication
- H04W 12/35: {Protecting application or service provisioning, e.g. securing SIM application provisioning}
- 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)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

In one embodiment, in an information processing apparatus comprising at least one computer processor, a method for binding a GET/AUTHORIZE URL to a proxy through a native application may include: (1) receiving, at a native application executed by an electronic device, an applink call or a universal link call from a third-party application executed by the electronic device, the redirect comprising at least one parameter; (2) providing a Get/Authorize call with the at least one parameter to an API gateway; (3) receiving a 302 redirect from the API gateway; (4) providing authentication information to an authorization platform; (5) receiving an authorization code from the authorization platform; and (6) redirecting the third-party application with the redirect URL and authorization code.

## Claims

### Claim 1

A method for binding a GET/AUTHORIZE URL to a proxy through a native application, comprising:
in an information processing apparatus comprising at least one computer processor:
receiving, at a native application executed by an electronic device, an applink call or a universal link call from a third-party application executed by the electronic device, the redirect comprising at least one parameter;
providing a Get/Authorize call with the at least one parameter to an API gateway;
receiving a 302 redirect from the API gateway;
providing authentication information to an authorization platform;
receiving an authorization code from the authorization platform; and
redirecting the third-party application with the redirect URL and authorization code.

### Claim 2 (depends on 1)

The method of claim 1, wherein a first parameter comprises a redirect URL.

### Claim 3 (depends on 2)

The method of the claim 2, wherein a second parameter comprises a response type.

### Claim 4 (depends on 1)

The method of claim 1, wherein the applink call or the universal link call redirects to a website associated with a provider of the native application.

### Claim 5 (depends on 1)

The method of claim 1, wherein the applink call or the universal link call redirects to download the native application.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
receiving consent from the user to share access to a protected service with the third party; and
providing the consent to the authorization platform.

### Claim 7 (depends on 1)

The method of claim 1, wherein the authorization code is time-limited.

### Claim 8

A system for binding a GET/AUTHORIZE URL to a proxy through a native application, comprising:
an electronic device executing a native application and a third-party application;
an API gateway; and
an authorization platform;
wherein:
the native application receives an applink call or a universal link call comprising at least one parameter from the third-party application;
the native application provides the API gateway with a Get/Authorize call with the at least one parameter;
the API gateway returns a 302 redirect to the native application;
the native application provides authentication information to the authorization platform;
the native application authenticates a user of the native application;
the authorization platform provides an authorization code to the native application; and
the native application redirects the third-party application with the redirect URL and authorization code.

### Claim 9 (depends on 8)

The system of claim 8, wherein the authentication information comprises a username and password.

### Claim 10 (depends on 8)

The system of claim 8, wherein the authorization platform requests the authentication code from the API gateway.

### Claim 11 (depends on 8)

The system of claim 8, wherein the authentication code is time-limited.

### Claim 12 (depends on 8)

The system of claim 8, wherein the authorization code is returned to the native application using the redirect URL.

### Claim 13 (depends on 8)

The system of claim 8, wherein the third-party application exchanges the authorization code for an access token.

### Claim 14 (depends on 13)

The system of claim 13, wherein the third-party application exchanges the authorization token for the access token with the API gateway via a third-party backend.

### Claim 15 (depends on 8)

The system of claim 8, wherein the third-party application uses the application token to access a protected service, wherein the access token is a proxy for a user login.

### Claim 16 (depends on 8)

The system of claim 8, wherein the access token comprises a Siteminder session.