Mobile Browser Extension Authentication via Mapped Key Exchange

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Users are required to redundantly input authentication credentials to browser extensions when accessing cloud services via mobile applications, despite the mobile application already being authenticated, due to operating system restrictions preventing credential sharing.

Innovation Solution

A browser extension on a mobile device requests an authentication key from a remote service, which is then mapped to additional data using a unique identifier and sent to a native mobile application, allowing the browser extension to authenticate without direct credential input from the user.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If the mobile application shares authentication credentials with the browser extension, then the browser extension can authenticate without redundant credential input, but the mobile operating system prevents credential sharing for security reasons

Engineering Contradiction:

Improveauthentication convenienceVSAvoidsecurity restriction

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent introduces an authentication key as an intermediary element that bridges the mobile application and browser extension. Instead of directly sharing credentials (which is blocked by OS security), the mobile application receives an authentication key from the cloud service and then shares this key with the browser extension. This intermediary mechanism allows indirect authentication while respecting OS security restrictions.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The authentication process is segmented into distinct phases: (1) mobile application authenticates with cloud service using user credentials, (2) cloud service issues an authentication key to the mobile application, (3) mobile application shares the key with the browser extension, and (4) browser extension uses the key for authentication. This segmentation allows each component to operate within security constraints while achieving the overall authentication goal.

Inventive Principle:

Principle #1Segmentation

2Reliability

If the user inputs credentials to the browser extension, then the extension can authenticate with the cloud service, but the user must redundantly input credentials even when the mobile application is already authenticated

Engineering Contradiction:

Improveauthentication capabilityVSAvoidtime for credential input

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The mobile application performs preliminary authentication with the cloud service before the browser extension needs to access any functionality. The authentication key is obtained and prepared in advance by the mobile application, so when the browser extension needs to authenticate, the key is already available for immediate use, eliminating redundant credential input and time loss.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system enables self-service authentication where the browser extension can authenticate automatically using the authentication key provided by the mobile application without requiring additional user intervention. The extension serves itself by utilizing the pre-obtained authentication key rather than requiring the user to manually input credentials again.

Inventive Principle:

Principle #25Self-service

3Adaptability or versatility

If the mobile application stores authentication credentials, then the browser extension can access them for authentication, but the operating system restricts access to credentials to prevent security breaches

Engineering Contradiction:

Improveauthentication accessVSAvoidsecurity risk

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The authentication key serves as a mediator that the mobile application receives from the cloud service and then shares with the browser extension. This intermediary approach allows the browser extension to access authentication information without the mobile application storing sensitive credentials locally, thereby reducing security risks while maintaining authentication capability.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts the sensitive credential storage function from the mobile application by using an authentication key mechanism. The mobile application no longer needs to store and manage credentials directly; instead, it receives authentication keys from the cloud service and shares these keys with the browser extension, separating the credential management function from the local device.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS20260082220A1Browser extension authentication

Publication Date: 2026.03.19 OPEN TEXT CORPORATION

AI summary

A computer-implemented method for browser extension authentication. A browser extension of a web browser on a mobile device requests an authentication key from a remote service. The browser extension receives the authentication key from the remote service. The browser extension provides the authentication key to a native mobile application on the mobile device. The native mobile application sends the remote service data to be mapped to the authentication key as mapped data. The browser extension requests the mapped data corresponding to the authentication key and receives the mapped data. The browser extension authenticates using the mapped data received from the remote service.