Authentication Data Migration via Hash Intermediary

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for migrating authentication data from an old computer system to a new one are inconvenient for users, as they often require re-registration and parallel operation of both systems, due to technical challenges and security considerations preventing direct password transfer.

Innovation Solution

A system and method where the old system generates hash values for user passwords, transfers these values to the new system, and uses them for authentication, allowing the new system to replace the hash values with plaintext passwords over time, enabling secure retirement of the old system without user re-registration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If passwords are directly transferred from the old system to the new system in plaintext, then user authentication can be seamlessly maintained, but security is compromised

Engineering Contradiction:
Improveauthentication continuityVSAvoidsecurity risk
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces hash values as an intermediary representation of passwords. Instead of transferring plaintext passwords directly, the old system generates hash values from the passwords and transfers these cryptographic representations to the new system. The new system then uses these hash values to authenticate users by comparing them against newly generated hash values, thereby maintaining authentication continuity while eliminating the security risk of plaintext password exposure.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If the new system requires users to reregister with new passwords, then security is improved, but user convenience deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoiduser convenience
Core Design Contradiction:
Object-affected harmful factorsVSEase of operation

Solution Approach 1:

The patent applies preliminary action by having the old system pre-generate hash values from user passwords before migration. These hash values are transferred to the new system in advance, enabling the new system to immediately authenticate users with their existing passwords without requiring re-registration. This preliminary preparation of authentication data allows seamless user experience while maintaining security through cryptographic hashing.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If both old and new systems operate in parallel during transition, then authentication coverage is maintained, but system complexity increases

Engineering Contradiction:
Improveauthentication coverageVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The hash value acts as a portable intermediary that bridges the old and new systems. The old system generates hash values that are transferred to and stored by the new system. During the transition period, users can authenticate against either system using the same credentials, as both systems can generate matching hash values from the same password. This intermediary mechanism enables smooth transition without requiring complex dual-system authentication logic or user re-registration.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10986084B1Authentication data migration
Publication Date: 2021.04.20 MASSACHUSETTS MUTUAL LIFE INSURANCE CO
  • US10986084B1 patent drawing
  • US10986084B1 patent drawing

AI summary

Disclosed herein are embodiments of systems, methods, and products comprises an analytic server, which retains the old passwords during security system migration. The analytic server receives strings corresponding to passwords from an old system. When a user issues a login request after the system migration, the analytic server determines the input password and computes a second string based on the input password. By comparing the second string with the string received from the old system, the analytic server determines whether input password is correct. If the second string and the received string match, the analytic server determines that the input password is the actual password and replaces the received string with the input password. In this way, the analytic server obtains the actual password, which is the original password. As a result, the analytic server retains the old password during the system migration.