Secure Cross-Domain Scripting via Callback Resource Identifier

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern web browsers' same origin policy restricts cross-domain communication, making it difficult for web service developers to provide integrated services or applications across different domains while maintaining security, as it limits script access and data sharing between web pages from different domains.

Innovation Solution

A system that generates a developer key to bind a callback resource identifier, allowing secure data transmission and resource sharing between domains by creating nested inline frames within a web page, using the callback URL to facilitate communication between different domains while ensuring security through revocation status and authentication tokens.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If modern browsers enforce same origin policy to prevent security risks, then security is improved, but cross-domain service integration and data sharing are restricted

Engineering Contradiction:
ImprovesecurityVSAvoidcross-domain service integration
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a callback resource identifier as an intermediary mechanism that enables secure cross-domain communication. The callback URL acts as a mediator between the first domain (web page) and second domain (service provider), allowing data exchange while maintaining browser security policies. The system generates a unique callback resource identifier for each developer, which serves as a secure channel for receiving data from external domains without violating same origin restrictions.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the cross-domain communication process into distinct components: an initiation request from the first domain, a callback resource identifier generation by the server, and a second inline frame creation in the second domain. This segmentation allows each component to operate within its own domain context while maintaining secure communication through the callback mechanism, thus enabling service integration without compromising security.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If scripts are embedded to access cross-domain APIs and functions, then service integration capability is improved, but security risks from malicious script injection increase

Engineering Contradiction:
Improveservice integration capabilityVSAvoidsecurity risks from script injection
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent implements a feedback mechanism where the server generates a unique callback resource identifier in response to an initiation request, and this identifier is then used to create a controlled communication channel. The callback URL provides feedback from the second domain back to the first domain in a secure manner, allowing service integration while preventing unauthorized script injection since only authenticated callback channels can communicate.

Inventive Principle:
Principle #23Feedback

3Ease of operation

If cross-domain script execution is allowed to provide integrated services, then ease of operation is improved, but security control and access protection deteriorate

Engineering Contradiction:
Improvecross-domain service accessVSAvoidsecurity control mechanism
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent performs preliminary actions by generating the callback resource identifier before actual cross-domain data exchange occurs. The server authenticates the developer and creates a secure callback channel in advance, which simplifies subsequent cross-domain operations. This preliminary setup reduces the complexity of security control during runtime, as the communication channel is already authenticated and secured before use.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8789204B2Method and apparatus for secure cross-site scripting
Publication Date: 2014.07.22 WSOU INVESTMENTS LLC
  • US8789204B2 patent drawing
  • US8789204B2 patent drawing
  • US8789204B2 patent drawing

AI summary

An approach is provided for providing secure cross-site scripting. A web services platform causes, at least in part, reception of an initiation request from at least a first inline frame of at least one web page. The initiation request specifies a developer identifier associated with a domain of the at least one web page. The web services platform determines a callback resource identifier based on the developer identifier. The web services platform then determines to cause, at least in part, transmission of the callback resource identifier to the at least the first inline frame for use in creation of at least a second inline frame associated with the at least the first inline frame.