Cross-Domain Web App Data Sharing via Browser Mediator
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for data communication between web applications across different domains require a third-party intervention, leading to performance, configuration, and security issues, especially when pages are hosted under different domains and operated by various actors.
Innovation Solution
Implementing a method where web applications use a local database within the browser to share data, with access restricted to modules from the same domain, allowing secure data sharing without external entities, leveraging HTML5 standard secure storage capabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a third-party entity is used to enable data sharing between web applications from different domains, then data communication between domains is enabled, but performance deteriorates, configuration becomes complex, and security issues arise
Solution Approach 1:
The patent introduces a mediator component (cookie service) that enables communication between web applications from different domains without requiring them to directly share databases or credentials. This mediator reads cookies from one domain and makes them available to applications from other domains, thus enabling cross-domain data sharing while maintaining security boundaries and avoiding direct exposure of sensitive data.
Solution Approach 2:
Instead of sharing the actual database or credentials between domains, the patent creates a copy mechanism where cookie data is read from the source domain and presented to the target domain through the mediator. This copying approach allows data access without exposing the original data source, maintaining security while enabling functionality.
2Productivity
If web applications from different domains share access to common databases, then data exchange is enabled, but security is compromised and configuration complexity increases
Solution Approach 1:
The patent segments the data access architecture by separating the database (stored in browser memory) from the web applications. Each application maintains its own data access path through the mediator, which reads cookies rather than allowing direct database sharing. This segmentation enables efficient data exchange while simplifying configuration and security management.
Solution Approach 2:
The mediator service operates autonomously to manage cross-domain data access. It automatically reads cookies from the source domain and presents them to target domain applications without requiring complex configuration or manual security management. This self-service approach reduces configuration complexity while maintaining secure data exchange.
3Reliability
If a secure local storage mode is implemented where only same-domain modules can access recorded data, then security is enhanced, but data sharing between different domains becomes impossible
Solution Approach 1:
The patent introduces a mediator (cookie service) that operates within the secure local storage environment to enable cross-domain data sharing. The mediator reads cookies from the source domain (which are accessible due to same-domain rules) and presents them to target domain applications. This intermediary approach maintains the security constraints of local storage while enabling the needed versatility for cross-domain sharing.
Data Source
Figure 1~3
Figure 2~4B
Figure 4C~4F
AI summary
The invention relates to a method which enables communication between a first web application (App30A) associated with a first navigation domain (D30A) and a second web application (App30B) associated with a second navigation domain (D30B). Said applications are run inside a browser (20) which has access to a database (40) which is designed to store data supplied by a software module loaded in said browser (20) and to prevent any software module loaded in the browser (20) which is not associated with a navigation domain (D30C) from accessing the data stored by a software module associated with said navigation domain (D30C). The browser concomitantly loads and displays at least two sub-pages (P30A, P30B) of an initial web page (P30), a first sub-page (P30A) being used to display a user interface of the first web application (App30A) and a second sub-page (P30B) being used to display a user interface of the second web application (App30B) which is implemented independently from the first web application. A first software module (S30AC) of the first web application (App30A) stores data in the database (40) which are read by a second software module (S30BC) of the second web application (App30B), of data written into said database (40) by the first software module (S30AC), the first and second software modules (S30AC, S30BC) being associated with a third navigation domain (D30C).