Local Server Self-Signed Certificates for Mixed Content Compliance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Web browsers implement mixed content security policies that prevent web pages loaded via HTTPS from making HTTP requests or WebSocket connections to local services, blocking communication with local services.

Innovation Solution

A system and method for generating self-signed certificates to establish secure socket connections between a web browser and a local service, using a self-signed certificate authority (CA) certificate and local server Transport Layer Security (TLS) certificates, allowing compliance with mixed content security policies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a web page loaded via HTTPS makes HTTP requests or WebSocket connections to local services, then content transfer and manipulation capabilities are enabled, but the connection is blocked by mixed content security policies

Engineering Contradiction:
Improvecontent transfer capabilityVSAvoidconnection validity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a local server acting as an intermediary between the web page and the remote service. The local server receives HTTP requests from the web page, translates them into WebSocket connections to the remote service, and forwards the communication. This intermediary approach allows HTTPS web pages to access local services without directly violating mixed content security policies, as the local server operates within the same origin context.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the connection establishment process into multiple stages: first establishing a secure WebSocket connection to the remote service, then creating a local server instance that handles the actual content transfer. This segmentation allows the system to maintain security compliance while enabling the desired content transfer functionality through separate, manageable components.

Inventive Principle:
Principle #1Segmentation

2Reliability

If self-signed certificates are generated and stored in the browser's certificate store, then secure socket connections to local services are enabled, but the device complexity increases

Engineering Contradiction:
Improveconnection securityVSAvoidcertificate management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements self-service by having the local server generate and store its own self-signed certificates automatically. The server creates a private key pair, generates a certificate signed by itself (CA certificate), and stores it in the browser's certificate store without requiring manual intervention or external certificate authorities. This automation reduces operational complexity while maintaining security.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent performs preliminary actions by pre-generating and pre-storing the self-signed CA certificate and server certificate before the actual WebSocket connection is established. The local server creates these certificates during initialization, so they are ready for immediate use when the browser needs to establish a secure connection, eliminating the need for runtime certificate generation or user configuration.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12388660B2System and method for a local server with self-signed certificates
Publication Date: 2025.08.12 OPEN TEXT CORP
  • US12388660B2 patent drawing
  • US12388660B2 patent drawing
  • US12388660B2 patent drawing

AI summary

A system comprising a processor and a computer readable memory coupled to the processor, the computer-readable memory comprising computer program code executable by the processor to generate create a self-signed certificate, create a second certificate using the set of certificate generation parameters, the second certificate linked to the self-signed certificate, store the self-signed certificate in a certificate store of a first web browser; and store the second certificate in a local server certificate store to allow a local service to use the second certificate in a handshake to establish a secure socket connection with the first web browser in compliance with a mixed content security policy of the first web browser.