Browser Script Authentication for Private Network Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network authentication methods rely on browser plug-ins, which are being discontinued due to security concerns, particularly those using the Netscape Plugin API, rendering them unsuitable for future authentication processes.

Innovation Solution

A client device authenticates to a private network by executing a browser program that downloads a script to establish a connection with a local host program, collecting authentication information such as device-specific details or connection state, and communicates this information to a server for authentication, without relying on browser plug-ins.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If browser plug-ins are used for authentication, then authentication functionality is provided, but security vulnerabilities and compatibility issues arise due to discontinuation of support

Engineering Contradiction:
Improveauthentication reliabilityVSAvoidsecurity vulnerabilities
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts the authentication functionality from the browser plug-in environment and relocates it to the browser's native JavaScript execution environment. The authentication script runs directly in the browser without requiring external plug-ins, thereby eliminating security vulnerabilities associated with plug-in discontinuation while maintaining authentication reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an authentication script as an intermediary between the browser and the authentication server. This script mediates the authentication process by collecting device information, establishing connections with local host programs, and communicating with the server, replacing the need for browser plug-ins while preserving authentication functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If browser plug-ins are used for authentication, then device authentication is enabled, but device complexity increases due to plug-in installation and configuration requirements

Engineering Contradiction:
Improveauthentication capabilityVSAvoidplug-in installation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The authentication system performs self-service by automatically downloading and executing the authentication script within the browser's existing JavaScript environment. The script automatically collects device information and establishes necessary connections without requiring users to manually install or configure additional plug-ins, thereby reducing device complexity while maintaining authentication capability.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent leverages the browser's universal JavaScript execution capability to perform authentication functions that previously required specialized plug-ins. By using the browser's existing, universally-supported script execution feature, the system achieves authentication capability without adding specialized components, thereby reducing device complexity.

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

3Reliability

If traditional authentication methods are used, then user identity verification is performed, but device verification capability is lacking

Engineering Contradiction:
Improveidentity verification accuracyVSAvoiddevice verification capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent merges user identity verification with device verification into a single integrated authentication process. The authentication script collects both user credentials and device-specific information (such as device identifiers, operating system details, and browser characteristics) and submits them together to the server, enabling simultaneous verification of both user identity and device authorization.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The authentication process is segmented into distinct components: user credential collection, device information gathering, connection establishment with local host programs, and server verification. This segmentation allows the system to independently verify both user identity and device characteristics, enhancing both identity verification accuracy and device verification capability.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10348799B2Unique device authentication via a browser
Publication Date: 2019.07.09 CA TECH INC
  • US10348799B2 patent drawing
  • US10348799B2 patent drawing
  • US10348799B2 patent drawing

AI summary

Techniques are disclosed relating to unique device authentication via browser. In one embodiment, a server computer system receives, from a browser program executing on a client computer system, a request to authenticate to a private network. The server computer system causes a script to be downloaded to the client computer system, the script being executable by the browser program to establish a connection with a local host program executing on the client computer system. The server computer system receives, from the browser program, authentication information that is based on communication between the browser program and the local host program over the connection. The server computer system may then perform a process responsive to the request to authenticate the client computer system to the private network using the received authentication information. In some embodiments, the authentication information includes an identifier that uniquely identifies the client computer system within the private network.