Authorization Server Token Encryption for Secure Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Identity and Access Management (IAM) systems face challenges in securely authenticating client applications accessing protected resources without redundant user administration, particularly in ensuring the security and anonymity of sensitive account information.

Innovation Solution

A network device and method that includes a communication interface, memory, and processing unit configured to receive a request from a client application for an access token, encrypt an authorization code using an end-user's public key, and transmit both the access token and the encrypted code, while also validating bearer tokens with digital signatures to ensure secure access to protected resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If IAM systems implement open industry standards for interoperability, then user authentication and authorization across autonomous security domains is enabled, but security risks increase due to potential vulnerabilities in standardized protocols

Engineering Contradiction:
ImproveinteroperabilityVSAvoidsecurity risks
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an authorization server as an intermediary component that mediates between client applications and protected resources. This server implements the OAuth 2.0 protocol to issue access tokens, acting as a trusted third party that enables secure cross-domain authentication without exposing direct vulnerabilities in the standardized protocol implementation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If client applications directly access protected resources, then access speed is improved, but security control is weakened due to lack of centralized authentication

Engineering Contradiction:
Improveaccess speedVSAvoidsecurity control
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent implements preliminary authentication by requiring client applications to obtain access tokens from the authorization server before accessing protected resources. This pre-authentication step ensures that security verification is completed in advance, allowing fast direct access during the actual resource operation without compromising security control.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If multiple authentication layers are implemented, then security is improved, but system complexity increases due to additional validation steps

Engineering Contradiction:
ImprovesecurityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the authentication system into distinct functional components: the authorization server that issues tokens, the client applications that present tokens, and the protected resources that validate tokens. This segmentation allows multiple authentication layers to be implemented in a modular fashion, where each component has a specific responsibility, reducing overall system complexity while maintaining strong security.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11811748B2Methods and systems for controlling access to a protected resource
Publication Date: 2023.11.07 THE TORONTO DOMINION BANK
  • US11811748B2 patent drawing
  • US11811748B2 patent drawing
  • US11811748B2 patent drawing

AI summary

A computer-implemented method is disclosed. The method includes: receiving, via a communication interface from a client application executing on a first device, a first signal including a request to obtain an access token for accessing a protected resource, the request including a public key associated with an end user; validating the request to obtain the access token; and in response to validating the request: encrypting an authorization code associated with the request using the public key to generate a first code; and transmitting, via the communication interface to the client application on the first device, a second signal including both the access token for accessing the protected resource and the first code.