Cross-Domain Session Storage via Iframe Mediator

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In cloud-based multi-tenant database systems, cross-domain session storage is challenging as session data is not accessible across different domains, leading to interruptions in applications when users switch between webpages from different domains.

Innovation Solution

Implementing an inline frame (iframe) within webpages to load documents from a host server, utilizing postMessage and onMessage APIs for cross-domain inter-frame communications, allowing session data storage and retrieval across domains, and ensuring seamless application continuity during domain switches.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If session data is stored in domain-specific storage, then security and domain isolation are maintained, but session data becomes inaccessible across different domains, causing application interruptions

Engineering Contradiction:
Improvesession continuityVSAvoidcross-domain accessibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a cross-domain storage mechanism that acts as an intermediary between domain-specific storage systems. This intermediary enables session data to be shared across different domains while maintaining the security boundaries of each domain, thus resolving the contradiction between domain isolation and cross-domain accessibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments session storage into domain-specific portions and shared portions. Each domain maintains its own session data securely, while a designated shared storage area allows specific session data to be accessed across domains when needed, thereby maintaining both security and cross-domain accessibility.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If session data is shared across all domains, then application continuity is maintained during domain switches, but security and domain isolation are compromised

Engineering Contradiction:
Improvecross-domain accessibilityVSAvoidsecurity risk
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies local quality by allowing different access permissions for different domains. Specifically, session data can be marked as accessible to certain domains while remaining restricted to others, enabling cross-domain accessibility where needed while maintaining security isolation where required.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The cross-domain storage mechanism serves as a secure intermediary that controls access to session data. It implements security protocols to verify which domains are authorized to access which session data, thus enabling cross-domain sharing without compromising overall security.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If an iframe is used to load documents from a host server, then cross-domain session storage is enabled, but system complexity increases

Engineering Contradiction:
Improvecross-domain session storageVSAvoidsystem architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent makes the iframe-based cross-domain storage mechanism universal by designing it to work with multiple domains and different types of session data. The same iframe infrastructure and storage protocol can be reused across various applications and domains, reducing the need for separate implementations and thereby managing complexity.

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

Data Source

PatentUS10693972B2Secure cross-domain session storage
Publication Date: 2020.06.23 SALESFORCE INC
  • US10693972B2 patent drawing
  • US10693972B2 patent drawing
  • US10693972B2 patent drawing

AI summary

Methods, systems, and devices for webpage domain handling are described. Some systems may include functionality for a user device to persist embedded application sessions between different webpages. For example, the user device may load a first webpage for a first domain, instantiate an inline frame (iframe) within the webpage, and run an embedded application in the webpage. Using an iframe-embedded document for a host server, the user device may store session data associated with running the application in session storage for the host server. If the user device switches to a second webpage (e.g., of a different domain) while continuing to run the application, the user device may reload the iframe and enclosed document, and may retrieve the active session data from the session storage for the host server. The user device may continue running the embedded application without interruption in the second webpage based on this session data.