# US 2021/0176247 A1 · Device authorization systems

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

- Number: US 2021/0176247 A1
- Document ID: US20210176247A1
- Status: Published application
- Kind: A1
- Application number: 16/764,722
- Filed: 2018-11-19
- Published: 2021-06-10
- Earliest claimed: 2017-11-17
- Assignees: Light Blue Optics Ltd.
- Applicants: Light Blue Optics Ltd.
- Inventors: Euan Christopher SMITH; Julian HALL
- Web page: https://patentgrep.com/patent/US20210176247A1

## CPC

- G06F 21/445: {by mutual authentication, e.g. between devices or programs}
- H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint}
- H04L 63/0236: {Filtering by address, protocol, port number or service, e.g. IP-address or URL}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/107: {wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals}
- H04W 12/065: Continuous authentication
- H04W 12/30: Security of mobile devices; Security of mobile applications
- H04W 12/63: Location-dependent; Proximity-dependent
- 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)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A method of distributed authorization of one or more client applications to one or more connected devices. The method comprises: receiving at a connected device, from a browser executing a client application, a client token and an access request. The client token has been provided to the client application by a process comprising generating one or more client tokens, one for each of one or more client applications (a client token defines permissions for a client application and a domain hosting the client application); signing the client tokens with a private key of a client token issuer, and distributing the client tokens to the client applications; verifying a signature of the client token using a public key of the client token issuer; determining whether the client token grants the client application permission for the access request and, if permission is granted: replying to the browser with a redirect response including an access token granting permission for the client application to access the connected device and identification of the domain hosting the client application from the client token; and executing the redirect response with the browser to make the access token available to the client application for use by the client application when requesting the connected device to perform a task.

## Claims

### Claim 1

A method of distributed authorization of one or more client applications to one or more connected devices, comprising:
receiving at a connected device, from a browser executing a client application, a client token and an access request, wherein the client token has been provided to the client application by a process comprising:
generating one or more client tokens, one for each of one or more client applications, wherein a client token defines permissions for a client application and a domain hosting the client application,
signing the client tokens with a private key of a client token issuer, and distributing the client tokens to the client applications;
verifying a signature of the client token using a public key of the client token issuer;
determining whether the client token grants the client application permission for the access request and, if permission is granted:
replying to the browser with a redirect response including an access token granting permission for the client application to access the connected device and identification of the domain hosting the client application from the client token; and
executing the redirect response with the browser to make the access token available to the client application for use by the client application when requesting the connected device to perform a task.

### Claim 2 (depends on 1)

A method as claimed in claim 1 wherein executing the redirect response comprises fetching a further response from the domain hosting the client application defined in the client token.

### Claim 3 (depends on 2)

A method as claimed in claim 2 further comprising executing the further response to pass a message comprising the access token to the client application.

### Claim 4 (depends on 1)

A method as claimed in claim 1 wherein executing the redirect response comprises fetching a further response from a redirect URL and passing the access token to the domain hosting the client application defined in the client token.

### Claim 5 (depends on 4)

A method as claimed in claim 4 wherein the redirect URL defines a URL associated with the connected device.

### Claim 6 (depends on 1)

A method as claimed in claim 1 wherein the redirect response includes a fragment comprising the access token.

### Claim 7 (depends on 1)

A method as claimed in claim 1 wherein the connected device does not communicate with the client token issuer to perform the determining of whether the client token grants the client application permission for the requested access.

### Claim 8 (depends on 1)

A method as claimed in claim 1 further comprising determining whether a user is locally present at the connected device to determine whether permission for the access request is granted.

### Claim 9 (depends on 1)

A method as claimed in claim 1 further comprising:
replying to the browser with an additional redirect response to redirect the browser to a authentication service;
receiving an authentication response from the authentication service with a redirect response to redirect the browser to the connected device; and
validating the authentication response prior to replying to the browser with the redirect response including the access token.

### Claim 10 (depends on 9)

A method as claimed in claim 9 comprising determining using the authentication service whether a user is locally present at the connected device.

### Claim 11 (depends on 1)

A method as claimed in claim 1 further comprising signing the access token by the connected device.

### Claim 12 (depends on 1)

A method as claimed in claim 1 further comprising sending the access token to the connected device with a request to perform a task, and verifying the access token prior to performing the task.

### Claim 13 (depends on 1)

A method as claimed in claim 1 wherein the connected device comprises a whiteboard image capture device and wherein the access request comprises a request to access an image captured by the whiteboard image capture device and/or wherein the task comprises sending an image from the whiteboard image capture device to the client application.

### Claim at position 14

14-19. (canceled)

### Claim 20

An authorization system, the system comprising:
a non-transitory computer readable medium including instructions executable by a processor to:
receive at a connected device, from a browser executing a client application, a client token and an access request, wherein the client token has been provided to the client application by a process comprising:
generate one or more client tokens, one for each of one or more client applications, wherein a client token defines permissions for a client application and a domain hosting the client application,
sign the client tokens with a private key of a client token issuer, and distributing the client tokens to the client applications;
verify a signature of the client token using a public key of the client token issuer;
determine whether the client token grants the client application permission for the access request and, if permission is granted:
reply to the browser with a redirect response including an access token granting permission for the client application to access the connected device and identification of the domain hosting the client application from the client token to enable the browser to make the access token available to the client application for use by the client application when requesting the connected device to perform a task.

### Claim 21 (depends on 20)

The system of claim 20 wherein the non-transitory computer readable medium further comprises instructions executable by the processor to:
reply to the browser with an additional redirect response to redirect the browser to a authentication service; and
validate a authentication response from the authentication service prior to replying to the browser with the redirect response including the access token.

### Claim 22

A system comprising a plurality of devices including at least one connected device and at least one further device configured to implement a web browser, the system further comprising code executable on at least one processor to control the devices to:
receive at a connected device, from a browser executing a client application, a client token and an access request, wherein the client token has been provided to the client application by a process comprising:
generating one or more client tokens, one for each of one or more client applications, wherein a client token defines permissions for a client application and a domain hosting the client application,
signing the client tokens with a private key of a client token issuer, and distributing the client tokens to the client applications;
verify a signature of the client token using a public key of the client token issuer;
determine whether the client token grants the client application permission for the access request and, if permission is granted:
reply to the browser with a redirect response including an access token granting permission for the client application to access the connected device and identification of the domain hosting the client application from the client token; and
execute the redirect response with the browser to make the access token available to the client application for use by the client application when requesting the connected device to perform a task.

### Claim 23 (depends on 22)

The system of claim 22, wherein the code executable on the at least one processor to control the devices further executable to:
reply to the browser with an additional redirect response to redirect the browser to a authentication service;
receive an authentication response from the authentication service with a redirect response to redirect the browser to the connected device; and
validating the authentication response prior to replying to the browser with the redirect response including the access token.

### Claim 24 (depends on 23)

The system of claim 23, wherein the code executable on the at least one processor to control the devices further executable to:
determine using the authentication service whether a user is locally present at the connected device.

### Claim 25 (depends on 22)

The system of claim 22, wherein executing the redirect response comprises fetching a further response from the domain hosting the client application defined in the client token.
