Multi-factor Authentication via Third-party Notification Service

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing multi-factor authentication methods for network access are inconvenient and time-consuming for users, requiring them to launch a separate browser to enter secondary credentials, which complicates the authentication process.

Innovation Solution

A system that performs multi-factor authentication by an authentication server in conjunction with a third-party server, allowing seamless secondary user credential authentication without the need for the user to launch a browser on the client device, using contact information to obtain and verify secondary credentials through methods like SMS, email, or push notifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional multi-factor authentication is implemented requiring users to launch a separate browser to enter secondary credentials, then network security is enhanced, but user convenience and authentication time are reduced

Engineering Contradiction:
Improvenetwork securityVSAvoidauthentication process convenience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces a notification service as an intermediary component that receives authentication requests from the authentication server, generates notifications with secondary credentials, and delivers them to the user's device. This mediator handles the complex authentication flow behind the scenes, allowing users to simply approve or deny access requests through the native application interface without manually entering credentials in a separate browser.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system enables self-service authentication by allowing the notification service to automatically generate and deliver secondary credentials to the user's device. The user's device itself serves as the authentication medium, using its native notification system to present credentials and receive approval decisions, eliminating the need for manual browser interaction and credential entry.

Inventive Principle:
Principle #25Self-service

2Reliability

If traditional multi-factor authentication requiring separate browser launch is used, then security verification is strengthened, but authentication time and user effort increase

Engineering Contradiction:
Improvesecurity verificationVSAvoidauthentication time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The notification service performs preliminary actions by pre-generating secondary credentials and preparing authentication notifications before they are needed. When an authentication request is initiated, the system has already prepared the credential delivery mechanism, allowing for immediate presentation to the user without delays associated with browser launch and manual credential entry.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent replaces the mechanical interaction of manually launching a browser, navigating to authentication pages, and typing credentials with an automated electronic notification system. The native application's notification mechanism substitutes for the manual browser-based authentication flow, delivering credentials electronically and capturing user approval through automated interface interaction.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS11477186B2Multi-factor user authentication for network access
Publication Date: 2022.10.18 HEWLETT PACKARD ENTERPRISE DEV LP
  • US11477186B2 patent drawing
  • US11477186B2 patent drawing
  • US11477186B2 patent drawing

AI summary

An authentication server associated with a network authenticates a primary user credential responsive to a request from a client device to access the network. The authentication server queries a database server for contact information for obtaining a secondary user credential. The contact information is provided to a third-party authentication server to obtain and authenticate the secondary user credential. In response to both the third-party authentication server obtaining and authenticating the secondary user credential successfully and the authentication server authenticating the primary user credential successfully, the client device is granted access to the network.