Portal Application Nesting for Secure CMS Integration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Content management platforms often lack secure integration mechanisms with third-party applications, leading to security concerns and loss of control over data integrity and system robustness.

Innovation Solution

The solution involves nesting the content management system within a core portal application, using API interfaces to accept customized web parts and extensions, enabling trusted authentication and seamless integration with third-party applications, such as Tableau or JasperSoft, for secure delivery of dynamic interactive visualizations and analytics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If generic integration devices such as raw APIs and controls are used for third-party application integration, then integration flexibility is improved, but security control and data integrity are worsened

Engineering Contradiction:

Improveintegration flexibilityVSAvoidsecurity control

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a portal application as an intermediary layer between the content management system and third-party applications. This portal application provides a controlled interface that enables integration flexibility while maintaining security control, as it mediates all interactions and enforces authentication protocols without requiring direct access to the CMS core.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the integration architecture by separating the content management system from the portal application layer. This segmentation allows third-party integrations to occur at the portal level with controlled access, preventing direct exposure of the CMS and its data, thereby maintaining security while enabling versatile integrations.

Inventive Principle:

Principle #1Segmentation

2Ease of manufacture

If open API integration is used for third-party applications, then ease of integration is improved, but vulnerability to platform exploitation and data access is worsened

Engineering Contradiction:

Improveease of integrationVSAvoidplatform exploitation vulnerability

Core Design Contradiction:

Ease of manufactureVSObject-affected harmful factors

Solution Approach 1:

The portal application serves as a secure intermediary that maintains open API integration capabilities while filtering and controlling access requests. It provides ease of integration through standardized interfaces while preventing platform exploitation by enforcing authentication and authorization protocols before requests reach the CMS.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements preliminary anti-action by establishing trusted authentication mechanisms before any integration interactions occur. The portal application pre-validates all third-party applications and users, preventing potential exploitation attempts before they can affect the CMS platform.

Inventive Principle:

Principle #9Preliminary anti-action

3Adaptability or versatility

If third-party solutions are used for CMS integration, then integration capability is improved, but control over security mechanisms is worsened

Engineering Contradiction:

Improveintegration capabilityVSAvoidsecurity control dependency

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges the content management system with the portal application into a unified integrated system. This combination maintains integration capability with third-party applications while consolidating security control within the organization's own platform architecture, eliminating dependency on external third-party security mechanisms.

Inventive Principle:

Principle #5Merging (Combining)

4Device complexity

If customized integration hooks are not provided by the CMS, then system simplicity is maintained, but integration flexibility and adaptability are worsened

Engineering Contradiction:

Improvesystem simplicityVSAvoidintegration flexibility

Core Design Contradiction:

Device complexityVSAdaptability or versatility

Solution Approach 1:

The portal application is nested within or integrated with the content management system, creating a layered architecture. This nesting provides customized integration hooks and extended functionality without complicating the core CMS system, allowing flexible third-party integrations while maintaining the simplicity of the base platform.

Inventive Principle:

Principle #7Nested doll (Nesting)

Data Source

PatentEP3559850B1Methods and systems for securely embedding dashboards into a content management system

Publication Date: 2022.11.16 AON GLOBAL OPERATIONS LTD (SINGAPORE BRANCH)

Figure 1A
Figure 1B
Figure 2

AI summary

In an illustrative embodiment, systems and methods for secure access to dynamic analytics content include receiving a request for analytics information from a user at a computing device, confirming the user's access rights, embedding access credentials within a resource link for accessing the visualization content, and supplying the resource link to the user's computing device for use in obtaining the analytics information, where, upon the computing device following the resource link, the access credentials are confirmed and visualization content is provided to the user.