# US 12,010,113 B1 · Authorizing front-end devices with tokens > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,010,113 B1 - Document ID: US12010113B1 - Status: Granted - Kind: B1 - Application number: 18/188,983 - Filed: 2023-03-23 - Granted: 2024-06-11 - Earliest claimed: 2023-03-23 - Assignees: Capital One Services, LLC - Applicants: Capital One Services, LLC - Inventors: Tejen Shrestha - Web page: https://patentgrep.com/patent/US12010113B1 ## CPC - G06Q 20/385: {using an alias or single-use codes} - H04L 63/0853: {using an additional device, e.g. smartcard, SIM or a different communication terminal (cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234)} - G06Q 20/38215: {Use of certificates or encrypted proofs of transaction rights} - G06Q 20/4014: {Identity check for transactions} - 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)} - H04L 63/102: {Entity profiles} - H04W 12/08: Access security - 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 - 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 In some implementations, a token client may transmit, to a token server, a request for a token associated with the front-end device and derived from a secret associated with the front-end device. The token client may receive, from the token server, the token in response to the request for the token and may transmit, to the front-end device, the token. The token client may determine an expiry associated with the token. The token client may transmit, to the token server, a request for a new token prior to the expiry associated with the token. The token client may receive, from the token server, the new token in response to the request for the new token and may transmit, to the front-end device, the new token. ## Claims ### Claim 1 A system for authorizing a front-end device, the system comprising: one or more memories; and one or more processors, coupled to the one or more memories, configured to: receive, from an input component associated with the front-end device, a request to perform an action; receive, from a storage associated with the front-end device and based on receiving the request to perform the action, a token associated with the front-end device and derived from a secret associated with the front-end device; transmit, to a proxy device, a request associated with the action and including the token; receive, from the proxy device, a message indicating a status of the action based on an authorization attempt using the token; and output, using an output component associated with the front-end device, an indication of the status. ### Claim 2 (depends on 1) The system of claim 1, wherein the one or more processors, to store the token, are configured to: store the token in a registry associated with the front-end device. ### Claim 3 (depends on 1) The system of claim 1, wherein the one or more processors, to receive the token, are configured to: transmit, to a token client, a request for authorization; and receive, from the token client, the token in response to the request for authorization. ### Claim 4 (depends on 1) The system of claim 1, wherein the one or more processors are further configured to: receive, from a token client, a new token associated with the front-end device and derived from the secret associated with the front-end device; and overwrite the token with the new token. ### Claim 5 (depends on 1) The system of claim 1, wherein the request includes the token in a header of the request. ### Claim 6 (depends on 1) The system of claim 1, wherein the one or more processors are further configured to: detect expiry of the token; transmit, to a token client, a request for authorization based on the expiry of the token; and receive, from the token client, a new token in response to the request for authorization. ### Claim 7 (depends on 6) The system of claim 6, wherein the status of the action is a failure status, and the expiry of the token is detected based on the failure status. ### Claim 8 (depends on 1) The system of claim 1, wherein the token comprises a JavaScript object notation (JSON) web token (JWT). ### Claim 9 A method of authorizing a front-end device, comprising: receiving, from the front-end device, a request for a first token associated with the front-end device and derived from a secret associated with the front-end device; transmitting, to a token server, the request; receiving, from the token server, the first token in response to the request for the first token; transmitting, to the front-end device, the first token; determining an expiry associated with the first token; transmitting, to the token server, a request for a second token prior to the expiry associated with the first token; receiving, from the token server, the second token in response to the request for the second token; and transmitting, to the front-end device, the second token. ### Claim 10 (depends on 9) The method of claim 9, further comprising: receiving, from the front-end device, a request for authorization, wherein the request for the first token is transmitted based on the request for authorization. ### Claim 11 (depends on 9) The method of claim 9, wherein transmitting the request for the second token comprises: transmitting the request for the second token according to a schedule, wherein the schedule is associated with an interval that ends earlier than the expiry associated with the first token. ### Claim 12 (depends on 9) The method of claim 9, wherein the request for the first token includes an identifier associated with the front-end device. ### Claim 13 (depends on 12) The method of claim 12, further comprising: receiving, from the front-end device, the identifier associated with the front-end device. ### Claim 14 (depends on 9) The method of claim 9, wherein the first token comprises a JavaScript object notation (JSON) web token (JWT). ### Claim 15 A non-transitory computer-readable medium storing a set of instructions for authorizing a front-end device, the set of instructions comprising: one or more instructions that, when executed by one or more processors of a device, cause the device to: receive, from a front-end device, a request, including a token associated with the front-end device, to perform an action; verify the token; transmit, to an application programming interface (API) gateway, a request associated with the action based on the token being verified, wherein the request includes an identifier of the front-end device; receive, from the API gateway, an indication of a status of the action in response to the request associated with the action; and transmit, to the front-end device, a message indicating the status. ### Claim 16 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, when executed by the one or more processors, further cause the device to: extract the token from a header of the request to perform the action. ### Claim 17 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, that cause the device to verify the token, cause the device to: perform an API call, including the token as an argument, to an authentication function; and verify the token based on a response from the authentication function. ### Claim 18 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, when executed by the one or more processors, further cause the device to: receive, from the front-end device, an additional request, including the token; determine that the token is expired; and transmit, to the front-end device, a failure message based on expiry of the token. ### Claim 19 (depends on 18) The non-transitory computer-readable medium of claim 18, wherein the one or more instructions, that cause the device to determine that the token is expired, cause the device to: perform an API call, including the token as an argument, to an authentication function; and determine that the token is expired based on a response from the authentication function. ### Claim 20 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the token comprises a JavaScript object notation (JSON) web token (JWT).