Verifier Truncation for Limited Storage Authentication

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Legacy computer systems face challenges in accommodating larger-size verifiers produced by sophisticated hash functions due to limited storage space, making it difficult to modify the operating system without disrupting mission-critical database applications.

Innovation Solution

Transforming non-conforming verifiers into conforming ones by truncation to fit within the storage limit, allowing for the use of different verifier types and flexible selection by users or administrators, while maintaining secure authentication processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If sophisticated hash functions are used to produce verifiers, then security is improved, but the verifier size exceeds the limited storage space

Engineering Contradiction:

ImprovesecurityVSAvoidverifier size

Core Design Contradiction:

ReliabilityVSVolume of stationary object

Solution Approach 1:

The patent extracts only the necessary portion of the verifier (truncating it to fit within the storage limit) while retaining enough information to perform authentication. This allows the system to use sophisticated hash functions for security while storing only the essential part of the verifier.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent changes the parameter of verifier size by transforming the original verifier into a truncated version that fits within the storage limit. This parameter transformation allows the system to accommodate larger verifiers produced by sophisticated hash functions within fixed storage constraints.

Inventive Principle:

Principle #35Parameter changes

2Adaptability or versatility

If the operating system is modified to accommodate larger verifiers, then verifier type flexibility is improved, but the operation of mission-critical database applications is disrupted

Engineering Contradiction:

Improveverifier type flexibilityVSAvoiddatabase application operation

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the authentication process into two parts: verifier generation (which can use sophisticated hash functions) and verifier storage/comparison (which uses the truncated version). This segmentation allows the system to support multiple verifier types without modifying the underlying operating system or database application structure.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary transformation process that converts sophisticated verifiers into truncated versions suitable for storage. This intermediary step allows the system to use advanced hash functions while maintaining compatibility with the existing fixed-size storage structure of the legacy operating system.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Stability of the object's composition

If fixed-size storage space is allocated for verifiers, then system stability is improved, but the ability to accommodate larger verifier types is lost

Engineering Contradiction:

Improvesystem stabilityVSAvoidverifier type accommodation

Core Design Contradiction:

Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent applies parameter transformation by changing the verifier from its original large size to a truncated size that fits within the fixed storage allocation. This allows the system to maintain stable fixed-size storage structures while accommodating different verifier types through the transformation process.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS7941671B2Method and apparatus for accommodating multiple verifier types with limited storage space

Publication Date: 2011.05.10 ORACLE INT CORP

AI summary

One embodiment of the present invention provides a system that accommodates different types of verifiers in a computer system. During operation, the system receives a username and a password. The system then computes a verifier based on the password. If the size of the verifier exceeds a storage limit, the system transforms the verifier into a transformed verifier which conforms to the storage limit, thereby allowing the computer system to compare the transformed verifier with a locally stored verifier associated with the username to facilitate user authentication.