Dynamic Credential Update Framework

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing authentication frameworks, such as EAP, require specific credential management for each authentication method, complicating the process and user experience, and do not allow for dynamic updating of credentials independently of the authentication method.

Innovation Solution

A generic authentication framework with a credential interface that allows authentication components to describe required credentials, enabling applications to manage and collect credentials independently, improving user experience and facilitating dynamic updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a generic authentication framework with credential interface is implemented, then credential management flexibility and user experience are improved, but device complexity increases

Engineering Contradiction:

Improvecredential management flexibilityVSAvoidauthentication framework complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The authentication framework is segmented into distinct components: a credential interface layer that handles credential acquisition independently, an authentication component that executes protocols, and an application layer that consumes authentication services. This segmentation allows each component to be developed, maintained, and updated independently, improving flexibility while managing complexity through modular architecture.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

A credential interface acts as an intermediary between applications and authentication components. This intermediary layer abstracts the complexity of credential acquisition and management, providing a standardized interface that applications can use without directly implementing authentication logic. The credential interface mediates between the application's needs and the authentication framework's capabilities, improving adaptability while containing complexity within the interface layer.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Duration of action of moving object

If credential acquisition is decoupled from authentication execution, then dynamic credential updates are enabled, but coordination overhead between components increases

Engineering Contradiction:

Improvecredential update timing flexibilityVSAvoidcomponent coordination complexity

Core Design Contradiction:

Duration of action of moving objectVSDevice complexity

Solution Approach 1:

Credentials are acquired and validated in advance through the credential interface before authentication execution begins. The credential interface performs preliminary checks, retrieves credentials from secure storage, and prepares them for use. This preliminary action enables credentials to be updated independently of the authentication flow, as long as the update occurs before authentication execution, providing timing flexibility while maintaining coordination through the predefined interface contract.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The credential interface is designed to be dynamic, allowing credentials to be retrieved, updated, or refreshed during the authentication process without requiring changes to the authentication component itself. The interface can adapt to different credential types, sources, and update mechanisms, enabling flexible credential management while the authentication component remains stable and coordinated through standardized interface calls.

Inventive Principle:

Principle #15Dynamics

3Reliability

If each EAP method handles credential acquisition independently, then authentication protocol specificity is maintained, but overall system complexity and difficulty of implementation increase

Engineering Contradiction:

Improveauthentication protocol accuracyVSAvoidimplementation complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The credential interface is designed as a universal component that can serve multiple EAP methods and authentication protocols. Instead of each EAP method implementing its own credential acquisition logic, the credential interface provides a common mechanism that adapts to different protocol requirements through configuration and parameter passing. This multi-functionality maintains protocol specificity through interface parameters while reducing implementation complexity by sharing the core credential acquisition infrastructure across all protocols.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS7941831B2Dynamic update of authentication information

Publication Date: 2011.05.10 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

A framework is provided that decouples credential acquisition from authentication processes using those credentials in a way that facilitates dynamic update of credential information. An authentication component may receive credential information for authentication of a user or a device for access to a resource. During interactions with an external authenticator, the authentication component may identify that updated credential information is required and issue a request to the application including credential parameters defining the updated credential information. An application component receiving the request may acquire updated credential information from a user or another entity. In addition, the authentication method may issue notifications to the application. The framework enables the application to update credentials in a context specific way.