Web Resource Tokenization via Arbitrary Path Identifiers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing web-based applications expose server-side data models to clients and unauthorized users by transparently sharing server-side resource references, posing a security threat, and existing mechanisms like session IDs and random URLs do not effectively address this issue.

Innovation Solution

Implementing a resource-mapper on the server to generate and manage tokens that identify server-side resources, using arbitrary path identifiers to protect the true identity of these resources, ensuring they are only visible to the client and maintaining a mapping of these tokens to their corresponding resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If server-side resource references are shared transparently with clients, then clients can easily access and use server-side resources, but the true identity and data model of server-side resources are exposed to public view creating security threats

Engineering Contradiction:
Improveclient access to server resourcesVSAvoidsecurity threat from exposed data model
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent introduces tokens as intermediary elements that clients use to reference server-side resources. These tokens act as mediators between the client and the actual server-side resources, allowing clients to access resources without directly exposing the server-side data model or resource identities. The resource-mapper component serves as another intermediary that translates token references into actual resource access on the server side.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates simplified copies of server-side resource references in the form of tokens. These token copies contain arbitrary path identifiers that are viewable by clients but do not reveal the true identity of server-side resources. The copies enable client-side referencing while maintaining security by not exposing the actual resource structure or data model.

Inventive Principle:
Principle #26Copying

2Object-affected harmful factors

If session IDs and random URLs are used to hide server-side resources, then resource identity is protected, but the solution is transparent to developers and does not fundamentally solve the exposure problem

Engineering Contradiction:
Improveresource identity protectionVSAvoidcomplexity of security mechanism
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The patent creates a universal token mechanism that can be applied across all server-side resources and application types. The token system with resource-mapper provides a multi-functional solution that handles resource identification, access control, and data model protection in a unified manner, making it transparent to developers while fundamentally addressing the exposure problem across the entire application.

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

Data Source

PatentUS8533291B1Method and system for protecting publicly viewable web client reference to server resources and business logic
Publication Date: 2013.09.10 ORACLE AMERICAN INC
  • US8533291B1 patent drawing
  • US8533291B1 patent drawing
  • US8533291B1 patent drawing

AI summary

A method and system for protecting publicly viewable web client reference to network accessible data includes receiving a request for a server side resource from a client. The request is triggered upon loading of a page having a component that needs to access server side resource, at the client. A token for the server side resource is generated at the server using a resource-mapper, the resource-mapper identifying the server side resource that is to service the request from the client. The generated token and contents for the component are returned to the client, the generated token identifying an arbitrary path identifier to the server side resource that is viewable to the client, the arbitrary path identifier being interpreted by the resource-mapper to enable rendering of the content for the component at the client, such that the arbitrary path identifier protects identification information associated with the server side resource.