# US 2024/0205225 A1 · Open id connect electronic access control system

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

- Number: US 2024/0205225 A1
- Document ID: US20240205225A1
- Status: Published application
- Kind: A1
- Application number: 18/531,975
- Filed: 2023-12-07
- Published: 2024-06-20
- Earliest claimed: 2022-12-20
- Assignees: Axis AB
- Applicants: Axis AB
- Inventors: Johnny WAHNSTRÖM; Mustafa Albayati; Aslan Murjan
- Web page: https://patentgrep.com/patent/US20240205225A1

## CPC

- G06F 21/629: {to features or functions of an application}
- H04L 63/101: {Access control lists [ACL]}
- G06F 21/604: {Tools and structures for managing or administering access control systems}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/0815: {providing single-sign-on or federations}
- H04L 63/0884: {by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity}
- G06F 2221/2141: Access rights, e.g. capability lists, access control lists, access tables, access matrices
- 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

There is provided an electronic access control system for a device. An OACS gateway is configured to obtain, via an OACS client, a request for the OACS gateway to issue a service ticket for a user agent. The OACS gateway is configured to retrieve, via an OIDC client, a profile for the user agent and an access control list for a profile and a device from the OIDC provider. The OACS gateway is configured to, responsive to having confirmed, by checking an access control list for the profile and the device, and by checking the profile itself, that the profile fulfils a permission to access a service on the device, generate a service ticket that validates the user agent for a one-time access to the service. The OACS gateway is configured to provide, via the OACS client, the service ticket towards the user agent.

## Claims

### Claim 1

An Open ID Connect electronic access control system (OACS) for a device, wherein the electronic access control system comprises an OACS client and an OACS gateway to an OIDC provider, wherein the OACS gateway implements an OIDC client, and wherein the OACS gateway is configured to:
obtain, via the OACS client, a request for the OACS gateway to issue a service ticket for a user agent, the request comprising an indication that the user agent requests to access a service on the device, wherein the service is associated with a permission;
retrieve, via the OIDC client, a profile for the user agent and an access control list for the profile and the device from the OIDC provider;
responsive to having confirmed, by checking the access control list for the profile and the device, and by checking the profile itself, that the profile fulfils the permission to access the service on the device:
generate a service ticket that validates the user agent for a one-time access to the service, wherein the service ticket is a token that is signed by the OACS gateway; and
provide, via the OACS client, the service ticket to the user agent.

### Claim 2 (depends on 1)

The electronic access control system according to claim 1, wherein the OACS gateway is configured to:
obtain, via the OACS client, an authorization request for the user agent responsive to the user agent requesting to log in to the device; and
authenticate the OICD client towards the OIDC provider by providing, via the OIDC client, a signed token to the OIDC provider.

### Claim 3 (depends on 2)

The electronic access control system according to claim 2, wherein the OACS gateway is configured to:
obtain, via the OIDC client and from the OIDC provider, a device code and a verification URL for the device, wherein the verification URL comprises an embedded user agent code that is paired with the device code; and
provide, via the OACS client, the verification URL and the device code to the user client for authenticating the user agent.

### Claim 4 (depends on 3)

The electronic access control system according to claim 3, wherein the OACS gateway is configured to:
obtain, via the OACS client, a request for a refresh token from the user agent, wherein the request comprises the device code;
retrieve, via the OIDC client, an access token and the refresh token for the user agent from the OIDC provider by providing the device code to the OIDC provider; and
provide, via the OACS client, the refresh token to the user client.

### Claim 5 (depends on 4)

The electronic access control system according to claim 4, wherein the request for the OACS gateway to issue the service ticket comprises the refresh token.

### Claim 6 (depends on 5)

The electronic access control system according to claim 5, wherein a new refresh token is retrieved, via the OIDC client, from the OIDC provider together with the profile, and wherein the new refresh token is provided, via the OACS client, together with the service ticket to the user agent.

### Claim 7 (depends on 6)

The electronic access control system according to claim 6, wherein the new refresh token is retrieved upon having verified the profile of the user agent on the access control list.

### Claim 8 (depends on 4)

The electronic access control system according to claim 4, wherein the OACS gateway is configured to:
obtain, via the OACS client, a token revocation request for the user agent responsive to the user agent requesting to log out from the device, wherein the token revocation request comprises the refresh token.

### Claim 9 (depends on 8)

The electronic access control system according to claim 8, wherein the OACS gateway is configured to:
authenticate the OIDC client towards the OIDC provider by providing, via the OIDC client, a signed token to the OIDC provider; and
provide, via the OIDC client, the refresh token and the signed token to the OIDC provider.

### Claim 10 (depends on 9)

The electronic access control system according to claim 9, wherein the OACS gateway is configured to:
obtain, via the OIDC client and from the OIDC provider, a response indicating that the refresh token has been revoked.

### Claim 11 (depends on 10)

The electronic access control system according to claim 10, wherein the OACS gateway is configured to:
provide, via the OACS client, a response towards the user client that the refresh token has been revoked and that the user agent is logged out.

### Claim 12

A method for operating an electronic access control system for a device, wherein the electronic access control system comprises an OACS client and an OACS gateway to an OIDC provider, wherein the OACS gateway implements an OIDC client, wherein the method is performed by the OACS gateway, and wherein the method comprises:
obtaining, via the OACS client, a request for the OACS gateway to issue a service ticket for a user agent, the request comprising an indication that the user agent requests to access a service on the device, wherein the service is associated with a permission;
retrieving, via the OIDC client, a profile for the user agent and an access control list for the profile and the device from the OIDC provider;
responsive to having confirmed, by checking the access control list for the profile and the device, and by checking the profile itself, that the profile fulfils the permission to access the service on the device:
generating a service ticket that validates the user agent for a one-time access to the service, wherein the service ticket is a token that is signed by the OACS gateway; and
providing, via the OACS client, the service ticket towards the user agent.

### Claim 13

A computer program for operating an electronic access control system for a device, wherein the electronic access control system comprises an OACS client and an OACS gateway to an OIDC provider, wherein the OACS gateway implements an OIDC client, the computer program comprising computer code which, when run on processing circuitry of the electronic access control system, causes the OACS gateway to:
obtain, via the OACS client, a request for the OACS gateway to issue a service ticket for a user agent, the request comprising an indication that the user agent requests to access a service on the device, wherein the service is associated with a permission;
retrieve, via the OIDC client, a profile for the user agent and an access control list for the profile and the device from the OIDC provider;
responsive to having confirmed, by checking the access control list for the profile and the device, and by checking the profile itself, that the profile fulfils the permission to access the service on the device:
generate a service ticket that validates the user agent for a one-time access to the service, wherein the service ticket is a token that is signed by the OACS gateway; and
provide, via the OACS client, the service ticket towards the user agent.

### Claim 14 (depends on 13)

A computer program according to claim 13, further including a computer readable storage medium on which the computer program is stored.
