Request-Specific Authentication for Web Service Resources

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In dynamic environments, existing authentication methods are inadequate as they rely on a single instance of authentication, which may not be sufficient for accessing protected resources, potentially leading to unauthorized actions that could harm the resource.

Innovation Solution

A computing system and method that employs message-specific authentication, where a client is authenticated using multiple factors, with the system determining the necessary authentication level based on the request type, ensuring that only sufficient authentication is required for the specific action being performed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a single instance of authentication is used at the outset of communications, then ease of operation is improved, but reliability deteriorates because it may not be sufficient for accessing protected resources in dynamic environments

Engineering Contradiction:
Improveease of operationVSAvoidreliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The authentication system dynamically adjusts the number and type of authentication factors required based on the specific request being processed. The server determines whether one or multiple authentication factors are needed depending on the sensitivity and nature of the requested operation, making the system adaptable rather than static.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

Different authentication requirements are applied to different requests based on their specific characteristics. High-risk operations require multiple authentication factors while low-risk operations require only one factor, allowing localized security measures tailored to each request's needs.

Inventive Principle:
Principle #3Local quality

2Reliability

If multiple authentication factors are required for all requests, then reliability is improved, but device complexity worsens

Engineering Contradiction:
ImprovereliabilityVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system applies multiple authentication factors only when necessary for specific high-risk requests, rather than requiring all requests to undergo the same extensive authentication process. This partial application of multiple factors maintains reliability for critical operations while avoiding unnecessary complexity for routine operations.

Inventive Principle:
Principle #16Partial or excessive action

3Ease of operation

If authentication requirements are fixed at the outset, then ease of operation is improved, but adaptability deteriorates in dynamic environments where different authentication levels are needed for different actions

Engineering Contradiction:
Improveease of operationVSAvoidadaptability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The authentication system transitions from a static, predetermined authentication model to a dynamic model where authentication requirements are determined at request time based on the specific operation being requested. This allows the system to adapt to different security needs while maintaining ease of operation for standard requests.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP2149102B1Request-specific authentication for accessing web service resources
Publication Date: 2023.08.23 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP2149102B1 patent drawingFigure 1
  • EP2149102B1 patent drawingFigure 2
  • EP2149102B1 patent drawingFigure 3

AI summary

Requests for access to Web service resources are evaluated based on the type of request that is received. Requests are not granted unless sufficient proof of authentication is provided to grant that request. An authentication service evaluates one or more factors to determine whether or not to authenticate the client. After being authenticated by the authentication service, proof of authentication is provided to the Web service, which grants access to the Web service resource.