Unified UI Header and SSO for Cloud Container Orchestration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional user interface (UI) management approaches face challenges in integrating multiple UI applications and providing a seamless user experience due to frequent changes in UI-related technologies and the use of different UI frameworks, leading to issues with authentication and navigation across disparate applications.

Innovation Solution

The implementation of a dynamic unification method in a cloud native environment, which configures a single sign-on authentication mechanism and common header across multiple UI applications within a container-orchestration system, using Kubernetes-based Platform-as-a-Service (PaaS) to automate the configuration of ingress routes and unified navigation, enabling a unified user interface experience.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If separate UI applications are used for different management software, then each application can be developed independently with its own UI framework, but integration problems and poor user experience occur across applications

Engineering Contradiction:
ImproveUI framework selection flexibilityVSAvoidUser experience consistency
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces a common header component as an intermediary element that is injected into multiple disparate UI applications. This common header serves as a mediator that provides consistent navigation, branding, and user interface elements across applications built with different UI frameworks, thereby improving user experience consistency without constraining the choice of UI frameworks for individual applications.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple separate sign-in methods are implemented for different UI applications, then each application can have its own authentication logic, but integration complexity and user inconvenience increase

Engineering Contradiction:
ImproveAuthentication method flexibilityVSAvoidAuthentication system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal single sign-on (SSO) authentication mechanism that can be applied across multiple UI applications. This SSO system serves multiple functions: it provides centralized authentication, manages user sessions across applications, and handles authorization. By making the authentication system universal, the patent reduces the number of separate sign-in methods while maintaining the flexibility to support different authentication providers and methods through configuration rather than code changes.

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

3Ease of operation

If common UI framework is forced across multiple applications, then user experience consistency improves, but adaptability to different UI technologies decreases

Engineering Contradiction:
ImproveUser experience consistencyVSAvoidUI technology diversity
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent applies local quality by allowing each UI application to maintain its own framework-specific characteristics and styling in the body content, while only the common header portion is standardized across applications. This approach enables user experience consistency in critical areas (navigation, branding) while preserving the adaptability and framework-specific features of individual applications. The common header is injected locally into each application without forcing a global UI framework unification.

Inventive Principle:
Principle #3Local quality

4Adaptability or versatility

If manual configuration of each UI application is performed, then customization flexibility is maintained, but time consumption and operational effort increase

Engineering Contradiction:
ImproveConfiguration flexibilityVSAvoidConfiguration time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action through automated configuration mechanisms that pre-set common headers and single sign-on authentication parameters for UI applications. Instead of requiring manual configuration of each application, the system automatically injects common headers and configures SSO settings in advance based on templates or centralized configurations. This preliminary setup reduces configuration time while maintaining flexibility through parameterizable configuration options that can be adjusted as needed.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12069039B2Dynamically unifying disparate user interface applications in a cloud native environment
Publication Date: 2024.08.20 EMC IP HLDG CO LLC
  • US12069039B2 patent drawing
  • US12069039B2 patent drawing
  • US12069039B2 patent drawing

AI summary

Methods, apparatus, and processor-readable storage media for dynamically unifying disparate UI applications in a cloud native environment are provided herein. An example computer-implemented method includes obtaining information pertaining to a container-orchestration system operating within at least one cloud native environment; configuring, based on the obtained information, a single sign-on authentication mechanism for multiple user interface applications in the container-orchestration system; configuring, based on the obtained information, at least one ingress route for two or more of the multiple user interface applications in the container-orchestration system; configuring and rendering, based on information pertaining to the at least one ingress route, a common header in at least each of the two or more user interface applications; and performing one or more automated actions based on the configured single sign-on authentication mechanism, the at least one configured ingress route, and the configured and rendered common header.