Reusable Authentication Widget for Web Page Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional user authentication systems on web pages are ineffective against malicious users and phishing sites, and multi-factor authentication methods can be complex, costly, and negatively impact user experience due to additional software requirements and potential disruptions to the web page's appearance and functionality.

Innovation Solution

A reusable authentication component, such as a widget, is implemented on web pages to authenticate users by receiving and verifying user data like IP addresses, user IDs, and challenge question answers, providing mutual authentication data, and updating the user interface without refreshing the parent web page, allowing communication directly between the client and authentication server.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multi-factor authentication is implemented, then user security is improved, but device complexity and implementation cost increase

Engineering Contradiction:
Improveuser securityVSAvoidauthentication system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an authentication widget as an intermediary component that mediates between the web page and the authentication server. This widget handles all authentication logic, data exchange, and security protocols, allowing the web application to remain simple while achieving secure multi-factor authentication through the specialized authentication service layer

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The authentication widget serves multiple functions: it provides user authentication, mutual authentication to verify site legitimacy, handles multi-factor authentication protocols, and integrates seamlessly with various web pages. This universal component eliminates the need for separate authentication implementations in different web applications

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If multi-factor authentication is implemented, then user security is improved, but the user experience deteriorates due to multiple data exchanges and page refreshes

Engineering Contradiction:
Improveuser securityVSAvoiduser experience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The authentication widget maintains continuous operation within the existing web page context, eliminating interruptions through multiple page refreshes. The widget performs authentication data exchanges asynchronously, allowing the user to remain on the same web page throughout the authentication process without losing their place or experiencing disruptions

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The widget acts as an intermediary that manages the authentication communication between the user's browser and the authentication server, handling all data exchanges in the background. This mediator approach allows authentication to occur without requiring the user to manually navigate between different pages or experience repeated page reloads

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If multi-factor authentication is implemented, then user security is improved, but implementation cost increases due to additional software integration requirements

Engineering Contradiction:
Improveuser securityVSAvoidimplementation cost
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The authentication widget serves as a pre-built intermediary component that web applications can simply embed without needing to develop their own authentication systems. This eliminates the need for complex software integration work, as the widget handles all authentication logic, security protocols, and server communication in a ready-to-use package

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Instead of requiring each web application to implement its own authentication system from scratch, the patent uses a standardized authentication widget that can be copied and deployed across multiple sites. This reusable component reduces implementation costs by eliminating redundant development work while maintaining consistent security standards

Inventive Principle:
Principle #26Copying

4Reliability

If multi-factor authentication is implemented, then user security is improved, but the web page appearance and functionality are disrupted

Engineering Contradiction:
Improveuser securityVSAvoidweb page appearance
Core Design Contradiction:
ReliabilityVSShape

Solution Approach 1:

The authentication widget is nested within the existing web page structure, allowing it to blend with the page's design. The widget can be configured to match the web page's appearance and layout, ensuring that authentication functionality is integrated seamlessly without disrupting the overall visual design or user interface

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS8595809B2Reusable authentication experience tool
Publication Date: 2013.11.26 BANK OF AMERICA CORP
  • US8595809B2 patent drawing
  • US8595809B2 patent drawing
  • US8595809B2 patent drawing

AI summary

A reusable authentication component may be integrated into a web page to communicate with an authentication server and authenticate a user to the web page. The reusable authentication component may implement a complex authentication process, including multiple user interfaces to receive multiple assurances of user identity and user confirmation of previously stored mutual authentication data. The authentication process may be performed by the authentication component without refreshing or redirecting the parent web page until completion of a successful user authentication, after which the parent web page may receive authentication data and refresh to provide user specific and/or secure user data on the web page.