# US 2020/0396223 A1 · Client-server security enhancement using information accessed from access tokens

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

- Number: US 2020/0396223 A1
- Document ID: US20200396223A1
- Status: Published application
- Kind: A1
- Application number: 16/443,236
- Filed: 2019-06-17
- Published: 2020-12-17
- Earliest claimed: 2019-06-17
- Assignees: Microsoft Technology Licensing, LLC
- Applicants: Microsoft Technology Licensing, LLC
- Inventors: Anshul DUBE; Xiaoqin ZHU; Andrew Burke RYAN; Shankaranand ARUNACHALAM; Gokay HURMALI; Dmitri GAVRILOV; Ganesh Pandey; Parul Manek
- Web page: https://patentgrep.com/patent/US20200396223A1

## CPC

- G06F 21/335: {for accessing specific resources, e.g. using Kerberos tickets}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A service computing system receives an API call in which an authorization token, that contains an identifier in the content of the authorization token, is included in a header of the API call. The identifier is also included as a parameter passed in with the API call. The service computing system parses the API call to obtain the authorization token, and the identifier included in the authorization token. It also obtains the identifier passed in as a parameter of the API call. The service computing system compares the identifier obtained from the authorization token to the identifier passed in as a parameter of the API call to determine whether they match. If they do not match, the API call is processed as an unauthorized API call. A security system in the service computing system authorizes the API call based on the comparison.

## Claims

### Claim 1

A computing system, comprising:
a processor;
a front end system that exposes an application programming interface (API) that receives an access request requesting access to a protected resource, the access request having a header portion and a parameter portion; and
a security system that identifies a resource access token in the header portion of the access request and authorizes the access request based on information in the resource access token and in the parameter portion of the resource access request.

### Claim 2 (depends on 1)

The computing system of claim 1 wherein the security system comprises:
API header parsing logic configured to parse the header portion to identify the resource access token.

### Claim 3 (depends on 2)

The computing system of claim 2 wherein the resource access token has a content portion that includes a first identifier and wherein the parameter portion of the access request has a second identifier.

### Claim 4 (depends on 3)

The computing system of claim 3 wherein the security system comprises:
token processing logic configured to identify the first identifier in the content portion of the resource access token.

### Claim 5 (depends on 4)

The computing system of claim 4 wherein the security system comprises:
parameter parsing logic configured to identify the second identifier in the parameter portion of the access request.

### Claim 6 (depends on 5)

The computing system of claim 5 wherein the security system comprises:
identifier comparison logic configured to compare the first identifier with the second identifier and generate a comparison result indicative of the comparison; and
authorization logic configured to determine whether the access request is an authorized access request based on the comparison result.

### Claim 7 (depends on 6)

The computing system of claim 6 wherein the first and second identifiers identify a user corresponding to the protected resource.

### Claim 8 (depends on 6)

The computing system of claim 6 wherein the first and second identifiers identify an organization corresponding to the protected resource.

### Claim 9 (depends on 4)

The computing system of claim 4 wherein the resource access token has a signature portion that has a signature and wherein the token processing logic is configured to authenticate the resource access token based on the signature.

### Claim 10

A client computing system, comprising:
a processor;
token request logic that obtains an access token from a token issuer;
an application programming interface (API) call generator that generates a resource access request call to an API to request access to a protected resource, the resource access request call including a set of parameters and including, in a header portion of the resource access request call, the access token; and
a communication system that communicates the resource access request call to the API.

### Claim 11 (depends on 10)

The client computing system of claim 10 wherein the API call generator comprises:
token insertion logic configured to insert the access token in the header portion of the resource access request call, the access token including, in a content portion of the access token, a first identifier.

### Claim 12 (depends on 11)

The client computing system of claim 11 wherein the API call generator comprises:
parameter insertion logic configured to insert a second identifier in the set of parameters.

### Claim 13 (depends on 12)

The client computing system of claim 12 wherein the first and second identifiers identify a user corresponding to the protected resource.

### Claim 14 (depends on 12)

The client computing system of claim 12 wherein the first and second identifiers identify an organization corresponding to the protected resource.

### Claim 15

A computer implemented method, comprising:
exposing an application programming interface (API);
receiving, through the API, an access request requesting access to a protected resource, the access request having a header portion and a parameter portion;
identifying a resource access token in the header portion of the access request;
and authorizing the access request based on information in the resource access token and in the parameter portion of the resource access request.

### Claim 16 (depends on 15)

The computer implemented method of claim 15 wherein identifying a resource access token comprises:
parsing the header portion to identify the resource access token.

### Claim 17 (depends on 16)

The computer implemented method of claim 16 wherein authorizing comprises:
parsing a content portion of the resource access token to identify a first identifier.

### Claim 18 (depends on 17)

The computer implemented method of claim 17 wherein authorizing comprises:
parsing the parameter portion of the access request to identify a second identifier.

### Claim 19 (depends on 18)

The computer implemented method of claim 18 wherein authorizing comprises:
comparing the first identifier with the second identifier; and
generating a comparison result indicative of the comparison.

### Claim 20 (depends on 19)

The computer implemented method of claim 19 wherein authorizing comprises:
authorization logic configured to determine whether the access request is an authorized access request based on the comparison result.
