API Authentication via Network Traversal Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Network-based services face challenges in securely managing API requests to prevent unauthorized access, particularly in ensuring that authentication material is only generated and used within authorized network traversals, as existing security measures are inadequate in restricting access to virtual computing resources.

Innovation Solution

Implementing a system where a token service on the customer's local network generates authentication material using a non-routable protocol, which is then sent to a service provider environment using a routable protocol, with an authentication service validating requests based on network traversal policies, such as hop count and latency, to restrict access to authorized networks only.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If authentication material is generated and transmitted using standard network protocols, then accessibility and ease of operation are improved, but security is worsened due to potential unauthorized access from external networks

Engineering Contradiction:
ImproveaccessibilityVSAvoidunauthorized access
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an authentication service as an intermediary component that sits between the token service and external API requests. This authentication service validates authentication material and enforces network traversal policies, acting as a security gatekeeper that allows legitimate access while blocking unauthorized requests without preventing the token service from being accessible within the authorized network

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements location-aware authentication by evaluating network traversal characteristics (such as hop count, latency, and network path) to determine whether an API request originates from an authorized network. This creates different authentication requirements and validation rules based on the local network context, allowing easy operation within the authorized network while providing strong security against external unauthorized access

Inventive Principle:
Principle #3Local quality

2Object-affected harmful factors

If network traversal restrictions are implemented to enhance security, then security is improved, but device complexity and system complexity increase

Engineering Contradiction:
ImprovesecurityVSAvoidsystem complexity
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The patent divides the authentication system into distinct functional components: a token service that generates authentication material, an authentication service that validates requests and enforces network traversal policies, and a clear separation between authorized and unauthorized network paths. This segmentation allows each component to focus on a specific security function, making the overall complex system manageable and maintainable

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The authentication service implements feedback mechanisms by evaluating network traversal characteristics of incoming API requests and comparing them against stored network traversal restrictions. This feedback loop automatically accepts or rejects requests based on their network origin, providing security through automated policy enforcement rather than manual configuration complexity

Inventive Principle:
Principle #23Feedback

3Object-affected harmful factors

If authentication validation is performed based on network traversal characteristics, then security is improved, but processing time and response time worsen

Engineering Contradiction:
ImprovesecurityVSAvoidresponse time
Core Design Contradiction:
Object-affected harmful factorsVSLoss of time

Solution Approach 1:

The patent performs preliminary validation by checking network traversal characteristics (such as calculating hop count and estimating latency) during the authentication process itself, rather than requiring separate validation steps later. This preliminary action integrates security checking into the existing authentication flow, providing enhanced security without adding significant processing overhead

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The authentication service changes the parameters being validated from simple credential checking to include network traversal characteristics such as hop count, latency, and network path. By evaluating these additional parameters in parallel with traditional authentication validation, the system enhances security through multi-factor verification while maintaining acceptable response times through efficient parameter evaluation

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9602482B1Authentication for an API request
Publication Date: 2017.03.21 AMAZON TECH INC
  • US9602482B1 patent drawing
  • US9602482B1 patent drawing
  • US9602482B1 patent drawing

AI summary

Technology for managing an API request is described. In an example implementation, an authentication service may receive a request to access a service. The authentication service may be configured to determine a proximity of a client device from which the request originated to the service. The authentication service may be further configured to grant the request based in part on the determined proximity of the client device to the service with respect to a policy.