Workspace Orchestration System API Access Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Information Handling Systems (IHSs) face challenges in securely managing access to resources within isolated software environments, particularly when web applications request access to native APIs, which can compromise security if not properly restricted.

Innovation Solution

Implementing a workspace orchestration system that determines and restricts access to native APIs for web applications, while allowing access to web APIs associated with the same peripheral device, thereby enhancing security by limiting the exposure of sensitive resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If web applications are allowed to access native APIs directly, then functionality and ease of operation are improved, but security and system stability deteriorate

Engineering Contradiction:
Improveweb application access to peripheral devicesVSAvoidsystem security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces a workspace orchestration system as an intermediary layer between web applications and native APIs. This mediator translates web application requests into appropriate native API calls while enforcing security policies, thus maintaining ease of operation for web apps while protecting system security through controlled access mediation

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If web applications are isolated from native APIs, then security is improved, but functionality and adaptability deteriorate

Engineering Contradiction:
Improvesystem securityVSAvoidweb application access to hardware resources
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments API access into two distinct categories: web APIs for standard web application needs and native APIs for advanced hardware access. This segmentation allows web applications to freely use web APIs while native API access is tightly controlled through the workspace orchestration system, thus maintaining security while preserving necessary adaptability

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies different access control policies to different API types based on their security characteristics. Web APIs receive permissive access control allowing broad functionality, while native APIs receive restrictive access control with explicit approval requirements, thus balancing security and adaptability according to the specific needs of each API category

Inventive Principle:
Principle #3Local quality

3Adaptability or versatility

If web applications can use native APIs, then functionality is improved, but the complexity of access management increases

Engineering Contradiction:
Improveweb application functionalityVSAvoidaccess management system
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The workspace orchestration system provides universal access management for both web APIs and native APIs through a single unified platform. This multi-functional system handles approval workflows, policy enforcement, and access control for both API types, thus managing functionality expansion without proportionally increasing system complexity

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

Data Source

PatentUS11310304B1Web application access management system and method for a workspace orchestration system
Publication Date: 2022.04.19 DELL PROD LP
  • US11310304B1 patent drawing
  • US11310304B1 patent drawing
  • US11310304B1 patent drawing

AI summary

Embodiments of systems and methods for managing an Information Handling System (IHS) using a workspace orchestration system are described. In an illustrative, non-limiting embodiment, an IHS may include computer-executable instructions to, for each of a plurality of workspaces instantiated on the IHS, upon receiving a request to launch a web application from an online server; determine one or more native APIs that the web application is restricted from using. When the web application request access to one of the restricted native APIs, the instructions reject the request, and when the web application request access to one of a web API, the instructions accept the request. The web API and the native API are associated with the same peripheral device.